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/Makefile

22 lines
946 B
Makefile
Raw Normal View History

arm: Freescale K64/FRDM-K64F Pinmux support K64 pinmux support is created as a normal driver. As opposed to the Galileo board, the pin configuration options are defined by the MCU and are not board-specific. Separate platform/board-specific configuration code uses the pinmux driver for the default pin settings. For FRDM-K64F, only the Arduino pins (22 of a possible 160) are set up. Some of the I/O pins routed to the Arduino header are also configured as JTAG/SWD signals by default and are used by the OpenSDAv2 debug interface. Therefore, a PRESERVE_JTAG_IO_PINS config option was created for the FRDM-K64 platform to prevent the default pin settings from re-configuring these pins. The K64 MCU separates pin configuration and control, implemented in the pinmux driver, from GPIO. This results in some cross referencing between the K64 GPIO driver and the K64 pinmux driver due to the dependencies of one on the other. This pinmux driver also uses the expanded pinmux function/mode parameter size to describe pin configuration options with bit fields for the K64, including up to 8 pin functions, plus interrupt, pullup/down, drive strength, open-drain and slew rate. The following GCC warnings in the K64 pinmux driver are prevented when not compiling with 'no-optimization' (-O0): warning: 'gpio_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] Change-Id: Ie5031d18750143bf895883058b3cd55fd9989fd3 Signed-off-by: Jeff Blais <jeff.blais@windriver.com>
2016-02-02 06:30:48 +08:00
ccflags-y +=-I$(srctree)/drivers
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
# Board initialization
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
ifdef CONFIG_PINMUX_K64
obj-y += k64/pinmux.o
pinmux: Rename frdm_k64f pinmux driver to k64 The k64 pinmux driver can be used for any k64 board, not just frdm_k64f, therefore renaming the driver accordingly. Change-Id: I45e96d4a5ff6aa859d0f57fe098e44a8ae5283d1 Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2016-10-09 22:56:23 +08:00
obj-$(CONFIG_BOARD_FRDM_K64F) += k64/pinmux_board_frdm_k64f.o
pinmux: Add hexiwear pinmux table The hexiwear board has a k64 SoC, so we can reuse the k64 pinmux driver and just add a new pinmux table for the board. Jira: ZEP-716 Change-Id: I936691b3578db298014f44fe18433d7943b431f3 Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
2016-10-10 01:25:35 +08:00
obj-$(CONFIG_BOARD_HEXIWEAR_K64) += k64/pinmux_board_hexiwear.o
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
endif
obj-$(CONFIG_PINMUX_KSDK) += pinmux_ksdk.o
pinmux: Move STM32 boards to the pinmux model This moves the STM32 based boards (Nucleo F103RB and STM32 Mini A15) to the "new" pinmux model. Change-Id: I190df271a6b83fafeec0b281cd4ee7cf13d7e7db Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
2016-03-22 04:14:15 +08:00
obj-$(CONFIG_PINMUX_STM32) += stm32/pinmux_stm32.o
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
obj-$(CONFIG_PINMUX_BEETLE) += beetle/pinmux_board_v2m_beetle.o
pinmux: Move STM32 boards to the pinmux model This moves the STM32 based boards (Nucleo F103RB and STM32 Mini A15) to the "new" pinmux model. Change-Id: I190df271a6b83fafeec0b281cd4ee7cf13d7e7db Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
2016-03-22 04:14:15 +08:00
obj-$(CONFIG_BOARD_NUCLEO_F103RB) += stm32/pinmux_board_nucleo_f103rb.o
boards: nucleo_f401re: add new board Add configuration for Nucleo-64 F410RE board. Change-Id: I88b06d87f0fc62b941241cc2f374b8541de86e00 Signed-off-by: Ricardo Salveti <ricardo.salveti@linaro.org> Signed-off-by: Amit Kucheria <amit.kucheria@linaro.org> Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2016-08-11 11:35:41 +08:00
obj-$(CONFIG_BOARD_NUCLEO_F401RE) += stm32/pinmux_board_nucleo_f401re.o
board: add initial support for Nucleo-64 with Soc STM32F411RE Change-Id: I698693bccce1e9599c20e57f5d4172643ca38cc9 Signed-off-by: Matthias Boesl <matthias.boesl@gmail.com>
2016-12-03 16:22:00 +08:00
obj-$(CONFIG_BOARD_NUCLEO_F411RE) += stm32/pinmux_board_nucleo_f411re.o
boards: 96b_carbon: Add support for 96boards Carbon board Add support for the STM32F401 chip on the board Change-Id: I96c0799f3658ecea096fa5971bce9faf21919ee1 Signed-off-by: Amit Kucheria <amit.kucheria@linaro.org> Signed-off-by: Ricardo Salveti <ricardo.salveti@linaro.org> Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2016-09-23 21:21:48 +08:00
obj-$(CONFIG_BOARD_96B_CARBON) += stm32/pinmux_board_carbon.o
nucleo_l476rg: add board support Add board support for the Nucleo64 L476RG development board. Change-Id: Ibb5424bc936c67a5d96855617202136d7dea772c Signed-off-by: Fabien Parent <fparent@baylibre.com> Signed-off-by: Kumar Gala <kumar.gala@linaro.org> Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2016-10-05 17:57:51 +08:00
obj-$(CONFIG_BOARD_NUCLEO_L476RG) += stm32/pinmux_board_nucleo_l476rg.o
boards/olimexino_stm32: add new board Add configuration for OLIMEXINO_STM32 board. By default, the UART console is forwarded to USART1 available on UEXT connector. All GPIO ports available on the connecot headers are enabled. Change-Id: I60b3ff20ea60b5294a3a6c31f4dba0802794f9d8 Origin: Based on nucleo_f103rb board Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2016-04-13 00:50:14 +08:00
obj-$(CONFIG_BOARD_OLIMEXINO_STM32) += stm32/pinmux_board_olimexino_stm32.o
pinmux: Move STM32 boards to the pinmux model This moves the STM32 based boards (Nucleo F103RB and STM32 Mini A15) to the "new" pinmux model. Change-Id: I190df271a6b83fafeec0b281cd4ee7cf13d7e7db Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
2016-03-22 04:14:15 +08:00
obj-$(CONFIG_BOARD_STM32_MINI_A15) += stm32/pinmux_board_stm32_mini_a15.o
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
# "runtime" pinmux
obj-$(CONFIG_PINMUX_DEV) += dev/