OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/drivers/pinmux/Kconfig

56 lines
1.2 KiB
Plaintext
Raw Normal View History

pinmux: Add API for pinmux driver This provides the API to manipulte the pin muxing, where a single pin may provide different functions depending on settings. [DL: changed commit message.] Change-Id: Ifd161137c062dff184024b5aa34737604911d09c Signed-off-by: Dan Kalowsky <daniel.kalowsky@intel.com> Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2015-09-25 01:57:06 +08:00
# Kconfig - Pinmux configuration options
#
# Copyright (c) 2015 Intel Corporation
#
license: Replace Apache boilerplate with SPDX tag Replace the existing Apache 2.0 boilerplate header with an SPDX tag throughout the zephyr code tree. This patch was generated via a script run over the master branch. Also updated doc/porting/application.rst that had a dependency on line numbers in a literal include. Manually updated subsys/logging/sys_log.c that had a malformed header in the original file. Also cleanup several cases that already had a SPDX tag and we either got a duplicate or missed updating. Jira: ZEP-1457 Change-Id: I6131a1d4ee0e58f5b938300c2d2fc77d2e69572c Signed-off-by: David B. Kinder <david.b.kinder@intel.com> Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-01-19 09:01:01 +08:00
# SPDX-License-Identifier: Apache-2.0
pinmux: Add API for pinmux driver This provides the API to manipulte the pin muxing, where a single pin may provide different functions depending on settings. [DL: changed commit message.] Change-Id: Ifd161137c062dff184024b5aa34737604911d09c Signed-off-by: Dan Kalowsky <daniel.kalowsky@intel.com> Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2015-09-25 01:57:06 +08:00
#
#
# PinMux options
#
menuconfig PINMUX
doc: Fix terminology in Kconfig files for 'platform' Completing the terminology change started with change 4008 by updating the Kconfig files processed to produce the online documentation, plus header files processed by doxygen. References to 'platform' are change to 'board' Change-Id: Id0ed3dc1439a0ea0a4bd19d4904889cf79bec33e Jira: ZEP-534 Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
2016-08-18 07:33:08 +08:00
bool "Enable board pinmux driver"
Cleanup whitespace in Kconfig files Convert leading whitespace into tabs in Kconfig files. Also replaced double spaces between config and <prompt>. Change-Id: I341c718ecf4143529b477c239bbde88e18f37062 Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2016-05-25 07:17:13 +08:00
default n
pinmux: Add API for pinmux driver This provides the API to manipulte the pin muxing, where a single pin may provide different functions depending on settings. [DL: changed commit message.] Change-Id: Ifd161137c062dff184024b5aa34737604911d09c Signed-off-by: Dan Kalowsky <daniel.kalowsky@intel.com> Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2015-09-25 01:57:06 +08:00
drivers: pinmux: Restructure kconfig options Moves config options for K64 into its own config file under its own submenu. Change-Id: I94ccac54709ab5ec8222daa8634818d9ebc3561d Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2016-03-22 16:59:39 +08:00
if PINMUX
pinmux_dev: Add the pinmux_dev driver for Atmel SAM3X This introduces the pinmux_dev driver for the Atmel SAM3X. This driver implements what used to be the pinmux driver API, which applications could use to modify the function of pins during runtime. That functionality is now protected under the CONFIG_PINMUX_DEV option, which should only be set during the early enabling of a new board, as there is risk of damage to the board when misused. Change-Id: I3aa00505d2771b53c41fe687c3e5230e804756be Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
2016-03-16 02:43:38 +08:00
source "drivers/pinmux/dev/Kconfig"
pinmux: fix naming inconsistency Jira: ZEP-288 Change-Id: Ie9bfd3ac95305a35c96453448d13d6b4cd6c0f0b Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-05-20 21:26:22 +08:00
config PINMUX_NAME
More cleanup whitespace in Kconfig files Some additional whitespace converted to TABs Change-Id: I945383f70960ad97e9cbc11ea96b099bcc558404 Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2016-06-02 02:46:14 +08:00
string "Pinmux driver name"
depends on PINMUX
default "PINMUX"
help
The name of the pinmux driver.
pinmux: fix naming inconsistency Jira: ZEP-288 Change-Id: Ie9bfd3ac95305a35c96453448d13d6b4cd6c0f0b Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-05-20 21:26:22 +08:00
init: Implement fine-grained initialization policy Put initialization priorities as device driver Kconfig parameter. Initialization priority value for each platform is defined in the platform Kconfig file. Drivers and platform code use SYS_DEFINE_DEVICE to add and initialization function. Change-Id: I2f4f3c7370dac02408a1b50a0a1bade8b427a282 Signed-off-by: Dmitriy Korovkin <dmitriy.korovkin@windriver.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com>
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
init: Implement fine-grained initialization policy Put initialization priorities as device driver Kconfig parameter. Initialization priority value for each platform is defined in the platform Kconfig file. Drivers and platform code use SYS_DEFINE_DEVICE to add and initialization function. Change-Id: I2f4f3c7370dac02408a1b50a0a1bade8b427a282 Signed-off-by: Dmitriy Korovkin <dmitriy.korovkin@windriver.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com>
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.
init: Implement fine-grained initialization policy Put initialization priorities as device driver Kconfig parameter. Initialization priority value for each platform is defined in the platform Kconfig file. Drivers and platform code use SYS_DEFINE_DEVICE to add and initialization function. Change-Id: I2f4f3c7370dac02408a1b50a0a1bade8b427a282 Signed-off-by: Dmitriy Korovkin <dmitriy.korovkin@windriver.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-10-27 03:56:02 +08:00
pinmux: make pinmux_dev the default pinmux driver for quark Jira: ZEP-958 Change-Id: Ib6c528a103372d5084efa5ae8635803e2912e0dd Signed-off-by: Anas Nashif <anas.nashif@intel.com>
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.
pinmux: Rename ksdk to mcux Renames the ksdk pinmux driver to mcux. Change-Id: I7a519318b5b580c47b6f6652a2ae763067d85033 Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2017-01-03 05:07:42 +08:00
source "drivers/pinmux/Kconfig.mcux"
pinmux: Introduce new ksdk pinmux driver Kinetis SoCs contain one or more PORT modules to handle pin muxing and pin configuration. Unlike the existing k64 pinmux driver, this driver handles each PORT module individually and can be used for other Kinetis SoCs. This driver uses KSDK CMSIS register accesses to the PORT module rather than the KSDK PORT driver (fsl_port.h), because the Zephyr pinmux interface contains both set() and get() functions to access the pin configuration. The KSDK PORT driver only contains a set() function (which is a very thin static inline function to modify the PCR register), therefore building a shim on top of it would result in a strange mix of using the KSDK PORT driver for the set() and a direct CMSIS register access for the get(). Jira: ZEP-1393 Change-Id: I2f7c6b08b207350697d590dcd665223f81de9f9e Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2016-11-23 23:10:03 +08:00
pinmux/stm32: add common driver for STM32 pinmux Add a common driver for pin control subsystem in STM32 MCU series. The driver allows for selection of pin's function without the ability of pin remapping. The driver implements a pinmux driver API, with custom `func` and `pin` encoding in API calls. The caller is expected to use STM32PIN() helper macro for encoding port/pin numbers or using one of the provided STM32_PIN_* defines. The common driver requires SoC specific support to be implemented. The SoC code must implement these calls: stm32_get_pin_config(), stm32_get_port_clock(), stm32_pin_configure(). Consult pinmux_stm32.h header for detailn on semantics of these calls. The driver also requires board level integration. The call stm32_board_get_pinconf() is expected to privide pin function assignments for the target board. Whenever an IO pin is being enabled, the driver will automatically enable the clock for corresponding port. The driver does not implement disabling of port's clock as this has potentially disruptive, as such such operation should be done explicitly in the code. The pin control module needs to be initialized before any other modules, but after clock_control. For this reason, the driver is initialized by default at PRIMARY level, with priority set to 2. The priority can be changed through configuration. Change-Id: I8cb746d0f3cad72cd50b3355fe6d93a9f469be25 Origin: Original Signed-off-by: Maciej Borzecki <maciek.borzecki@gmail.com>
2016-03-03 22:33:15 +08:00
source "drivers/pinmux/Kconfig.stm32"
drivers: pinmux: Restructure kconfig options Moves config options for K64 into its own config file under its own submenu. Change-Id: I94ccac54709ab5ec8222daa8634818d9ebc3561d Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2016-03-22 16:59:39 +08:00
pinmux: Add support for ARM V2M Beetle Initialization This patch adds the support for the board pinmux initialization on ARM V2M Beetle. The GPIO controllers 2 and 3 are reserved and therefore neither exposed nor configured by this driver. Jira: ZEP-1245 Change-Id: Id5499c5dd887c319730408eeb30f02eeed1c3699 Signed-off-by: Vincenzo Frascino <vincenzo.frascino@linaro.org> Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2016-09-08 17:54:21 +08:00
source "drivers/pinmux/Kconfig.beetle"
drivers: pinmux: Restructure kconfig options Moves config options for K64 into its own config file under its own submenu. Change-Id: I94ccac54709ab5ec8222daa8634818d9ebc3561d Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2016-03-22 16:59:39 +08:00
endif # PINMUX