Getting some of the configuration options switched on in Zephyr

[SmallerPond]

This might not be the optimal forum for this question, but I'm not sure where else to post it. I have a (I think) very simple question about configuring Zephyr.

I have a LIS2DH sensor hooked up to my nRF9160 DK. I can get the sensor example from Zephyr to build and flash and, seemingly, even to run properly. What I am having trouble with is enabling the trigger interrupt line. There is an option in the sample code,

`CONFIG_LIS2DH_TRIGGER`

that presumably enables this functionality, but when I try to set it in my `prj.conf` I get an error that I'm not supposed to set it there:

error: LIS2DH_TRIGGER (defined at drivers/sensor/lis2dh/Kconfig:35) is assigned in a configuration
file, but is not directly user-configurable (has no prompt). It gets its value indirectly from other
symbols. See docs.zephyrproject.org/.../CONFIG_LIS2DH_TRIGGER.html
and/or look up LIS2DH_TRIGGER in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.

It points me to a page that gives me no hints about how to set this option. Any chance someone here could point me in the correct direction?

[Simon]

Try setting CONFIG_LIS2DH_TRIGGER_GLOBAL_THREAD=y or CONFIG_LIS2DH_TRIGGER_OWN_THREAD=y in the prj.conf file (only one of them) instead.

They will then set CONFIG_LIS2DH_TRIGGER=y through the select statement (see zephyr/drivers/sensor/lis2dh/Kconfig#L26 and zephyr/drivers/sensor/lis2dh/Kconfig#L31).

---

All configurations without a prompt is not directly configurable, for example the config LIS2DH_TRIGGER has no text associated with it unlike the LIS2DH_TRIGGER_GLOBAL_THREAD for example, which has the text "Use global thread" associated with it.

The way I found this out was to search for "select LIS2DH_TRIGGER" in the whole NCS using VS code. You can also look at the Kconfig reference for CONFIG_LIS2DH_TRIGGER, which tells you what Kconfigs to set instead:

Best regards,

Simon