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.stm32

24 lines
723 B
Plaintext
Raw Normal View History

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
# Kconfig - configuration for STM32 pinmux
#
# Copyright (c) 2016 Open-RnD Sp. z o.o.
#
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/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
#
config PINMUX_STM32
bool "Pinmux driver for STM32 MCUs"
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 12:54:37 +08:00
depends on SOC_FAMILY_STM32
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
help
spell: fix Kconfig help typos: /boards /drivers Fix misspellings in Kconfig help text Change-Id: I3ae28a5d23d8e266612114bc0eb8a6e158129dc7 Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
2017-04-22 01:29:51 +08:00
Enable pin multiplexer for STM32 MCUs
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
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