2 # GPIO infrastructure and drivers
5 config ARCH_HAVE_CUSTOM_GPIO_H
8 Selecting this config option from the architecture Kconfig allows
9 the architecture to provide a custom asm/gpio.h implementation
10 overriding the default implementations. New uses of this are
13 config ARCH_WANT_OPTIONAL_GPIOLIB
16 Select this config option from the architecture Kconfig, if
17 it is possible to use gpiolib on the architecture, but let the
18 user decide whether to actually build it or not.
19 Select this instead of ARCH_REQUIRE_GPIOLIB, if your architecture does
20 not depend on GPIOs being available, but rather let the user
21 decide whether he needs it or not.
23 config ARCH_REQUIRE_GPIOLIB
27 Platforms select gpiolib if they use this infrastructure
28 for all their GPIOs, usually starting with ones integrated
30 Selecting this from the architecture code will cause the gpiolib
31 code to always get built in.
40 depends on ARCH_WANT_OPTIONAL_GPIOLIB || ARCH_REQUIRE_GPIOLIB
43 This enables GPIO support through the generic GPIO library.
44 You only need to enable this, if you also want to enable
45 one or more of the GPIO drivers below.
60 bool "Debug GPIO calls"
61 depends on DEBUG_KERNEL
63 Say Y here to add some extra checks and diagnostics to GPIO calls.
64 These checks help ensure that GPIOs have been properly initialized
65 before they are used, and that sleeping calls are not made from
66 non-sleeping contexts. They can make bitbanged serial protocols
67 slower. The diagnostics help catch the type of setup errors
68 that are most common when setting up new platforms or boards.
71 bool "/sys/class/gpio/... (sysfs interface)"
74 Say Y here to add a sysfs interface for GPIOs.
76 This is mostly useful to work around omissions in a system's
77 kernel support. Those are common in custom and semicustom
78 hardware assembled using standard kernels with a minimum of
79 custom patches. In those cases, userspace code may import
80 a given GPIO from the kernel, if no kernel driver requested it.
82 Kernel drivers may also request that a particular GPIO be
83 exported to userspace; this can be useful when debugging.
88 # put drivers in the right section, in alphabetical order
91 tristate "Dialog DA9052 GPIO"
92 depends on PMIC_DA9052
94 Say yes here to enable the GPIO driver for the DA9052 chip.
97 tristate "Dialog Semiconductor DA9055 GPIO"
100 Say yes here to enable the GPIO driver for the DA9055 chip.
102 The Dialog DA9055 PMIC chip has 3 GPIO pins that can be
103 be controller by this driver.
105 If driver is built as a module it will be called gpio-da9055.
110 comment "Memory mapped GPIO drivers:"
114 depends on ARCH_CLPS711X
116 config GPIO_GENERIC_PLATFORM
117 tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
120 Say yes here to support basic platform_device memory-mapped GPIO controllers.
123 tristate "IT8761E GPIO support"
124 depends on X86 # unconditional access to IO space.
126 Say yes here to support GPIO functionality of IT8761E super I/O chip.
129 tristate "Emma Mobile GPIO"
132 Say yes here to support GPIO on Renesas Emma Mobile SoCs.
136 depends on ARCH_EP93XX
139 config GPIO_MM_LANTIQ
140 bool "Lantiq Memory mapped GPIOs"
141 depends on LANTIQ && SOC_XWAY
143 This enables support for memory mapped GPIOs on the External Bus Unit
144 (EBU) found on Lantiq SoCs. The gpios are output only as they are
145 created by attaching a 16bit latch to the bus.
149 depends on PPC_MPC52xx
152 bool "MPC512x/MPC8xxx GPIO support"
153 depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \
154 FSL_SOC_BOOKE || PPC_86xx
156 Say Y here if you're going to use hardware that connects to the
157 MPC512x/831x/834x/837x/8572/8610 GPIOs.
160 tristate "Qualcomm MSM GPIO v1"
161 depends on GPIOLIB && ARCH_MSM && (ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50)
163 Say yes here to support the GPIO interface on ARM v6 based
164 Qualcomm MSM chips. Most of the pins on the MSM can be
165 selected for GPIO, and are controlled by this driver.
168 tristate "Qualcomm MSM GPIO v2"
169 depends on GPIOLIB && ARCH_MSM
171 Say yes here to support the GPIO interface on ARM v7 based
172 Qualcomm MSM chips. Most of the pins on the MSM can be
173 selected for GPIO, and are controlled by this driver.
177 depends on PLAT_ORION
180 select GENERIC_IRQ_CHIP
186 select GENERIC_IRQ_CHIP
192 select GENERIC_IRQ_CHIP
195 bool "PrimeCell PL061 GPIO support"
196 depends on ARM && ARM_AMBA
197 select GENERIC_IRQ_CHIP
199 Say yes here to support the PrimeCell PL061 GPIO device
202 bool "PXA GPIO support"
203 depends on ARCH_PXA || ARCH_MMP
205 Say yes here to support the PXA GPIO device
207 config GPIO_SPEAR_SPICS
208 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
209 depends on PLAT_SPEAR
210 select GENERIC_IRQ_CHIP
212 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
215 bool "STA2x11/ConneXt GPIO support"
216 depends on MFD_STA2X11
217 select GENERIC_IRQ_CHIP
219 Say yes here to support the STA2x11/ConneXt GPIO device.
220 The GPIO module has 128 GPIO pins with alternate functions.
223 tristate "TS-5500 DIO blocks and compatibles"
225 This driver supports Digital I/O exposed by pin blocks found on some
226 Technologic Systems platforms. It includes, but is not limited to, 3
227 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
231 bool "Xilinx GPIO support"
232 depends on PPC_OF || MICROBLAZE
234 Say yes here to support the Xilinx FPGA GPIO device
237 tristate "NEC VR4100 series General-purpose I/O Uint support"
238 depends on CPU_VR41XX
240 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
243 tristate "Intel SCH/TunnelCreek/Centerton GPIO"
244 depends on PCI && X86
248 Say yes here to support GPIO interface on Intel Poulsbo SCH,
249 Intel Tunnel Creek processor or Intel Centerton processor.
250 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
251 powered by the core power rail and are turned off during sleep
252 modes (S3 and higher). The remaining four GPIOs are powered by
253 the Intel SCH suspend power supply. These GPIOs remain
254 active during S3. The suspend powered GPIOs can be used to wake the
255 system from the Suspend-to-RAM state.
256 The Intel Tunnel Creek processor has 5 GPIOs powered by the
257 core power rail and 9 from suspend power supply.
258 The Intel Centerton processor has a total of 30 GPIO pins.
259 Twenty-one are powered by the core power rail and 9 from the
260 suspend power supply.
263 tristate "Intel ICH GPIO"
264 depends on PCI && X86
268 Say yes here to support the GPIO functionality of a number of Intel
269 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
270 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
271 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
276 tristate "VIA VX855/VX875 GPIO"
277 depends on PCI && GENERIC_HARDIRQS
281 Support access to the VX855/VX875 GPIO lines through the gpio library.
283 This driver provides common support for accessing the device,
284 additional drivers must be enabled in order to use the
285 functionality of the device.
288 bool "GE FPGA based GPIO"
291 Support for common GPIO functionality provided on some GE Single Board
294 This driver provides basic support (configure as input or output, read
295 and write pin state) for GPIO implemented in a number of GE single
298 config GPIO_LYNXPOINT
299 bool "Intel Lynxpoint GPIO support"
300 depends on ACPI && X86
303 driver for GPIO functionality on Intel Lynxpoint PCH chipset
304 Requires ACPI device enumeration code to set up a platform device.
307 tristate "Aeroflex Gaisler GRGPIO support"
312 Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
313 VHDL IP core library.
315 comment "I2C GPIO expanders:"
318 tristate "Wolfson Microelectronics Arizona class devices"
319 depends on MFD_ARIZONA
321 Support for GPIOs on Wolfson Arizona class devices.
324 tristate "Maxim MAX7300 GPIO expander"
328 GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
331 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
334 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
335 Port Expanders. Each IO port on these chips has a fixed role of
336 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
337 Input and Output (designed by 'P'). The combinations are listed
340 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
341 max7322 (4I4O), max7323 (4P4O)
343 16 bits: max7324 (8I8O), max7325 (8P8O),
344 max7326 (4I12O), max7327 (4P12O)
346 Board setup code must specify the model to use, and the start
347 number for these GPIOs.
349 config GPIO_MAX732X_IRQ
350 bool "Interrupt controller support for MAX732x"
351 depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
353 Say yes here to enable the max732x to be used as an interrupt
354 controller. It requires the driver to be built in the kernel.
356 config GPIO_MC9S08DZ60
357 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
358 depends on I2C=y && MACH_MX35_3DS
360 Select this to enable the MC9S08DZ60 GPIO driver
363 tristate "PCA953x, PCA955x, PCA957x, TCA64xx, and MAX7310 I/O ports"
366 Say yes here to provide access to several register-oriented
367 SMBus I/O expanders, made mostly by NXP or TI. Compatible
370 4 bits: pca9536, pca9537
372 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
373 pca9556, pca9557, pca9574, tca6408
375 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
378 config GPIO_PCA953X_IRQ
379 bool "Interrupt controller support for PCA953x"
380 depends on GPIO_PCA953X=y
382 Say yes here to enable the pca953x to be used as an interrupt
383 controller. It requires the driver to be built in the kernel.
386 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
390 Say yes here to provide access to most "quasi-bidirectional" I2C
391 GPIO expanders used for additional digital outputs or inputs.
392 Most of these parts are from NXP, though TI is a second source for
393 some of them. Compatible models include:
395 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
396 pca9670, pca9672, pca9674, pca9674a,
399 16 bits: pcf8575, pcf8575c, pca8575,
400 pca9671, pca9673, pca9675
402 Your board setup code will need to declare the expanders in
403 use, and assign numbers to the GPIOs they expose. Those GPIOs
404 can then be used from drivers and other kernel code, just like
405 other GPIOs, but only accessible from task contexts.
407 This driver provides an in-kernel interface to those GPIOs using
408 platform-neutral GPIO calls.
411 bool "RICOH RC5T583 GPIO"
412 depends on MFD_RC5T583
414 Select this option to enable GPIO driver for the Ricoh RC5T583
416 This driver provides the support for driving/reading the gpio pins
417 of RC5T583 device through standard gpio library.
420 bool "Semtech SX150x I2C GPIO expander"
424 Say yes here to provide support for Semtech SX150-series I2C
425 GPIO expanders. Compatible models include:
434 This enables support for the GPIOs found on the STMPE I/O
438 bool "XWAY STP GPIOs"
441 This enables support for the Serial To Parallel (STP) unit found on
442 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
443 that can be up to 24 bit. This peripheral is aimed at driving leds.
444 Some of the gpios/leds can be auto updated by the soc with dsl and
449 depends on MFD_TC3589X
451 This enables support for the GPIOs found on the TC3589X
455 tristate "TI TPS65912 GPIO"
456 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
458 This driver supports TPS65912 gpio chip
461 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
462 depends on TWL4030_CORE
464 Say yes here to access the GPIO signals of various multi-function
465 power management chips from Texas Instruments.
468 tristate "TWL6040 GPO"
469 depends on TWL6040_CORE
471 Say yes here to access the GPO signals of twl6040
472 audio chip from Texas Instruments.
475 tristate "WM831x GPIOs"
476 depends on MFD_WM831X
478 Say yes here to access the GPIO signals of WM831x power management
479 chips from Wolfson Microelectronics.
482 tristate "WM8350 GPIOs"
483 depends on MFD_WM8350
485 Say yes here to access the GPIO signals of WM8350 power management
486 chips from Wolfson Microelectronics.
489 tristate "WM8994 GPIOs"
490 depends on MFD_WM8994
492 Say yes here to access the GPIO signals of WM8994 audio hub
493 CODECs from Wolfson Microelectronics.
496 tristate "GPIO Support for ADP5520 PMIC"
497 depends on PMIC_ADP5520
499 This option enables support for on-chip GPIO found
500 on Analog Devices ADP5520 PMICs.
503 tristate "ADP5588 I2C GPIO expander"
506 This option enables support for 18 GPIOs found
507 on Analog Devices ADP5588 GPIO Expanders.
509 config GPIO_ADP5588_IRQ
510 bool "Interrupt controller support for ADP5588"
511 depends on GPIO_ADP5588=y
513 Say yes here to enable the adp5588 to be used as an interrupt
514 controller. It requires the driver to be built in the kernel.
517 tristate "Avionic Design N-bit GPIO expander"
518 depends on I2C && OF_GPIO
520 This option enables support for N GPIOs found on Avionic Design
521 I2C GPIO expanders. The register space will be extended by powers
522 of two, so the controller will need to accommodate for that. For
523 example: if a controller provides 48 pins, 6 registers will be
524 enough to represent all pins, but the driver will assume a
525 register layout for 64 pins (8 registers).
527 comment "PCI GPIO expanders:"
530 tristate "AMD CS5535/CS5536 GPIO support"
531 depends on PCI && X86 && MFD_CS5535
533 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
534 can be used for quite a number of things. The CS5535/6 is found on
535 AMD Geode and Lemote Yeeloong devices.
540 tristate "BT8XX GPIO abuser"
541 depends on PCI && VIDEO_BT848=n
543 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
544 as a cheap PCI GPIO card.
546 This chip can be found on Miro, Hauppauge and STB TV-cards.
548 The card needs to be physically altered for using it as a
549 GPIO card. For more information on how to build a GPIO card
550 from a BT8xx TV card, see the documentation file at
551 Documentation/bt8xxgpio.txt
556 tristate "AMD 8111 GPIO driver"
559 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
561 Note, that usually system firmware/ACPI handles GPIO pins on their
562 own and users might easily break their systems with uncarefull usage
568 bool "Intel Langwell/Penwell GPIO support"
569 depends on PCI && X86
572 Say Y here to support Intel Langwell/Penwell GPIO.
575 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
576 depends on PCI && X86
577 select GENERIC_IRQ_CHIP
579 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
580 which is an IOH(Input/Output Hub) for x86 embedded processor.
581 This driver can access PCH GPIO device.
583 This driver also can be used for LAPIS Semiconductor IOH(Input/
584 Output Hub), ML7223 and ML7831.
585 ML7223 IOH is for MP(Media Phone) use.
586 ML7831 IOH is for general purpose use.
587 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
588 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
591 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
593 select GENERIC_IRQ_CHIP
595 ML7213 is companion chip for Intel Atom E6xx series.
596 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
597 Hub) which is for IVI(In-Vehicle Infotainment) use.
598 This driver can access the IOH's GPIO device.
600 config GPIO_SODAVILLE
601 bool "Intel Sodaville GPIO support"
602 depends on X86 && PCI && OF
604 select GENERIC_IRQ_CHIP
606 Say Y here to support Intel Sodaville GPIO.
608 config GPIO_TIMBERDALE
609 bool "Support for timberdale GPIO IP"
610 depends on MFD_TIMBERDALE && HAS_IOMEM
612 Add support for the GPIO IP in the timberdale FPGA.
615 tristate "RDC R-321x GPIO support"
616 depends on PCI && GENERIC_HARDIRQS
620 Support for the RDC R321x SoC GPIOs over southbridge
621 PCI configuration space.
623 comment "SPI GPIO expanders:"
626 tristate "Maxim MAX7301 GPIO expander"
627 depends on SPI_MASTER
630 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
633 tristate "Microchip MCP23xxx I/O expander"
634 depends on SPI_MASTER || I2C
636 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
638 This provides a GPIO interface supporting inputs and outputs.
641 tristate "Freescale MC33880 high-side/low-side switch"
642 depends on SPI_MASTER
644 SPI driver for Freescale MC33880 high-side/low-side switch.
645 This provides GPIO interface supporting inputs and outputs.
648 tristate "74x164 serial-in/parallel-out 8-bits shift register"
649 depends on SPI_MASTER
651 Platform driver for 74x164 compatible serial-in/parallel-out
652 8-outputs shift registers. This driver can be used to provide access
653 to more gpio outputs.
655 comment "AC97 GPIO expanders:"
658 bool "Philips UCB1400 GPIO"
659 depends on UCB1400_CORE
661 This enables support for the Philips UCB1400 GPIO pins.
662 The UCB1400 is an AC97 audio codec.
664 comment "MODULbus GPIO expanders:"
667 tristate "Janz VMOD-TTL Digital IO Module"
668 depends on MFD_JANZ_CMODIO
670 This enables support for the Janz VMOD-TTL Digital IO module.
671 This driver provides support for driving the pins in output
672 mode only. Input mode is not supported.
675 bool "TI PALMAS series PMICs GPIO"
676 depends on MFD_PALMAS
678 Select this option to enable GPIO driver for the TI PALMAS
683 depends on MFD_TPS6586X
685 Select this option to enable GPIO driver for the TPS6586X
690 depends on MFD_TPS65910
692 Select this option to enable GPIO driver for the TPS65910
696 bool "Intel MSIC mixed signal gpio support"
697 depends on MFD_INTEL_MSIC
699 Enable support for GPIO on intel MSIC controllers found in
702 comment "USB GPIO expanders:"
704 config GPIO_VIPERBOARD
705 tristate "Viperboard GPIO a & b support"
706 depends on MFD_VIPERBOARD && USB
708 Say yes here to access the GPIO signals of Nano River
709 Technologies Viperboard. There are two GPIO chips on the
710 board: gpioa and gpiob.
711 See viperboard API specification and Nano
712 River Tech's viperboard.h for detailed meaning
713 of the module parameters.