zephyr/boards/arm/mec2016evb_assy6797
Ulf Magnusson 7fdb525754 kconfig: Use 'default' instead of 'def_bool' in Kconfig.defconfig files
Same deal as in commit 4638652214 ("Kconfig: Use 'default' instead of
'def_bool' in Kconfig.defconfig files"), fixing new stuff that got
introduced since then.

Some symbols, like ALTERA_AVALON_PIO, are only defined in
Kconfig.defconfig files, and so need the def_bool.

Motivation (from the note at the end of
guides/kconfig/index.html#common-shorthands):

For a symbol defined in multiple locations (e.g., in a Kconfig.defconfig
file in Zephyr), it is best to only give the symbol type for the "base"
definition of the symbol, and to use 'default' (instead of 'def_<type>'
value) for the remaining definitions. That way, if the base definition
of the symbol is removed, the symbol ends up without a type, which
generates a warning that points to the other definitions. That makes the
extra definitions easier to discover and remove.

Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-04-18 12:20:49 -04:00
..
doc doc: prepare for improving doc API linking 2019-03-15 05:47:19 +01:00
CMakeLists.txt
Kconfig.board
Kconfig.defconfig kconfig: Use 'default' instead of 'def_bool' in Kconfig.defconfig files 2019-04-18 12:20:49 -04:00
mec2016evb_assy6797.dts
mec2016evb_assy6797.yaml
mec2016evb_assy6797_defconfig
pinmux.c