-
Notifications
You must be signed in to change notification settings - Fork 8.4k
doc: kconfig: document DT_COMPAT_<...> macro variables #100678
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
doc: kconfig: document DT_COMPAT_<...> macro variables #100678
Conversation
|
Related to #100193 |
|
This probably overlaps with #100193 |
Yes in the sense that the assertions are not valid in (certain!) |
doc/contribute/style/kconfig.rst
Outdated
| depending on the automatically created ``DT_HAS_<node>_ENABLED`` symbol. | ||
|
|
||
| * When building complex expressions based on devicetree node compatibles, | ||
| use the automatically defined :samp:`DT_COMPAT_{VND,DEVICE}` instead |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| use the automatically defined :samp:`DT_COMPAT_{VND,DEVICE}` instead | |
| use the automatically defined :samp:`DT_COMPAT_{VND_DEVICE}` instead |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch - fixed.
The DT_COMPAT_<...> macro variables are generated for every compatible found in bindings: document them as existing and recommend using them in various Kconfig documentation pages. Signed-off-by: Mathieu Choplain <mathieu.choplain-ext@st.com>
b95e4d5 to
7a55bc9
Compare
|



The
DT_COMPAT_<...>macro variables are generated for every compatible found in bindings: document them as existing and recommend using them in various Kconfig documentation pages.