Folks, I was thinking about doing a code cleanup in the dts.fixup and uart and gpio driver for the i.MX7 SoC, where we create redundant defines already covered by devicetree aliases. Here is a breif e

#defines

This is an excellent idea. The only downside (upside?) is having to standardize on all of the subsystem driver labels. And it still doesn't solve the device specific properties unless we were to exten

#defines

Andy, Actually, the dts extraction already deals with the driver properties listed in the yaml file. For example, the nxp,imx-uart.yaml, has the following #defines automatically generated for the uart

#defines

Ah, right. Yeah this looks quite nice then.

#defines

>What do you think? Do you see any caveats about this? A similar or the same idea drived the #9526 PR. I think a prefix like dtconfig_ is usefull in aliases definition. Best regards, István

#defines

Hello fellow mailinglist members, I'm currently trying to get the samples "hci_uart" and "hci_usb" working on a laird654 module / Laird DVK-BL654-1.0 (nrf52480) Both samples work on the nrf52480DK (pc

#nrf52840 #defines

Hello Matthias, By default the BL654 DVK does not connect the external 32 kHz clock. In zephyr, the NRF52840 board files are setup to use the external 32 kHz clock. You have 2 options: Follow the inst

#nrf52840 #defines

Hello developers! I have difficulties finding any documentation/examples of how to define a simple GPIO as an e.g. output in the frdm_k64f.dts file for the frdm_k64f board. As long as we talk about de

#defines

Hello Bo, We have a general help page for Device Tree: https://docs.zephyrproject.org/latest/guides/dts/index.html In your particular case, you need to set port b pin 22 as output. Device Tree: The pu

#defines

Hello Andrei, And thank you very much for your quick answer. I really appriciate the quick link to where I can find the documentation and also the example you have provided. I am also aware of, that i

#defines

Hello, Yes, my example was hardcoded in regard to port and pin number. Your example makes them configurable via dts, while code remains the same. I only have to point another thing: the generated macr

#defines

Thank you for your quick assistance yesterday Andrei. Maybe I misunderstood your last point, but as I see it, it is the name "test_pin" in my example, which needs to remain the same across dts files f

#defines

Given this Kconfig: config MY_STR string "A string" The directive #if defined(CONFIG_MY_STR) will eval to true for the default empty string. How to check if CONFIG_MY_STR is an empty string at compile

#builds #defines