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

10 lines
551 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: 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/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
obj-$(CONFIG_PINMUX_STM32) += pinmux_stm32.o
pinmux: Move the Arduino 101 board to the pinmux model This driver doesn't provide any API, it only initializes the pinmux controller to appropriate values depending on the board. The first board to use this new infrastructure is the Arduino 101 board, because it is alphabetically the first. To better organize code for the different SoCs and boards, a "family" level is created in the 'drivers/pinmux' directory. The Arduino 101 board is part of the Quark MCU "family". The PINMUX_DEV configuration (and functionality) is removed for now, it will be added back when the pinmux_dev drivers are (re)introduced, with clearer semantics. Change-Id: Idf5cc3caf6be620aa50828ae8fdc535df6caf458 Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
2016-03-16 02:19:31 +08:00
obj-$(CONFIG_BOARD_ARDUINO_101) += quark_mcu/pinmux_board_arduino_101.o
pinmux: Move the Arduino Due board to the pinmux model Change-Id: I53fb54c0d11bcdbc42191dd4a26787d9beebbf58 Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
2016-03-16 02:24:45 +08:00
obj-$(CONFIG_BOARD_ARDUINO_DUE) += sam3x/pinmux_board_arduino_due.o
pinmux: Move the Galileo board to the pinmux model Change-Id: Ib58b1ea56d6c82c2e055bf4cb0df4b07b0dd936e Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
2016-03-16 02:26:14 +08:00
obj-$(CONFIG_BOARD_GALILEO) += galileo/pinmux_board_galileo.o galileo/pinmux_galileo.o
pinmux: Move the Quark D2000 board to the pinmux model Change-Id: If82e7323ffa8547bb6b090872948b5e69715b19b Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
2016-03-16 02:29:38 +08:00
obj-$(CONFIG_BOARD_QUARK_D2000_CRB) += quark_mcu/pinmux_board_quark_d2000_crb.o
pinmux: Move the Quark SE devboard to the pinmux model Change-Id: I4d10956a15c49f439b04163b1e25b33854214e21 Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
2016-03-16 02:30:31 +08:00
obj-$(CONFIG_BOARD_QUARK_SE_DEVBOARD) += quark_mcu/pinmux_board_quark_se_dev.o