projects / people / ms / u-boot.git / blame
| Commit | Line | Data |
|---|---|---|
| 0b11dbf7 MY |
1 | # |
| 2 | # GPIO infrastructure and drivers | |
| 3 | # | |
| 4 | ||
| 5 | menu "GPIO Support" | |
| 6 | ||
| da333ae7 MY |
7 | config DM_GPIO |
| 8 | bool "Enable Driver Model for GPIO drivers" | |
| 9 | depends on DM | |
| 10 | help | |
| f94a1bed SG |
11 | Enable driver model for GPIO access. The standard GPIO |
| 12 | interface (gpio_get_value(), etc.) is then implemented by | |
| 13 | the GPIO uclass. Drivers provide methods to query the | |
| 14 | particular GPIOs that they provide. The uclass interface | |
| 15 | is defined in include/asm-generic/gpio.h. | |
| 606f7047 | 16 | |
| 88d5ecf4 TC |
17 | config ALTERA_PIO |
| 18 | bool "Altera PIO driver" | |
| 19 | depends on DM_GPIO | |
| 20 | help | |
| 21 | Select this to enable PIO for Altera devices. Please find | |
| 22 | details on the "Embedded Peripherals IP User Guide" of Altera. | |
| 23 | ||
| e30a70c2 MV |
24 | config DWAPB_GPIO |
| 25 | bool "DWAPB GPIO driver" | |
| 26 | depends on DM && DM_GPIO | |
| 27 | default n | |
| 28 | help | |
| 29 | Support for the Designware APB GPIO driver. | |
| 30 | ||
| 2c62c56a WY |
31 | config ATMEL_PIO4 |
| 32 | bool "ATMEL PIO4 driver" | |
| 33 | depends on DM | |
| 34 | default n | |
| 35 | help | |
| 36 | Say yes here to support the Atmel PIO4 driver. | |
| 37 | The PIO4 is new version of Atmel PIO controller, which manages | |
| 38 | up to 128 fully programmable input/output lines. Each I/O line | |
| 39 | may be dedicated as a general purpose I/O or be assigned to | |
| 40 | a function of an embedded peripheral. | |
| 41 | ||
| 606f7047 AA |
42 | config LPC32XX_GPIO |
| 43 | bool "LPC32XX GPIO driver" | |
| 44 | depends on DM | |
| 45 | default n | |
| 46 | help | |
| 47 | Support for the LPC32XX GPIO driver. | |
| d79c50af | 48 | |
| 1f8f7730 SG |
49 | config ROCKCHIP_GPIO |
| 50 | bool "Rockchip GPIO driver" | |
| 51 | depends on DM_GPIO | |
| 52 | help | |
| 53 | Support GPIO access on Rockchip SoCs. The GPIOs are arranged into | |
| 54 | a number of banks (different for each SoC type) each with 32 GPIOs. | |
| 55 | The GPIOs for a device are defined in the device tree with one node | |
| 56 | for each bank. | |
| 57 | ||
| d79c50af SG |
58 | config SANDBOX_GPIO |
| 59 | bool "Enable sandbox GPIO driver" | |
| 60 | depends on SANDBOX && DM && DM_GPIO | |
| 61 | help | |
| 62 | This driver supports some simulated GPIOs which can be adjusted | |
| 63 | using 'back door' functions like sandbox_gpio_set_value(). Then the | |
| 64 | GPIOs can be inspected through the normal get_get_value() | |
| 65 | interface. The purpose of this is to allow GPIOs to be used as | |
| 66 | normal in sandbox, perhaps with test code actually driving the | |
| 67 | behaviour of those GPIOs. | |
| 68 | ||
| 69 | config SANDBOX_GPIO_COUNT | |
| 70 | int "Number of sandbox GPIOs" | |
| 71 | depends on SANDBOX_GPIO | |
| 72 | default 128 | |
| 73 | help | |
| 74 | The sandbox driver can support any number of GPIOs. Generally these | |
| 75 | are specified using the device tree. But you can also have a number | |
| 76 | of 'anonymous' GPIOs that do not belong to any device or bank. | |
| 77 | Select a suitable value depending on your needs. | |
| d348a943 BD |
78 | |
| 79 | config VYBRID_GPIO | |
| 80 | bool "Vybrid GPIO driver" | |
| 81 | depends on DM | |
| 82 | default n | |
| 83 | help | |
| 84 | Say yes here to support Vybrid vf610 GPIOs. | |
| 0b11dbf7 MY |
85 | |
| 86 | endmenu |