Same deal as in commit 7fdb525754
("kconfig: Use 'default' instead of
'def_bool' in Kconfig.defconfig files"), but I hacked Kconfiglib to also
find cases where the type is given separately as e.g.
config FOO
int
default 3
Motivation (from a note in
https://docs.zephyrproject.org/latest/guides/kconfig/index.html):
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.
It's also nice if 'def_bool' and the like turn into a semi-reliable flag
that the symbol is only defined in Kconfig.defconfig files. That might
be a sign that things could be cleaned up.
Will do a separate pass later to remove some symbols only defined in
Kconfig.defconfig files.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
43 lines
549 B
Text
43 lines
549 B
Text
# Kconfig - ST STM32F469XI MCU configuration options
|
|
#
|
|
# Copyright (c) 2016 Linaro Limited.
|
|
#
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
#
|
|
|
|
if SOC_STM32F469XX
|
|
|
|
config SOC
|
|
default "stm32f469xx"
|
|
|
|
config NUM_IRQS
|
|
int
|
|
default 93
|
|
|
|
if GPIO_STM32
|
|
|
|
config GPIO_STM32_PORTF
|
|
default y
|
|
|
|
config GPIO_STM32_PORTG
|
|
default y
|
|
|
|
config GPIO_STM32_PORTI
|
|
default y
|
|
|
|
config GPIO_STM32_PORTJ
|
|
default y
|
|
|
|
config GPIO_STM32_PORTK
|
|
default y
|
|
|
|
endif # GPIO_STM32
|
|
|
|
if ENTROPY_GENERATOR
|
|
|
|
config ENTROPY_STM32_RNG
|
|
default y
|
|
|
|
endif # ENTROPY_GENERATOR
|
|
|
|
endif # SOC_STM32F469XX
|