2015-09-25 01:57:06 +08:00
|
|
|
# Kconfig - Pinmux configuration options
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Copyright (c) 2015 Intel Corporation
|
|
|
|
|
#
|
2017-01-19 09:01:01 +08:00
|
|
|
# SPDX-License-Identifier: Apache-2.0
|
2015-09-25 01:57:06 +08:00
|
|
|
#
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# PinMux options
|
|
|
|
|
#
|
|
|
|
|
menuconfig PINMUX
|
2016-08-18 07:33:08 +08:00
|
|
|
bool "Enable board pinmux driver"
|
2016-05-25 07:17:13 +08:00
|
|
|
default n
|
2015-09-25 01:57:06 +08:00
|
|
|
|
2016-03-22 16:59:39 +08:00
|
|
|
if PINMUX
|
|
|
|
|
|
2016-03-16 02:43:38 +08:00
|
|
|
source "drivers/pinmux/dev/Kconfig"
|
|
|
|
|
|
2016-05-20 21:26:22 +08:00
|
|
|
config PINMUX_NAME
|
2016-06-02 02:46:14 +08:00
|
|
|
string "Pinmux driver name"
|
|
|
|
|
depends on PINMUX
|
|
|
|
|
default "PINMUX"
|
|
|
|
|
help
|
2017-12-13 23:08:21 +08:00
|
|
|
The name of the pinmux driver.
|
2016-05-20 21:26:22 +08:00
|
|
|
|
2015-10-27 03:56:02 +08:00
|
|
|
config PINMUX_INIT_PRIORITY
|
|
|
|
|
int
|
|
|
|
|
prompt "Init priority"
|
pinmux: Make default init priority be between GPIO's prio and device prio.
Pinmux driver almost certainly should be initialized before the
rest of hardware devices (which may need specific pins already
configured for them), and usually after generic GPIO drivers.
Thus, its priority should be between KERNEL_INIT_PRIORITY_DEFAULT
(default 40) and KERNEL_INIT_PRIORITY_DEVICE (default 50). Thus,
we set PINMUX_INIT_PRIORITY to 45.
There are exceptions to the rule above for particular boards. For
example, BOARD=galileo has GPIO and pinmuxer on I2C bus and thus
overrides PINMUX_INIT_PRIORITY to be much higher. Note that while
PINMUX_INIT_PRIORITY was defined previously (at 60), it was used
only for galileo, which overrides it anyway.
This fix was prompted by investigation why eth_ksdk driver was
non-functional after kernel priorities re-hashing: both eth_ksdk
and pinmux used the same priority, and eth_ksdk happened to run
before pinmux. While bumping eth_ksdk priority would help in the
particular case, the same would likely reoccur with other drivers
like I2C, SPI, etc.
Change-Id: Ie5ca3135c1ee2fe8d9cf48d5c12e62eac63487f7
Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
2016-11-11 23:13:59 +08:00
|
|
|
default 45
|
2015-10-27 03:56:02 +08:00
|
|
|
depends on PINMUX
|
|
|
|
|
help
|
pinmux: Make default init priority be between GPIO's prio and device prio.
Pinmux driver almost certainly should be initialized before the
rest of hardware devices (which may need specific pins already
configured for them), and usually after generic GPIO drivers.
Thus, its priority should be between KERNEL_INIT_PRIORITY_DEFAULT
(default 40) and KERNEL_INIT_PRIORITY_DEVICE (default 50). Thus,
we set PINMUX_INIT_PRIORITY to 45.
There are exceptions to the rule above for particular boards. For
example, BOARD=galileo has GPIO and pinmuxer on I2C bus and thus
overrides PINMUX_INIT_PRIORITY to be much higher. Note that while
PINMUX_INIT_PRIORITY was defined previously (at 60), it was used
only for galileo, which overrides it anyway.
This fix was prompted by investigation why eth_ksdk driver was
non-functional after kernel priorities re-hashing: both eth_ksdk
and pinmux used the same priority, and eth_ksdk happened to run
before pinmux. While bumping eth_ksdk priority would help in the
particular case, the same would likely reoccur with other drivers
like I2C, SPI, etc.
Change-Id: Ie5ca3135c1ee2fe8d9cf48d5c12e62eac63487f7
Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
2016-11-11 23:13:59 +08:00
|
|
|
Pinmux driver initialization priority.
|
|
|
|
|
Pinmux driver almost certainly should be initialized before the
|
|
|
|
|
rest of hardware devices (which may need specific pins already
|
|
|
|
|
configured for them), and usually after generic GPIO drivers.
|
|
|
|
|
Thus, its priority should be between KERNEL_INIT_PRIORITY_DEFAULT
|
|
|
|
|
and KERNEL_INIT_PRIORITY_DEVICE. There are exceptions to this
|
|
|
|
|
rule for particular boards. Don't change this value unless you
|
|
|
|
|
know what you are doing.
|
2015-10-27 03:56:02 +08:00
|
|
|
|
2017-01-25 20:42:47 +08:00
|
|
|
config PINMUX_QMSI
|
|
|
|
|
bool "Enable QMSI pinmux dev driver"
|
|
|
|
|
depends on PINMUX && QMSI
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Enables the pinmux dev driver for QMSI supported boards.
|
|
|
|
|
|
2017-01-03 05:07:42 +08:00
|
|
|
source "drivers/pinmux/Kconfig.mcux"
|
2016-11-23 23:10:03 +08:00
|
|
|
|
2017-07-26 19:36:39 +08:00
|
|
|
source "drivers/pinmux/Kconfig.mcux_lpc"
|
|
|
|
|
|
2016-03-03 22:33:15 +08:00
|
|
|
source "drivers/pinmux/Kconfig.stm32"
|
2016-03-22 16:59:39 +08:00
|
|
|
|
2016-09-08 17:54:21 +08:00
|
|
|
source "drivers/pinmux/Kconfig.beetle"
|
|
|
|
|
|
2017-03-15 05:16:15 +08:00
|
|
|
source "drivers/pinmux/Kconfig.fe310"
|
|
|
|
|
|
2017-06-16 23:42:07 +08:00
|
|
|
source "drivers/pinmux/Kconfig.cc2650"
|
|
|
|
|
|
2017-06-27 08:07:43 +08:00
|
|
|
source "drivers/pinmux/Kconfig.esp32"
|
|
|
|
|
|
2018-01-31 03:37:46 +08:00
|
|
|
source "drivers/pinmux/Kconfig.sam0"
|
|
|
|
|
|
2016-03-22 16:59:39 +08:00
|
|
|
endif # PINMUX
|