Lines Matching refs:symbol

27 If a symbol has a prompt (e.g. ``bool "Enable foo"``), then the user can change
28 the symbol's value in the ``menuconfig`` or ``guiconfig`` interface (see
30 symbol without a prompt can never be changed directly by the user, not even by
33 Only put a prompt on a symbol if it makes sense for the user to change its
91 The ``select`` statement is used to force one symbol to ``y`` whenever another
92 symbol is ``y``. For example, the following code forces ``CONSOLE`` to ``y``
115 For example, say that a new dependency is added to the ``CONSOLE`` symbol
116 above, by a developer who is unaware of the ``USB_CONSOLE`` symbol (or simply
165 In general, whenever the dependencies of a symbol are updated, the dependencies
175 which hides ways in which a symbol might get enabled.
238 For example, a helper symbol for indicating that a particular CPU/SoC has an
279 the following code defines a helper symbol that has the value ``y`` if the
308   of the selecting and selected symbol will never drift out of sync, e.g. when
416 respected, and any symbol defaults are ignored. This is why the value of
495 calculating symbol values.
510 The Kconfig definitions below will hide the ``FOO_DEVICE_FREQUENCY`` symbol and
532 If the definition of a symbol ``FOO`` is immediately followed by other symbols
568 ``FOO_SUBSYSTEM`` into a ``menuconfig`` symbol:
596 Note that making a symbol without children a ``menuconfig`` is meaningless. It
597 should be avoided, because it looks identical to a symbol with all children
635 afterwards. To get to a symbol quickly, use the jump-to feature (press
643   If one symbol depends on another, then it's often a good idea to place it
644   right after the symbol it depends on. It will then be shown indented relative
645   to the symbol it depends on in the ``menuconfig`` interface, and in a
646   separate menu rooted at the symbol in ``guiconfig``. This also works if
647   several symbols are placed after the symbol they depend on.
657   ``FOO_SUPPORT`` symbol.
661   This can be checked by selecting a symbol and pressing :kbd:`?` to view the
662   symbol information. If there are duplicated dependencies, then use the
663   ``Included via ...`` path shown in the symbol information to figure out where
675 Some checks are necessarily a bit heuristic, so a symbol being flagged by a
680 When investigating an unknown symbol ``FOO_BAR``, it is a good idea to run
682 for some components of the symbol name with e.g. ``git grep FOO`` and
785 be what was intended compared to other symbol types as well.
788 defining a symbol in multiple locations and wanting to override e.g. a
824 - ``<type> "prompt"`` is a shorthand for giving a symbol/choice a type and a
862    For a symbol defined in multiple locations (e.g., in a ``Kconfig.defconfig``
863    file in Zephyr), it is best to only give the symbol type for the "base"
864    definition of the symbol, and to use ``default`` (instead of ``def_<type>
866    the symbol is removed, the symbol ends up without a type, which generates a
874 For a Kconfig symbol that enables a driver/subsystem FOO, consider having just
937 A condition can be put on a symbol's prompt to make it optionally configurable
958 The ``HAS_CONFIGURABLE_MASK`` helper symbol would get selected by boards to
992 within it, while still allowing symbol default values to kick in.
1077 The *Intro to symbol values* section in the `Kconfiglib docstring