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.
69 # put drivers in the right section, in alphabetical order
72 tristate "Dialog DA9052 GPIO"
73 depends on PMIC_DA9052
75 Say yes here to enable the GPIO driver for the DA9052 chip.
80 comment "Memory mapped GPIO drivers:"
82 config GPIO_GENERIC_PLATFORM
83 tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
86 Say yes here to support basic platform_device memory-mapped GPIO controllers.
89 tristate "IT8761E GPIO support"
91 Say yes here to support GPIO functionality of IT8761E super I/O chip.
95 depends on ARCH_EP93XX
100 depends on CPU_EXYNOS4210
104 depends on PPC_MPC52xx
107 tristate "Qualcomm MSM GPIO v1"
108 depends on GPIOLIB && ARCH_MSM
110 Say yes here to support the GPIO interface on ARM v6 based
111 Qualcomm MSM chips. Most of the pins on the MSM can be
112 selected for GPIO, and are controlled by this driver.
115 tristate "Qualcomm MSM GPIO v2"
116 depends on GPIOLIB && ARCH_MSM
118 Say yes here to support the GPIO interface on ARM v7 based
119 Qualcomm MSM chips. Most of the pins on the MSM can be
120 selected for GPIO, and are controlled by this driver.
126 select GENERIC_IRQ_CHIP
132 select GENERIC_IRQ_CHIP
134 config GPIO_PLAT_SAMSUNG
136 depends on SAMSUNG_GPIOLIB_4BIT
140 depends on CPU_S5PC100
144 depends on CPU_S5PV210
147 bool "PrimeCell PL061 GPIO support"
150 Say yes here to support the PrimeCell PL061 GPIO device
153 bool "Xilinx GPIO support"
154 depends on PPC_OF || MICROBLAZE
156 Say yes here to support the Xilinx FPGA GPIO device
159 tristate "NEC VR4100 series General-purpose I/O Uint support"
160 depends on CPU_VR41XX
162 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
165 tristate "Intel SCH/TunnelCreek GPIO"
166 depends on PCI && X86
170 Say yes here to support GPIO interface on Intel Poulsbo SCH
171 or Intel Tunnel Creek processor.
172 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
173 powered by the core power rail and are turned off during sleep
174 modes (S3 and higher). The remaining four GPIOs are powered by
175 the Intel SCH suspend power supply. These GPIOs remain
176 active during S3. The suspend powered GPIOs can be used to wake the
177 system from the Suspend-to-RAM state.
178 The Intel Tunnel Creek processor has 5 GPIOs powered by the
179 core power rail and 9 from suspend power supply.
182 tristate "VIA VX855/VX875 GPIO"
183 depends on MFD_SUPPORT && PCI
187 Support access to the VX855/VX875 GPIO lines through the gpio library.
189 This driver provides common support for accessing the device,
190 additional drivers must be enabled in order to use the
191 functionality of the device.
193 comment "I2C GPIO expanders:"
196 tristate "Maxim MAX7300 GPIO expander"
200 GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
203 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
206 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
207 Port Expanders. Each IO port on these chips has a fixed role of
208 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
209 Input and Output (designed by 'P'). The combinations are listed
212 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
213 max7322 (4I4O), max7323 (4P4O)
215 16 bits: max7324 (8I8O), max7325 (8P8O),
216 max7326 (4I12O), max7327 (4P12O)
218 Board setup code must specify the model to use, and the start
219 number for these GPIOs.
221 config GPIO_MAX732X_IRQ
222 bool "Interrupt controller support for MAX732x"
223 depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
225 Say yes here to enable the max732x to be used as an interrupt
226 controller. It requires the driver to be built in the kernel.
229 tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports"
232 Say yes here to provide access to several register-oriented
233 SMBus I/O expanders, made mostly by NXP or TI. Compatible
236 4 bits: pca9536, pca9537
238 8 bits: max7310, pca9534, pca9538, pca9554, pca9557,
241 16 bits: pca9535, pca9539, pca9555, tca6416
243 config GPIO_PCA953X_IRQ
244 bool "Interrupt controller support for PCA953x"
245 depends on GPIO_PCA953X=y
247 Say yes here to enable the pca953x to be used as an interrupt
248 controller. It requires the driver to be built in the kernel.
251 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
254 Say yes here to provide access to most "quasi-bidirectional" I2C
255 GPIO expanders used for additional digital outputs or inputs.
256 Most of these parts are from NXP, though TI is a second source for
257 some of them. Compatible models include:
259 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
260 pca9670, pca9672, pca9674, pca9674a,
263 16 bits: pcf8575, pcf8575c, pca8575,
264 pca9671, pca9673, pca9675
266 Your board setup code will need to declare the expanders in
267 use, and assign numbers to the GPIOs they expose. Those GPIOs
268 can then be used from drivers and other kernel code, just like
269 other GPIOs, but only accessible from task contexts.
271 This driver provides an in-kernel interface to those GPIOs using
272 platform-neutral GPIO calls.
275 bool "Semtech SX150x I2C GPIO expander"
279 Say yes here to provide support for Semtech SX150-series I2C
280 GPIO expanders. Compatible models include:
289 This enables support for the GPIOs found on the STMPE I/O
294 depends on MFD_TC3589X
296 This enables support for the GPIOs found on the TC3589X
300 tristate "TI TPS65912 GPIO"
301 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
303 This driver supports TPS65912 gpio chip
306 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
307 depends on TWL4030_CORE
309 Say yes here to access the GPIO signals of various multi-function
310 power management chips from Texas Instruments.
313 tristate "WM831x GPIOs"
314 depends on MFD_WM831X
316 Say yes here to access the GPIO signals of WM831x power management
317 chips from Wolfson Microelectronics.
320 tristate "WM8350 GPIOs"
321 depends on MFD_WM8350
323 Say yes here to access the GPIO signals of WM8350 power management
324 chips from Wolfson Microelectronics.
327 tristate "WM8994 GPIOs"
328 depends on MFD_WM8994
330 Say yes here to access the GPIO signals of WM8994 audio hub
331 CODECs from Wolfson Microelectronics.
334 tristate "GPIO Support for ADP5520 PMIC"
335 depends on PMIC_ADP5520
337 This option enables support for on-chip GPIO found
338 on Analog Devices ADP5520 PMICs.
341 tristate "ADP5588 I2C GPIO expander"
344 This option enables support for 18 GPIOs found
345 on Analog Devices ADP5588 GPIO Expanders.
347 config GPIO_ADP5588_IRQ
348 bool "Interrupt controller support for ADP5588"
349 depends on GPIO_ADP5588=y
351 Say yes here to enable the adp5588 to be used as an interrupt
352 controller. It requires the driver to be built in the kernel.
354 comment "PCI GPIO expanders:"
357 tristate "AMD CS5535/CS5536 GPIO support"
358 depends on PCI && X86 && !CS5535_GPIO && MFD_CS5535
360 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
361 can be used for quite a number of things. The CS5535/6 is found on
362 AMD Geode and Lemote Yeeloong devices.
367 tristate "BT8XX GPIO abuser"
368 depends on PCI && VIDEO_BT848=n
370 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
371 as a cheap PCI GPIO card.
373 This chip can be found on Miro, Hauppauge and STB TV-cards.
375 The card needs to be physically altered for using it as a
376 GPIO card. For more information on how to build a GPIO card
377 from a BT8xx TV card, see the documentation file at
378 Documentation/bt8xxgpio.txt
383 bool "Intel Langwell/Penwell GPIO support"
384 depends on PCI && X86
386 Say Y here to support Intel Langwell/Penwell GPIO.
389 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GPIO"
390 depends on PCI && X86
392 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
393 which is an IOH(Input/Output Hub) for x86 embedded processor.
394 This driver can access PCH GPIO device.
396 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
398 ML7223 IOH is for MP(Media Phone) use.
399 ML7223 is companion chip for Intel Atom E6xx series.
400 ML7223 is completely compatible for Intel EG20T PCH.
403 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
406 ML7213 is companion chip for Intel Atom E6xx series.
407 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
408 Hub) which is for IVI(In-Vehicle Infotainment) use.
409 This driver can access the IOH's GPIO device.
411 config GPIO_TIMBERDALE
412 bool "Support for timberdale GPIO IP"
413 depends on MFD_TIMBERDALE && HAS_IOMEM
415 Add support for the GPIO IP in the timberdale FPGA.
418 tristate "RDC R-321x GPIO support"
424 Support for the RDC R321x SoC GPIOs over southbridge
425 PCI configuration space.
427 comment "SPI GPIO expanders:"
430 tristate "Maxim MAX7301 GPIO expander"
431 depends on SPI_MASTER
434 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
437 tristate "Microchip MCP23xxx I/O expander"
438 depends on SPI_MASTER || I2C
440 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
442 This provides a GPIO interface supporting inputs and outputs.
445 tristate "Freescale MC33880 high-side/low-side switch"
446 depends on SPI_MASTER
448 SPI driver for Freescale MC33880 high-side/low-side switch.
449 This provides GPIO interface supporting inputs and outputs.
452 tristate "74x164 serial-in/parallel-out 8-bits shift register"
453 depends on SPI_MASTER
455 Platform driver for 74x164 compatible serial-in/parallel-out
456 8-outputs shift registers. This driver can be used to provide access
457 to more gpio outputs.
459 comment "AC97 GPIO expanders:"
462 bool "Philips UCB1400 GPIO"
463 depends on UCB1400_CORE
465 This enables support for the Philips UCB1400 GPIO pins.
466 The UCB1400 is an AC97 audio codec.
468 comment "MODULbus GPIO expanders:"
471 tristate "Janz VMOD-TTL Digital IO Module"
472 depends on MFD_JANZ_CMODIO
474 This enables support for the Janz VMOD-TTL Digital IO module.
475 This driver provides support for driving the pins in output
476 mode only. Input mode is not supported.
479 bool "ST-Ericsson AB8500 Mixed Signal Circuit gpio functions"
480 depends on AB8500_CORE && BROKEN
482 Select this to enable the AB8500 IC GPIO driver
486 depends on MFD_TPS65910
488 Select this option to enable GPIO driver for the TPS65910