Lines Matching full:foo
27 If a symbol has a prompt (e.g. ``bool "Enable foo"``), then the user can change
251 bool "FOO SoC"
326 bool "external SPI ADC foo driver"
357 config FOO
358 bool "Support foo"
360 In this case, ``FOO`` will end up with this definition:
364 config FOO
365 bool "Support foo"
369 ``FOO`` in :file:`Kconfig.other`, because the ``DEP`` dependency has already
386 config FOO
387 bool "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
516 bool "Foo device"
519 int "Foo device frequency"
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``.
545 menu "Foo subsystem"
548 bool "Foo subsystem"
553 bool "Foo feature 1"
556 bool "Foo feature 2"
559 int "Foo frequency"
561 ... lots of other FOO-related symbols
573 bool "Foo subsystem"
578 bool "Foo feature 1"
581 bool "Foo feature 2"
584 int "Foo frequency"
586 ... lots of other FOO-related symbols
594 [*] Foo subsystem --->
614 config FOO
625 config FOO
682 for some components of the symbol name with e.g. ``git grep FOO`` and
703 config FOO
704 bool "Foo"
729 config FOO
730 bool "Foo"
757 menu "Foo features"
761 bool "Foo feature 1"
764 bool "Foo feature 2"
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
798 bool "foo"
801 config FOO
802 bool "foo"
805 In the following example FOO will get the value ``y``.
809 config FOO
810 bool "foo"
813 config FOO
814 bool "foo"
829 config FOO
830 bool "foo"
834 config FOO
836 prompt "foo"
845 config FOO
850 config FOO
874 For a Kconfig symbol that enables a driver/subsystem FOO, consider having just
875 "Foo" as the prompt, instead of "Enable Foo support" or the like. It will
917 USB keyboard support by default on the FOO SoC, while still allowing the user
923 bool "FOO SoC"
998 menu "Foo subsystem"
1002 int "Foo setting 1"
1006 int "Foo setting 2"
1018 int "Foo setting 1"
1023 int "Foo setting 2"
1033 menu "Foo subsystem"
1037 int "Foo setting 1"
1041 int "Foo setting 2"
1051 int "Foo setting 1" if HAS_CONFIGURABLE_FOO
1055 int "Foo setting 2" if HAS_CONFIGURABLE_FOO