2 # GPIO infrastructure and expanders
5 config ARCH_WANT_OPTIONAL_GPIOLIB
8 Select this config option from the architecture Kconfig, if
9 it is possible to use gpiolib on the architecture, but let the
10 user decide whether to actually build it or not.
11 Select this instead of ARCH_REQUIRE_GPIOLIB, if your architecture does
12 not depend on GPIOs being available, but rather let the user
13 decide whether he needs it or not.
15 config ARCH_REQUIRE_GPIOLIB
19 Platforms select gpiolib if they use this infrastructure
20 for all their GPIOs, usually starting with ones integrated
22 Selecting this from the architecture code will cause the gpiolib
23 code to always get built in.
29 depends on ARCH_WANT_OPTIONAL_GPIOLIB || ARCH_REQUIRE_GPIOLIB
32 This enables GPIO support through the generic GPIO library.
33 You only need to enable this, if you also want to enable
34 one or more of the GPIO expansion card drivers below.
41 bool "Debug GPIO calls"
42 depends on DEBUG_KERNEL
44 Say Y here to add some extra checks and diagnostics to GPIO calls.
45 These checks help ensure that GPIOs have been properly initialized
46 before they are used, and that sleeping calls are not made from
47 non-sleeping contexts. They can make bitbanged serial protocols
48 slower. The diagnostics help catch the type of setup errors
49 that are most common when setting up new platforms or boards.
52 bool "/sys/class/gpio/... (sysfs interface)"
53 depends on SYSFS && EXPERIMENTAL
55 Say Y here to add a sysfs interface for GPIOs.
57 This is mostly useful to work around omissions in a system's
58 kernel support. Those are common in custom and semicustom
59 hardware assembled using standard kernels with a minimum of
60 custom patches. In those cases, userspace code may import
61 a given GPIO from the kernel, if no kernel driver requested it.
63 Kernel drivers may also request that a particular GPIO be
64 exported to userspace; this can be useful when debugging.
66 # put expanders in the right section, in alphabetical order
68 comment "Memory mapped GPIO expanders:"
71 bool "PrimeCell PL061 GPIO support"
74 Say yes here to support the PrimeCell PL061 GPIO device
77 bool "Xilinx GPIO support"
78 depends on PPC_OF || MICROBLAZE
80 Say yes here to support the Xilinx FPGA GPIO device
83 tristate "NEC VR4100 series General-purpose I/O Uint support"
86 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
88 comment "I2C GPIO expanders:"
91 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
94 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
95 Port Expanders. Each IO port on these chips has a fixed role of
96 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
97 Input and Output (designed by 'P'). The combinations are listed
100 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
101 max7322 (4I4O), max7323 (4P4O)
103 16 bits: max7324 (8I8O), max7325 (8P8O),
104 max7326 (4I12O), max7327 (4P12O)
106 Board setup code must specify the model to use, and the start
107 number for these GPIOs.
110 tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports"
113 Say yes here to provide access to several register-oriented
114 SMBus I/O expanders, made mostly by NXP or TI. Compatible
117 4 bits: pca9536, pca9537
119 8 bits: max7310, pca9534, pca9538, pca9554, pca9557,
122 16 bits: pca9535, pca9539, pca9555, tca6416
124 This driver can also be built as a module. If so, the module
125 will be called pca953x.
128 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
131 Say yes here to provide access to most "quasi-bidirectional" I2C
132 GPIO expanders used for additional digital outputs or inputs.
133 Most of these parts are from NXP, though TI is a second source for
134 some of them. Compatible models include:
136 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
137 pca9670, pca9672, pca9674, pca9674a,
140 16 bits: pcf8575, pcf8575c, pca8575,
141 pca9671, pca9673, pca9675
143 Your board setup code will need to declare the expanders in
144 use, and assign numbers to the GPIOs they expose. Those GPIOs
145 can then be used from drivers and other kernel code, just like
146 other GPIOs, but only accessible from task contexts.
148 This driver provides an in-kernel interface to those GPIOs using
149 platform-neutral GPIO calls.
152 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
153 depends on TWL4030_CORE
155 Say yes here to access the GPIO signals of various multi-function
156 power management chips from Texas Instruments.
159 bool "TPS65910 GPIOs"
160 depends on TPS65910_CORE
162 Say yes here to access the GPIO signal of TPS65910x multi-function
163 power management chips from Texas Instruments.
166 tristate "WM8994 GPIOs"
167 depends on MFD_WM8994
169 Say yes here to access the GPIO signals of WM8994 audio hub
170 CODECs from Wolfson Microelectronics.
173 tristate "WM831x GPIOs"
174 depends on MFD_WM831X
176 Say yes here to access the GPIO signals of WM831x power management
177 chips from Wolfson Microelectronics.
180 tristate "GPIO Support for ADP5520 PMIC"
181 depends on PMIC_ADP5520
183 This option enables support for on-chip GPIO found
184 on Analog Devices ADP5520 PMICs.
186 To compile this driver as a module, choose M here: the module will
187 be called adp5520-gpio.
189 comment "PCI GPIO expanders:"
192 tristate "BT8XX GPIO abuser"
193 depends on PCI && VIDEO_BT848=n
195 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
196 as a cheap PCI GPIO card.
198 This chip can be found on Miro, Hauppauge and STB TV-cards.
200 The card needs to be physically altered for using it as a
201 GPIO card. For more information on how to build a GPIO card
202 from a BT8xx TV card, see the documentation file at
203 Documentation/bt8xxgpio.txt
208 bool "Intel Moorestown Platform Langwell GPIO support"
211 Say Y here to support Intel Moorestown platform GPIO.
213 comment "SPI GPIO expanders:"
216 tristate "Maxim MAX7301 GPIO expander"
217 depends on SPI_MASTER
219 gpio driver for Maxim MAX7301 SPI GPIO expander.
222 tristate "Microchip MCP23S08 I/O expander"
223 depends on SPI_MASTER
225 SPI driver for Microchip MCP23S08 I/O expander. This provides
226 a GPIO interface supporting inputs and outputs.
229 tristate "Freescale MC33880 high-side/low-side switch"
230 depends on SPI_MASTER
232 SPI driver for Freescale MC33880 high-side/low-side switch.
233 This provides GPIO interface supporting inputs and outputs.
235 comment "AC97 GPIO expanders:"
238 bool "Philips UCB1400 GPIO"
239 depends on UCB1400_CORE
241 This enables support for the Philips UCB1400 GPIO pins.
242 The UCB1400 is an AC97 audio codec.
244 To compile this driver as a module, choose M here: the
245 module will be called ucb1400_gpio.
248 bool "GPIO EXPANDER PCA9554"
251 Say yes here to access the PCA9554 GPIO EXPANDER
253 config IOEXTEND_TCA6424
254 bool "ROCKCHIP TCA6424 CONTROL"
257 Say yes here to access the TCA6424 GPIO EXPANDER
260 config EXPANDED_GPIO_NUM
261 int "setting the amount of expanded gpios"
265 config EXPANDED_GPIO_IRQ_NUM
266 int "setting the amount of expanded gpio irqs"
269 config EXPAND_GPIO_SOFT_INTERRUPT
270 bool "soft interrupt for expand gpio use"
272 if you want expand gpio support interrupt,choose it
274 config SPI_FPGA_GPIO_NUM
276 int "setting the amount of fpga gpios"
278 for fpga, set 96,no used ,set 0
280 config SPI_FPGA_GPIO_IRQ_NUM
282 int "setting the amount of fpga gpio irqs"
284 for fpga, set 16,no used ,set 0