Use custom sensor driver instead of the Zephyr one

[bojan]

Hello, guys!  

We are using Zephyr RTOS for our development.

As you know, many of the sensors come integrated into the Zephyr under zephyr/drivers/sensor/. For one of the sensors from that list (lis2dw12), we wanted to implement our own customized version and not use the official one coming with Zephyr.

The problem comes when we want to compile our code that includes the sensor. The problem is about multiple definitions of some sensor APIs - one definition is coming from the Zephyr another from our implementation.

What would be the simplest way to tell the compiler not to include the sensor driver that comes from Zephyr?

Thanks in advance for your time and efforts.

Sincerely,
Bojan.

[Einar Thorsrud]

Hi Bojan,

First of all, I suggest you rename your sensor driver. Having multiple instances with the same name will only cause problems. Secondly, you will need to disable the original sensor in your device tree (bord definition) to not use the existing driver.

Einar

[bojan]

Thanks, Einar Thorsrud .

That did the trick!

Cheers!