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

12 lines
469 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: Move the Freescale FRDM K64F board to the pinmux model Change-Id: I50cf5fcf00481a3ebac07ced3aa6f7783765934f Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
2016-03-16 02:28:30 +08:00
obj-$(CONFIG_PINMUX_K64) += frdm_k64f/pinmux_k64.o frdm_k64f/pinmux_board_frdm_k64f.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
obj-$(CONFIG_BOARD_NUCLEO_F103RB) += stm32/pinmux_board_nucleo_f103rb.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/