2 # GPIO infrastructure and drivers
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 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 drivers in the right section, in alphabetical order
71 comment "Memory mapped GPIO drivers:"
73 config GPIO_BASIC_MMIO
74 tristate "Basic memory-mapped GPIO controllers support"
76 Say yes here to support basic memory-mapped GPIO controllers.
79 tristate "IT8761E GPIO support"
82 Say yes here to support GPIO functionality of IT8761E super I/O chip.
85 bool "PrimeCell PL061 GPIO support"
88 Say yes here to support the PrimeCell PL061 GPIO device
91 bool "Xilinx GPIO support"
92 depends on PPC_OF || MICROBLAZE
94 Say yes here to support the Xilinx FPGA GPIO device
97 tristate "NEC VR4100 series General-purpose I/O Uint support"
100 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
103 tristate "Intel SCH/TunnelCreek GPIO"
104 depends on GPIOLIB && PCI && X86
108 Say yes here to support GPIO interface on Intel Poulsbo SCH
109 or Intel Tunnel Creek processor.
110 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
111 powered by the core power rail and are turned off during sleep
112 modes (S3 and higher). The remaining four GPIOs are powered by
113 the Intel SCH suspend power supply. These GPIOs remain
114 active during S3. The suspend powered GPIOs can be used to wake the
115 system from the Suspend-to-RAM state.
116 The Intel Tunnel Creek processor has 5 GPIOs powered by the
117 core power rail and 9 from suspend power supply.
119 This driver can also be built as a module. If so, the module
120 will be called sch-gpio.
123 bool "ST-Ericsson U300 COH 901 335/571 GPIO"
124 depends on GPIOLIB && ARCH_U300
126 Say yes here to support GPIO interface on ST-Ericsson U300.
127 The names of the two IP block variants supported are
128 COH 901 335 and COH 901 571/3. They contain 3, 5 or 7
129 ports of 8 GPIO pins each.
132 bool "ST-Ericsson Nomadik GPIO"
133 depends on GPIOLIB && (ARCH_U8500 || ARCH_NOMADIK)
135 Say yes here to support GPIO interface for ST-Ericsson Nomadik.
136 This is found in the Nomadik NHK8815, DB8500, DB5500 SoCs
140 tristate "VIA VX855/VX875 GPIO"
141 depends on GPIOLIB && MFD_SUPPORT && PCI
145 Support access to the VX855/VX875 GPIO lines through the gpio library.
147 This driver provides common support for accessing the device,
148 additional drivers must be enabled in order to use the
149 functionality of the device.
151 comment "I2C GPIO expanders:"
154 tristate "Maxim MAX7300 GPIO expander"
158 GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
161 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
164 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
165 Port Expanders. Each IO port on these chips has a fixed role of
166 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
167 Input and Output (designed by 'P'). The combinations are listed
170 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
171 max7322 (4I4O), max7323 (4P4O)
173 16 bits: max7324 (8I8O), max7325 (8P8O),
174 max7326 (4I12O), max7327 (4P12O)
176 Board setup code must specify the model to use, and the start
177 number for these GPIOs.
179 config GPIO_MAX732X_IRQ
180 bool "Interrupt controller support for MAX732x"
181 depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
183 Say yes here to enable the max732x to be used as an interrupt
184 controller. It requires the driver to be built in the kernel.
187 tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports"
190 Say yes here to provide access to several register-oriented
191 SMBus I/O expanders, made mostly by NXP or TI. Compatible
194 4 bits: pca9536, pca9537
196 8 bits: max7310, pca9534, pca9538, pca9554, pca9557,
199 16 bits: pca9535, pca9539, pca9555, tca6416
201 This driver can also be built as a module. If so, the module
202 will be called pca953x.
204 config GPIO_PCA953X_IRQ
205 bool "Interrupt controller support for PCA953x"
206 depends on GPIO_PCA953X=y
208 Say yes here to enable the pca953x to be used as an interrupt
209 controller. It requires the driver to be built in the kernel.
212 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
215 Say yes here to provide access to most "quasi-bidirectional" I2C
216 GPIO expanders used for additional digital outputs or inputs.
217 Most of these parts are from NXP, though TI is a second source for
218 some of them. Compatible models include:
220 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
221 pca9670, pca9672, pca9674, pca9674a,
224 16 bits: pcf8575, pcf8575c, pca8575,
225 pca9671, pca9673, pca9675
227 Your board setup code will need to declare the expanders in
228 use, and assign numbers to the GPIOs they expose. Those GPIOs
229 can then be used from drivers and other kernel code, just like
230 other GPIOs, but only accessible from task contexts.
232 This driver provides an in-kernel interface to those GPIOs using
233 platform-neutral GPIO calls.
236 bool "Semtech SX150x I2C GPIO expander"
240 Say yes here to provide support for Semtech SX150-series I2C
241 GPIO expanders. Compatible models include:
250 This enables support for the GPIOs found on the STMPE I/O
255 depends on MFD_TC3589X
257 This enables support for the GPIOs found on the TC3589X
261 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
262 depends on TWL4030_CORE
264 Say yes here to access the GPIO signals of various multi-function
265 power management chips from Texas Instruments.
268 tristate "WM831x GPIOs"
269 depends on MFD_WM831X
271 Say yes here to access the GPIO signals of WM831x power management
272 chips from Wolfson Microelectronics.
275 tristate "WM8350 GPIOs"
276 depends on MFD_WM8350
278 Say yes here to access the GPIO signals of WM8350 power management
279 chips from Wolfson Microelectronics.
282 tristate "WM8994 GPIOs"
283 depends on MFD_WM8994
285 Say yes here to access the GPIO signals of WM8994 audio hub
286 CODECs from Wolfson Microelectronics.
289 tristate "GPIO Support for ADP5520 PMIC"
290 depends on PMIC_ADP5520
292 This option enables support for on-chip GPIO found
293 on Analog Devices ADP5520 PMICs.
295 To compile this driver as a module, choose M here: the module will
296 be called adp5520-gpio.
299 tristate "ADP5588 I2C GPIO expander"
302 This option enables support for 18 GPIOs found
303 on Analog Devices ADP5588 GPIO Expanders.
304 To compile this driver as a module, choose M here: the module will be
307 config GPIO_ADP5588_IRQ
308 bool "Interrupt controller support for ADP5588"
309 depends on GPIO_ADP5588=y
311 Say yes here to enable the adp5588 to be used as an interrupt
312 controller. It requires the driver to be built in the kernel.
314 comment "PCI GPIO expanders:"
317 tristate "AMD CS5535/CS5536 GPIO support"
318 depends on PCI && X86 && !CS5535_GPIO
320 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
321 can be used for quite a number of things. The CS5535/6 is found on
322 AMD Geode and Lemote Yeeloong devices.
327 tristate "BT8XX GPIO abuser"
328 depends on PCI && VIDEO_BT848=n
330 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
331 as a cheap PCI GPIO card.
333 This chip can be found on Miro, Hauppauge and STB TV-cards.
335 The card needs to be physically altered for using it as a
336 GPIO card. For more information on how to build a GPIO card
337 from a BT8xx TV card, see the documentation file at
338 Documentation/bt8xxgpio.txt
343 bool "Intel Langwell/Penwell GPIO support"
344 depends on PCI && X86
346 Say Y here to support Intel Langwell/Penwell GPIO.
349 tristate "PCH GPIO of Intel Topcliff"
350 depends on PCI && X86
352 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
353 which is an IOH(Input/Output Hub) for x86 embedded processor.
354 This driver can access PCH GPIO device.
357 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
360 ML7213 is companion chip for Intel Atom E6xx series.
361 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
362 Hub) which is for IVI(In-Vehicle Infotainment) use.
363 This driver can access the IOH's GPIO device.
365 config GPIO_TIMBERDALE
366 bool "Support for timberdale GPIO IP"
367 depends on MFD_TIMBERDALE && GPIOLIB && HAS_IOMEM
369 Add support for the GPIO IP in the timberdale FPGA.
372 tristate "RDC R-321x GPIO support"
373 depends on PCI && GPIOLIB
378 Support for the RDC R321x SoC GPIOs over southbridge
379 PCI configuration space.
381 comment "SPI GPIO expanders:"
384 tristate "Maxim MAX7301 GPIO expander"
385 depends on SPI_MASTER
388 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
391 tristate "Microchip MCP23Sxx I/O expander"
392 depends on SPI_MASTER
394 SPI driver for Microchip MCP23S08/MPC23S17 I/O expanders.
395 This provides a GPIO interface supporting inputs and outputs.
398 tristate "Freescale MC33880 high-side/low-side switch"
399 depends on SPI_MASTER
401 SPI driver for Freescale MC33880 high-side/low-side switch.
402 This provides GPIO interface supporting inputs and outputs.
405 tristate "74x164 serial-in/parallel-out 8-bits shift register"
406 depends on SPI_MASTER
408 Platform driver for 74x164 compatible serial-in/parallel-out
409 8-outputs shift registers. This driver can be used to provide access
410 to more gpio outputs.
412 comment "AC97 GPIO expanders:"
415 bool "Philips UCB1400 GPIO"
416 depends on UCB1400_CORE
418 This enables support for the Philips UCB1400 GPIO pins.
419 The UCB1400 is an AC97 audio codec.
421 To compile this driver as a module, choose M here: the
422 module will be called ucb1400_gpio.
424 comment "MODULbus GPIO expanders:"
427 tristate "Janz VMOD-TTL Digital IO Module"
428 depends on MFD_JANZ_CMODIO
430 This enables support for the Janz VMOD-TTL Digital IO module.
431 This driver provides support for driving the pins in output
432 mode only. Input mode is not supported.
435 bool "ST-Ericsson AB8500 Mixed Signal Circuit gpio functions"
436 depends on AB8500_CORE && BROKEN
438 Select this to enable the AB8500 IC GPIO driver