Lines Matching refs:FOO
251 bool "FOO SoC"
357 config FOO
360 In this case, ``FOO`` will end up with this definition:
364 config FOO
369 ``FOO`` in :file:`Kconfig.other`, because the ``DEP`` dependency has already
386 config FOO
391 default 0x200 if FOO
394 Assume that the intention here is to use a larger stack whenever ``FOO`` is
395 enabled, and that the configuration initially has ``FOO`` disabled. Also,
402 0x100, as expected. After enabling ``FOO``, you might reasonably expect the
417 ``STACK_SIZE`` appears to be "frozen" at 0x100 when toggling ``FOO``.
429 default 0x200 if FOO
435 0x200 when ``FOO`` is enabled, then disable its prompt when ``FOO`` is
441 hex "Stack size" if !FOO
442 default 0x200 if FOO
459 default 0x200 if FOO
532 If the definition of a symbol ``FOO`` is immediately followed by other symbols
533 that depend on ``FOO``, then those symbols become children of ``FOO``. If
534 ``FOO`` is defined with ``config FOO``, then the children are shown indented
535 relative to ``FOO``. Defining ``FOO`` with ``menuconfig FOO`` instead puts the
536 children in a separate menu rooted at ``FOO``.
561 ... lots of other FOO-related symbols
586 ... lots of other FOO-related symbols
614 config FOO
625 config FOO
682 for some components of the symbol name with e.g. ``git grep FOO`` and
703 config FOO
729 config FOO
792 That is, FOO will be set to ``n`` in the example below. If the ``default n`` was
793 omitted in the first definition, FOO would have been set to ``y``.
797 config FOO
801 config FOO
805 In the following example FOO will get the value ``y``.
809 config FOO
813 config FOO
829 config FOO
834 config FOO
845 config FOO
850 config FOO
874 For a Kconfig symbol that enables a driver/subsystem FOO, consider having just
896 USB keyboard support by default on the FOO SoC, while still allowing the user
902 bool "FOO SoC"