zephyr/drivers/pinmux/Kconfig.stm32
Ulf Magnusson 7089ec76b9 kconfig: pinmux: Remove lots of redundant PINMUX dependencies
Most of these are from source'ing a file within an 'if PINMUX', and then
adding another 'depends on PINMUX' within it.

'if FOO' is just shorthand for adding 'depends on FOO' to each item
within the 'if'. There are no "conditional includes" in Kconfig, so
'if FOO' has no special meaning around a 'source'. Conditional includes
wouldn't be possible, because an 'if' condition could include (directly
or indirectly) forward references to symbols not defined yet.

Tip: When adding a symbol, check its dependencies in the menuconfig
('ninja menuconfig', then / to jump to the symbol). The menuconfig also
shows how the file with the symbol got included, so if you see
duplicated dependencies, it's easy to hunt down where they come from.

Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-03-07 08:47:31 -05:00

24 lines
723 B
Plaintext

# Kconfig - configuration for STM32 pinmux
#
# Copyright (c) 2016 Open-RnD Sp. z o.o.
#
# SPDX-License-Identifier: Apache-2.0
#
config PINMUX_STM32
bool "Pinmux driver for STM32 MCUs"
depends on SOC_FAMILY_STM32
help
Enable pin multiplexer for STM32 MCUs
config PINMUX_STM32_DEVICE_INITIALIZATION_PRIORITY
int "Device initialization priority STM32 pinmux"
depends on PINMUX_STM32
default 2
help
This option controls the priority of pinmux device initialization.
Higher priority ensures that the device is initialized earlier in
the startup cycle. Note that the pinmux device needs to be initialized
after clock control device, but possibly before all other devices.
If unsure, leave at default value 2