Lines Matching defs:Kconfig

2 Kconfig Language
101 	a) A new Kconfig option for something that used to always be built
104 	b) A new gatekeeping Kconfig option that hides/shows other Kconfig
327 Kconfig syntax
453 '#' Kconfig source file comment:
460 Kconfig hints
462 This is a collection of Kconfig tips, most of which aren't obvious at
463 first glance and most of which have become idioms in several Kconfig
471 that is defined in a common Kconfig file and selected by the relevant
475 We would in lib/Kconfig see::
573 The most common way to express this optional dependency in Kconfig logic
609 Kconfig recursive dependency limitations
612 If you've hit the Kconfig error: "recursive dependency detected" you've run
613 into a recursive dependency issue with Kconfig, a recursive dependency can be
615 Kconfig files comply with specified configuration requirements. In order to do
616 that kconfig must determine the values that are possible for all Kconfig
618 between two or more Kconfig symbols. For more details refer to the "Simple
619 Kconfig recursive issue" subsection below. Kconfig does not do recursive
620 dependency resolution; this has a few implications for Kconfig file writers.
622 technical limitation which this brings upon Kconfig developers. Eager
626 Simple Kconfig recursive issue
629 Read: Documentation/kbuild/Kconfig.recursion-issue-01
633   make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-01 allnoconfig
635 Cumulative Kconfig recursive issue
638 Read: Documentation/kbuild/Kconfig.recursion-issue-02
642   make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig
647 Developers who run into the recursive Kconfig issue have two options
658 The resolution to a) can be tested with the sample Kconfig file
659 Documentation/kbuild/Kconfig.recursion-issue-01 through the removal
664 The two different resolutions for b) can be tested in the sample Kconfig file
665 Documentation/kbuild/Kconfig.recursion-issue-02.
712 Kconfig should have at least clear and well defined semantics which also
716 Further work on both of these areas is welcomed on Kconfig. We elaborate
719 Semantics of Kconfig
722 The use of Kconfig is broad, Linux is now only one of Kconfig's users:
723 one study has completed a broad analysis of Kconfig use in 12 projects [0]_.
725 in documenting basic Kconfig syntax a more precise definition of Kconfig
726 semantics is welcomed. One project deduced Kconfig semantics through
728 the deduced semantics matches our intended Kconfig design goals.
730 the Kconfig language [10]_.
734 express in boolean abstraction of the inferred semantics of Kconfig to
735 translate Kconfig logic into boolean formulas and run a SAT solver on this to
739 dependencies and has led to dozens of committed fixes to Linux Kconfig files [11]_.
741 Confirming this could prove useful as Kconfig stands as one of the leading
746 variability modeling languages such as Kconfig [3]_.
753 Full SAT solver for Kconfig
756 Although SAT solvers [4]_ haven't yet been used by Kconfig directly, as noted
758 abstraction the inferred semantics of Kconfig to translate Kconfig logic into
762 extract variability models from Kconfig and put them together with a
765 solver is desirable on Kconfig one approach would be to evaluate repurposing
766 such efforts somehow on Kconfig. There is enough interest from mentors of