7089ec76b9
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>
17 lines
491 B
Plaintext
17 lines
491 B
Plaintext
# SPDX-License-Identifier: Apache-2.0
|
|
#
|
|
# Kconfig for TI CC2650 SoC pinmux driver.
|
|
|
|
config PINMUX_CC2650
|
|
bool "Pinmux driver for CC2650 SoC"
|
|
depends on SOC_SERIES_CC2650
|
|
depends on GPIO
|
|
depends on GPIO_CC2650
|
|
help
|
|
Enable pin multiplexer for CC2650 SoC.
|
|
|
|
For hardware reasons, the pinmux depends on the GPIO module
|
|
being activated; it must initialize *before* the pinmux does.
|
|
Please take care that the pinmux init priority value is *lower*
|
|
that the GPIO driver init priority.
|