Lines Matching full:values

86 values:
108 values, run this code from e.g. 'make iscriptconfig':
115 Intro to symbol values
191 that this includes all symbols that would accept user values). Kconfiglib
208 In Kconfiglib, the set of (currently) assignable values for a bool/tristate
288 represented as constant symbols, so the only values that appear in expressions
509 Another gotcha is that environment variables referenced in the values of
592 if multiple configurations are loaded with different values for $srctree.
659 as .config files (which store configuration symbol values).
668 KCONFIG_STRICT relies on literal hex values being prefixed with 0x/0X.
902 Loads symbol values from a file in the .config format. Equivalent to
903 calling Symbol.set_value() to set each of the values.
918 True if all existing user values should be cleared before loading the
989 # choice from the kind of values that are assigned
1043 # Use strings for bool/tristate user values in the warning
1075 Writes out symbol values as a C header file, matching the format used
1126 Writes out symbol values in the .config format. The format matches the
1134 See the 'Intro to symbol values' section in the module docstring to
1232 2. If <path>/auto.conf exists, old symbol values are loaded from it,
1233 which are then compared against the current symbol values. If a
1239 won't exist, and no old symbol values will be available. This
1252 3. A new auto.conf with the current symbol values is written, to keep
1284 # Load old values from auto.conf, if any
1293 # Note: n tristate values do not get written to auto.conf and
1326 # Remember the current values as the "new old" values.
1350 # Loads old symbol values from auto.conf into a dedicated
1354 # symbol values and restoring them later, but this is simpler and
1361 # No old values
1470 Resets the user values of all symbols, as if Kconfig.load_config() or
2808 # _T_EQUAL, _T_UNEQUAL, etc., deliberately have the same values as
2847 # The default values and their conditions
3140 for sym in (self.syms.viewvalues if _IS_PY2 else self.syms.values)():
3254 A tuple containing the tristate user values that can currently be
3258 values is calculated from the symbol's visibility and selects/implies.
3261 visibility n. The other possible values are (0, 2), (0, 1, 2), (1, 2),
3290 the module documentation for an overview of symbol values and visibility.
3473 # Checking all values here instead makes more sense for us. It
3719 check which values can currently be assigned. Setting values outside
3734 values in Kconfiglib) or as one of the strings "n"/"m"/"y". For other
3737 Values that are invalid for the type (such as "foo" or 1 (m) for a
3745 values are currently in range and would actually be reflected in the
3754 # wouldn't be safe (symbol user values always match the values set in a
3769 # Display tristate values as n, m, y in the warning
3787 # choice. Like for symbol user values, the user selection is not
4012 # has cached values, because it's calculated as a side effect
4013 # of calculating all other (non-constant) cached values.
4016 # values on other items that depend on 'item', because if there
4022 # values, vs simply invalidating all possibly dependent symbols
4034 # symbol has a prompt. User values never have an effect on promptless
4052 "user values have no effect on it")
4200 See the symbol class documentation. Gives the assignable values (modes).
4370 Choice.assignable attribute to see what values are currently in range
4382 # Display tristate values as n, m, y in the warning
5074 Note that quoted values are represented as constants symbols
5217 # the values a user can set for them, corresponding to the visibility in
5904 # values can change e.g. when tokens get added. Client code would usually test
5912 # Tokens, with values 1, 2, ... . Avoiding 0 simplifies some checks by making