blob: a5da5e7e8825f4bf3ed8f1e00f934ac997ad4608 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
|
#
# GPIO infrastructure and drivers
#
menu "GPIO Support"
config DM_GPIO
bool "Enable Driver Model for GPIO drivers"
depends on DM
help
Enable driver model for GPIO access. The standard GPIO
interface (gpio_get_value(), etc.) is then implemented by
the GPIO uclass. Drivers provide methods to query the
particular GPIOs that they provide. The uclass interface
is defined in include/asm-generic/gpio.h.
config ALTERA_PIO
bool "Altera PIO driver"
depends on DM_GPIO
help
Select this to enable PIO for Altera devices. Please find
details on the "Embedded Peripherals IP User Guide" of Altera.
config DWAPB_GPIO
bool "DWAPB GPIO driver"
depends on DM && DM_GPIO
default n
help
Support for the Designware APB GPIO driver.
config ATMEL_PIO4
bool "ATMEL PIO4 driver"
depends on DM
default n
help
Say yes here to support the Atmel PIO4 driver.
The PIO4 is new version of Atmel PIO controller, which manages
up to 128 fully programmable input/output lines. Each I/O line
may be dedicated as a general purpose I/O or be assigned to
a function of an embedded peripheral.
config INTEL_BROADWELL_GPIO
bool "Intel Broadwell GPIO driver"
depends on DM
help
This driver supports Broadwell U devices which have an expanded
GPIO feature set. The difference is large enough to merit a separate
driver from the common Intel ICH6 driver. It supports a total of
95 GPIOs which can be configured from the device tree.
config LPC32XX_GPIO
bool "LPC32XX GPIO driver"
depends on DM
default n
help
Support for the LPC32XX GPIO driver.
config ROCKCHIP_GPIO
bool "Rockchip GPIO driver"
depends on DM_GPIO
help
Support GPIO access on Rockchip SoCs. The GPIOs are arranged into
a number of banks (different for each SoC type) each with 32 GPIOs.
The GPIOs for a device are defined in the device tree with one node
for each bank.
config SANDBOX_GPIO
bool "Enable sandbox GPIO driver"
depends on SANDBOX && DM && DM_GPIO
help
This driver supports some simulated GPIOs which can be adjusted
using 'back door' functions like sandbox_gpio_set_value(). Then the
GPIOs can be inspected through the normal get_get_value()
interface. The purpose of this is to allow GPIOs to be used as
normal in sandbox, perhaps with test code actually driving the
behaviour of those GPIOs.
config SANDBOX_GPIO_COUNT
int "Number of sandbox GPIOs"
depends on SANDBOX_GPIO
default 128
help
The sandbox driver can support any number of GPIOs. Generally these
are specified using the device tree. But you can also have a number
of 'anonymous' GPIOs that do not belong to any device or bank.
Select a suitable value depending on your needs.
config GPIO_UNIPHIER
bool "UniPhier GPIO"
depends on ARCH_UNIPHIER
help
Say yes here to support UniPhier GPIOs.
config VYBRID_GPIO
bool "Vybrid GPIO driver"
depends on DM
default n
help
Say yes here to support Vybrid vf610 GPIOs.
config PIC32_GPIO
bool "Microchip PIC32 GPIO driver"
depends on DM_GPIO && MACH_PIC32
default y
help
Say yes here to support Microchip PIC32 GPIOs.
endmenu
|
