treewide: use auto-generated Kconfig compatible macro variables #100216
Conversation
zephyrbot
requested review from
ClaCodes,
butok,
dbaluta,
decsny,
dleach02,
jaz1-nordic,
kl-cruz,
lstnl,
manuargue,
mmahadevan108,
nashif,
nordic-krch,
rlubos,
tmon-nordic and
udaynordic
Replace some manually-defined DT_COMPAT_<> Kconfig macro variables with their automatically generated counterparts. In most cases, this is straightforward as the manually defined macro is named identically to the one generated by the build system. Signed-off-by: Mathieu Choplain <[email protected]>
mathieuchopstm
force-pushed
the
topic/cleanup_DT_COMPAT_kconfig/treewide
branch
from
7da38f0 to
7fa30cc
Compare
|
Fixed conflict from #100326 merge + use identical wording in |
zephyrbot
requested review from
anangl,
asmellby,
carlescufi,
dcpleung,
de-nordic,
jfischer-no,
krish2718,
maass-hamburg,
masz-nordic and
nika-nordic
|
|
#100215 caused regressions on STM32 platforms - DNM until investigated |
| DT_COMPAT_NORDIC_NRF_SPIM := nordic,nrf-spim | ||
|
|
||
| config NRFX_SPIM | ||
| bool "SPIM driver" | ||
| depends on $(dt_has_compat,$(DT_COMPAT_NORDIC_NRF_SPIM)) | ||
|
|
||
| DT_COMPAT_NORDIC_NRF_SPIS := nordic,nrf-spis | ||
|
|
There was a problem hiding this comment.
I do not think you can remove them. They are not the same as generated DT_HAS_"compatiple"_ENABLED macros and actually used below as arguments in dt_has_compat().
There was a problem hiding this comment.
These macros are generated automatically by gen_driver_kconfig_dts.py - see <build dir>/Kconfig/Kconfig.dts.
This is a pattern already present in tree - see for example:
zephyr/drivers/audio/Kconfig.pcm1681
Lines 4 to 9 in 3b23c76
|
Removing DNM: there are no |
8 participants
Replace some manually-defined
DT_COMPAT_<>Kconfig macro variables with their automatically generated counterparts. In most cases, this is straightforward as the manually defined macro is named identically to the one generated by the build system.See also #100215