LIS2DH SPI Support

[theBASTI0N]

The LIS2DH works well with I2C devices such as the Thingy52, however when testing with a Ruuvitag which has the the sensor on the SPI bus readings are wrong.

The driver looks like it doesn't not configure the SPI bus correctly as it missues the CS controller and CS pin configurations. An example of the correct configuration type can be found for the lis2ds12 driver.

Steps to reproduce the behavior:

1. git clone https://github.com/theBASTI0N/zephyr-ruuvi.git /boards/arm/nrf52_ruuvi
2. cd ~/xephyrproject/zephyr/
3. west build -b nrf52_ruuvi samples/sensor/lis2dh
4. See readings, I used:
   CONFIG_USE_SEGGER_RTT=y
   CONFIG_RTT_CONSOLE=y
   CONFIG_UART_CONSOLE=n

There is no error in stating the device cannot be found, however the reading are wrong.

The output is:

SEGGER J-Link V6.60f - Real time terminal output
J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 7 2019 14:07:15 V1.0, SN=682061953
Process: JLinkExe
*** Booting Zephyr OS build zephyr-v2.1.0-1478-g702ebb321225 ***
Polling at 0.5 Hz
#1 @ 12600 ms: x -0.009576 , y -0.009576 , z -0.009576
#2 @ 13901 ms: x -0.009576 , y -0.009576 , z -0.009576
#3 @ 15202 ms: x -0.009576 , y -0.009576 , z -0.009576
#4 @ 16503 ms: x -0.009576 , y -0.009576 , z -0.009576
#5 @ 17804 ms: x -0.009576 , y -0.009576 , z -0.009576
#6 @ 19106 ms: x -0.009576 , y -0.009576 , z -0.009576
#7 @ 20407 ms: x -0.009576 , y -0.009576 , z -0.009576
#8 @ 21708 ms: x -0.009576 , y -0.009576 , z -0.009576
#9 @ 23009 ms: x -0.009576 , y -0.009576 , z -0.009576
#10 @ 24310 ms: x -0.009576 , y -0.009576 , z -0.009576

The makes using the lis2dh12 on the ruuvitag almost impossible.

Environment

• OS:Debian 10
• Toolchain Zephyr SDK
• Version 2.1.99

[avisconti]

OK, I'll start next week.
I'll put LIS2DH driver similar to LIS2DS12, with a lis2dh_i2c.c and lis2dh_spi.c file, compiled according to dts configuration.

[theBASTI0N]

Awesoe thanks for the help.
@https://github.com/ojousima

Did some work on an older version and git it work, which i added to the newest driver version.
This can be found at:
https://github.com/theBASTI0N/zephyr/tree/master/drivers/sensor/lis2dh

The sensor is now working.

[avisconti]

Did some work on an older version and git it work, which i added to the newest driver version.
This can be found at:
https://github.com/theBASTI0N/zephyr/tree/master/drivers/sensor/lis2dh

The sensor is now working.

Fine!
You may want to create a PR out of this. We can quickly merge it and close the bug then. In fact, I currently have some other urgencies, and working on this stuff may take longer than expected.

[theBASTI0N]

It works sometimes and the interrupts dont seem to work.

[avisconti]

@theBASTI0N
I'm providing a fix for this bug. Can you possibly cross verify it?

[theBASTI0N]

@avisconti
I will be able to verify it later today.

Thanks for the help