KConfig is warning me:
CONFIG_LSM6DSO was assigned the value y, but got the value n. Missing dependencies:
DT_HAS_ST_LSM6DSO_ENABLED
I am running on a custom board, the device tree entry looks like this:
&spi0 {
compatible = "nordic,nrf-spi";
/* Cannot be used together with i2c0. */
status = "okay";
cs-gpios = <&gpio0 24 GPIO_ACTIVE_LOW>; // P0.24
pinctrl-0 = <&spi0_default>;
pinctrl-1 = <&spi0_sleep>;
pinctrl-names = "default", "sleep";
lsm6dso: lsm6dso@0 {
compatible = "st,lsm6dso";
status="okay";
irq-gpios = <&gpio0 13 GPIO_ACTIVE_HIGH>;
int-pin=<1>;
spi-max-frequency = <1000000>;
reg = <0>;
};
};
In spite of the warning, the lsm6dso device seems to run fine in trigger mode. My concern is that the device trigger seems to be running on an interrupt handler, despite
In spite of the warning, the lsm6dso device seems to run fine in trigger mode. My concern is that the device trigger seems to be running on an interrupt handler, despite
CONFIG_LSM6DSO_TRIGGER_OWN_THREAD=y
Regardless, I'm confused as to why I'm seeing this warning - how can I be using the driver successfully at all if CONFIG_LSM6DSO got 'n'?
The devicetree GUI sees my lsm6dso device just fine. The KConfig GUI complains about DT_HAS_ST_LSM6DSO_ENABLED.
Thank you for any support!
Regardless, I'm confused as to why I'm seeing this warning - how can I be using the driver successfully at all if CONFIG_LSM6DSO got 'n'?
The devicetree GUI sees my lsm6dso device just fine. The KConfig GUI complains about DT_HAS_ST_LSM6DSO_ENABLED.
Thank you for any support!
