Lines Matching full:a
8 The configuration database is a collection of configuration options
9 organized in a tree structure::
31 Most entries define a config option; all other entries help to organize
32 them. A single configuration option is defined like this::
38 Usually, modules have to be recompiled whenever you switch to a new
41 Every line starts with a key word and can be followed by multiple
42 arguments. "config" starts a new config entry. The following lines
45 values. A config option can be defined multiple times with the same
46 name, but every definition can have only a single input prompt and the
52 A menu entry can have a number of attributes. Not all of them are
57 Every config option must have a type. There are only two basic types:
77 A config option can have any number of default values. If multiple
97 a) A new Kconfig option for something that used to always be built
100 b) A new gatekeeping Kconfig option that hides/shows other Kconfig
104 c) Sub-driver behavior or similar options for a driver that is
114 This is a shorthand notation for a type definition plus a value.
119 This defines a dependency for this menu entry. If multiple
135 While normal dependencies reduce the upper limit of a symbol (see
136 below), reverse dependencies can be used to force a lower limit of
145 a symbol to a value without visiting the dependencies.
146 By abusing select you are able to select a symbol FOO even
155 This is similar to "select" as it enforces a lower limit on another
157 from a direct dependency or with a visible prompt.
184 ability to hook into a secondary subsystem while allowing the user to
187 Note: If the combination of FOO=y and BAR=m causes a link error,
210 similar to a conditional "prompt" attribute for individual menu
216 and hex symbols. The user can only input a value which is larger than
222 This defines a help text. The end of the help text is determined by
224 a smaller indentation than the first line of the help text.
233 This declares a list of default entries which can be used when
249 Dependencies define the visibility of a menu entry and can also reduce
283 An expression can have a value of 'n', 'm' or 'y' (or 0, 1, 2
284 respectively for calculations). A menu entry becomes visible when its
298 The position of a menu entry in the tree is determined in two ways. First
309 All entries within the "menu" ... "endmenu" block become a submenu of
315 dependencies. If a menu entry somehow depends on the previous entry, it
316 can be made a submenu of it. First, the previous (parent) symbol must
341 The configuration file describes a series of menu entries, where every
342 line starts with a keyword (except help texts). The following keywords
343 end a menu entry:
353 The first five also start the definition of a menu entry.
360 This defines a config symbol <symbol> and accepts any of above
368 This is similar to the simple config entry above, but it also gives a
369 hint to front ends, that all suboptions should be displayed as a
416 This defines a choice group and accepts any of the above attributes as
417 options. A choice can only be of type bool or tristate. If no type is
418 specified for a choice, its type will be determined by the type of
420 choice elements have a type specified, as well.
422 While a boolean choice only allows a single config entry to be
423 selected, a tristate choice also allows any number of config entries
424 to be set to 'm'. This can be used if multiple drivers for a single
425 hardware exists and only a single driver can be compiled/loaded into
428 A choice accepts another option "optional", which allows to set the
430 If no [symbol] is associated with a choice, then you can not have multiple
431 definitions of that choice. If a [symbol] is associated to the choice,
440 This defines a comment which is displayed to the user during the
451 This defines a menu block, see "Menu structure" above for more
480 An unquoted '#' character anywhere in a source file line indicates
481 the beginning of a source file comment. The remainder of that line
482 is a comment.
487 This is a collection of Kconfig tips, most of which aren't obvious at
493 It is a common idiom to implement a feature/functionality that are
495 The recommended way to do so is to use a config variable named HAVE_*
496 that is defined in a common Kconfig file and selected by the relevant
519 Note: we use the existing config option and avoid creating a new
523 introduced to overcome the limitation of select which will force a
526 situation where select forces a symbol equals to 'y'.
533 followed by a test macro::
540 If you need to expose a compiler capability to makefiles and/or C source files,
548 To restrict a component build to module-only, qualify its config symbol
560 into a recursive dependency issue with Kconfig, a recursive dependency can be
561 summarized as a circular dependency. The kconfig tools need to ensure that
564 symbols, this is currently not possible if there is a circular relation
567 dependency resolution; this has a few implications for Kconfig file writers.
595 at their disposal. We document them below and also provide a list of
598 a) Remove any superfluous "select FOO" or "depends on FOO"
605 The resolution to a) can be tested with the sample Kconfig file
614 Below is a list of examples of prior fixes for these types of recursive issues;
621 06b718c01208 select A -> depends on A
622 c22eacfe82f9 depends on A -> depends on B
623 6a91e854442c select A -> depends on A
624 118c565a8f2e select A -> select B
625 f004e5594705 select A -> depends on A
626 c7861f37b4c6 depends on A -> (null)
627 80c69915e5fb select A -> (null) (1)
628 c2218e26c0d0 select A -> depends on A (1)
629 d6ae99d04e1c select A -> depends on A
630 95ca19cf8cbf select A -> depends on A
631 8f057d7bca54 depends on A -> (null)
632 8f057d7bca54 depends on A -> select A
633 a0701f04846e select A -> depends on A
634 0c8b92f7f259 depends on A -> (null)
635 e4e9e0540928 select A -> depends on A (2)
636 7453ea886e87 depends on A > (null) (1)
637 7b1fff7e4fdf select A -> depends on A
638 86c747d2a4f0 select A -> depends on A
639 d9f9ab51e55e select A -> depends on A
640 0c51a4d8abd6 depends on A -> select A (3)
641 e98062ed6dc4 select A -> depends on A (3)
642 91e5d284a7f1 select A -> (null)
653 evaluating the use of a full SAT solver for it. A full SAT solver can be
655 for instance on possible use case for a SAT solver could be that of handling
657 address such issues but such evaluation is desirable. If support for a full SAT
670 one study has completed a broad analysis of Kconfig use in 12 projects [0]_.
671 Despite its widespread use, and although this document does a reasonable job
672 in documenting basic Kconfig syntax a more precise definition of Kconfig
680 translate Kconfig logic into boolean formulas and run a SAT solver on this to
702 boolean formulas and run a SAT solver on it [5]_. Another known related project
705 extract variability models from Kconfig and put them together with a
706 propositional formula extracted from CPP #ifdefs and build-rules into a SAT
707 solver in order to find dead code, dead files, and dead symbols. If using a SAT