I know the device three mechanism is also applied in zephyr sdk, but it seems something diffferent compare with in linux.
in linux, the dtsi script file would be compiled to a binary blob which would be pared in running time, so, the driver would do some dynamically decision in running time to different branch.
but in zephyr sdk, the dts are commpiled to a intermidate dts script file, which would be parsed by tools before building process are held.
finally, the dts configuration would convert to header files,and just used in compile time, so cant used to do the branch control like linux.
is this right? and is there anyway to get the configuration in runtime in zephyr?
thnks for your help.