2018-10-11 18:46:10 +08:00
|
|
|
# Kconfig - ST Microelectronics STM32L476RG MCU
|
|
|
|
|
#
|
|
|
|
|
# Copyright (c) 2018 Allterco Robotics
|
|
|
|
|
#
|
|
|
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
if SOC_STM32L471XX
|
|
|
|
|
|
|
|
|
|
config SOC
|
|
|
|
|
default "stm32l471xx"
|
|
|
|
|
|
|
|
|
|
config NUM_IRQS
|
|
|
|
|
default 82
|
|
|
|
|
|
|
|
|
|
if GPIO_STM32
|
|
|
|
|
|
|
|
|
|
config GPIO_STM32_PORTD
|
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-03-18 19:29:31 +08:00
|
|
|
default y
|
2018-10-11 18:46:10 +08:00
|
|
|
|
|
|
|
|
config GPIO_STM32_PORTE
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config GPIO_STM32_PORTF
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config GPIO_STM32_PORTG
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
endif # GPIO_STM32
|
|
|
|
|
|
|
|
|
|
endif # SOC_STM32L471XX
|
