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.
36 depends on ARCH_WANT_OPTIONAL_GPIOLIB || ARCH_REQUIRE_GPIOLIB
38 This enables GPIO support through the generic GPIO library.
39 You only need to enable this, if you also want to enable
40 one or more of the GPIO drivers below.
59 bool "Debug GPIO calls"
60 depends on DEBUG_KERNEL
62 Say Y here to add some extra checks and diagnostics to GPIO calls.
63 These checks help ensure that GPIOs have been properly initialized
64 before they are used, and that sleeping calls are not made from
65 non-sleeping contexts. They can make bitbanged serial protocols
66 slower. The diagnostics help catch the type of setup errors
67 that are most common when setting up new platforms or boards.
70 bool "/sys/class/gpio/... (sysfs interface)"
73 Say Y here to add a sysfs interface for GPIOs.
75 This is mostly useful to work around omissions in a system's
76 kernel support. Those are common in custom and semicustom
77 hardware assembled using standard kernels with a minimum of
78 custom patches. In those cases, userspace code may import
79 a given GPIO from the kernel, if no kernel driver requested it.
81 Kernel drivers may also request that a particular GPIO be
82 exported to userspace; this can be useful when debugging.
87 # put drivers in the right section, in alphabetical order
90 tristate "Dialog DA9052 GPIO"
91 depends on PMIC_DA9052
93 Say yes here to enable the GPIO driver for the DA9052 chip.
96 tristate "Dialog Semiconductor DA9055 GPIO"
99 Say yes here to enable the GPIO driver for the DA9055 chip.
101 The Dialog DA9055 PMIC chip has 3 GPIO pins that can be
102 be controller by this driver.
104 If driver is built as a module it will be called gpio-da9055.
109 comment "Memory mapped GPIO drivers:"
112 tristate "CLPS711X GPIO support"
113 depends on ARCH_CLPS711X
116 Say yes here to support GPIO on CLPS711X SoCs.
118 config GPIO_GENERIC_PLATFORM
119 tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
122 Say yes here to support basic platform_device memory-mapped GPIO controllers.
125 tristate "IT8761E GPIO support"
126 depends on X86 # unconditional access to IO space.
128 Say yes here to support GPIO functionality of IT8761E super I/O chip.
131 tristate "Emma Mobile GPIO"
132 depends on ARM && OF_GPIO
134 Say yes here to support GPIO on Renesas Emma Mobile SoCs.
138 depends on ARCH_EP93XX
141 config GPIO_MM_LANTIQ
142 bool "Lantiq Memory mapped GPIOs"
143 depends on LANTIQ && SOC_XWAY
145 This enables support for memory mapped GPIOs on the External Bus Unit
146 (EBU) found on Lantiq SoCs. The gpios are output only as they are
147 created by attaching a 16bit latch to the bus.
150 tristate "F71882FG and F71889F GPIO support"
153 This option enables support for GPIOs found on Fintek Super-I/O
154 chips F71882FG and F71889F.
156 To compile this driver as a module, choose M here: the module will
157 be called f7188x-gpio.
160 bool "MOXART GPIO support"
161 depends on ARCH_MOXART
163 Select this option to enable GPIO driver for
164 MOXA ART SoC devices.
168 depends on PPC_MPC52xx
171 bool "MPC512x/MPC8xxx GPIO support"
172 depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \
173 FSL_SOC_BOOKE || PPC_86xx
175 Say Y here if you're going to use hardware that connects to the
176 MPC512x/831x/834x/837x/8572/8610 GPIOs.
179 tristate "Qualcomm MSM GPIO v1"
180 depends on GPIOLIB && ARCH_MSM && (ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50)
182 Say yes here to support the GPIO interface on ARM v6 based
183 Qualcomm MSM chips. Most of the pins on the MSM can be
184 selected for GPIO, and are controlled by this driver.
187 tristate "Qualcomm MSM GPIO v2"
188 depends on GPIOLIB && OF && ARCH_MSM
190 Say yes here to support the GPIO interface on ARM v7 based
191 Qualcomm MSM chips. Most of the pins on the MSM can be
192 selected for GPIO, and are controlled by this driver.
196 depends on PLAT_ORION
199 select GENERIC_IRQ_CHIP
205 select GENERIC_IRQ_CHIP
211 select GENERIC_IRQ_CHIP
214 tristate "Cavium OCTEON GPIO"
215 depends on GPIOLIB && CAVIUM_OCTEON_SOC
218 Say yes here to support the on-chip GPIO lines on the OCTEON
222 bool "PrimeCell PL061 GPIO support"
224 select GENERIC_IRQ_CHIP
226 Say yes here to support the PrimeCell PL061 GPIO device
229 bool "PXA GPIO support"
230 depends on ARCH_PXA || ARCH_MMP
232 Say yes here to support the PXA GPIO device
235 tristate "Renesas R-Car GPIO"
238 Say yes here to support GPIO on Renesas R-Car SoCs.
242 depends on PLAT_SAMSUNG
244 Legacy GPIO support. Use only for platforms without support for
247 config GPIO_SPEAR_SPICS
248 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
249 depends on PLAT_SPEAR
250 select GENERIC_IRQ_CHIP
252 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
255 bool "STA2x11/ConneXt GPIO support"
256 depends on MFD_STA2X11
257 select GENERIC_IRQ_CHIP
259 Say yes here to support the STA2x11/ConneXt GPIO device.
260 The GPIO module has 128 GPIO pins with alternate functions.
263 tristate "TS-5500 DIO blocks and compatibles"
265 This driver supports Digital I/O exposed by pin blocks found on some
266 Technologic Systems platforms. It includes, but is not limited to, 3
267 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
271 bool "Toumaz Xenif TZ1090 GPIO support"
272 depends on SOC_TZ1090
273 select GENERIC_IRQ_CHIP
276 Say yes here to support Toumaz Xenif TZ1090 GPIOs.
278 config GPIO_TZ1090_PDC
279 bool "Toumaz Xenif TZ1090 PDC GPIO support"
280 depends on SOC_TZ1090
283 Say yes here to support Toumaz Xenif TZ1090 PDC GPIOs.
286 bool "Xilinx GPIO support"
287 depends on PPC_OF || MICROBLAZE || ARCH_ZYNQ
289 Say yes here to support the Xilinx FPGA GPIO device
292 bool "Xtensa GPIO32 support"
296 Say yes here to support the Xtensa internal GPIO32 IMPWIRE (input)
297 and EXPSTATE (output) ports
300 tristate "NEC VR4100 series General-purpose I/O Uint support"
301 depends on CPU_VR41XX
303 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
306 tristate "Intel SCH/TunnelCreek/Centerton GPIO"
307 depends on PCI && X86
311 Say yes here to support GPIO interface on Intel Poulsbo SCH,
312 Intel Tunnel Creek processor or Intel Centerton processor.
313 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
314 powered by the core power rail and are turned off during sleep
315 modes (S3 and higher). The remaining four GPIOs are powered by
316 the Intel SCH suspend power supply. These GPIOs remain
317 active during S3. The suspend powered GPIOs can be used to wake the
318 system from the Suspend-to-RAM state.
319 The Intel Tunnel Creek processor has 5 GPIOs powered by the
320 core power rail and 9 from suspend power supply.
321 The Intel Centerton processor has a total of 30 GPIO pins.
322 Twenty-one are powered by the core power rail and 9 from the
323 suspend power supply.
326 tristate "Intel ICH GPIO"
327 depends on PCI && X86
331 Say yes here to support the GPIO functionality of a number of Intel
332 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
333 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
334 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
339 tristate "Intel IOP GPIO"
340 depends on ARM && (ARCH_IOP32X || ARCH_IOP33X)
342 Say yes here to support the GPIO functionality of a number of Intel
348 tristate "VIA VX855/VX875 GPIO"
353 Support access to the VX855/VX875 GPIO lines through the gpio library.
355 This driver provides common support for accessing the device,
356 additional drivers must be enabled in order to use the
357 functionality of the device.
360 bool "GE FPGA based GPIO"
363 Support for common GPIO functionality provided on some GE Single Board
366 This driver provides basic support (configure as input or output, read
367 and write pin state) for GPIO implemented in a number of GE single
370 config GPIO_LYNXPOINT
371 tristate "Intel Lynxpoint GPIO support"
372 depends on ACPI && X86
375 driver for GPIO functionality on Intel Lynxpoint PCH chipset
376 Requires ACPI device enumeration code to set up a platform device.
379 tristate "Aeroflex Gaisler GRGPIO support"
384 Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
385 VHDL IP core library.
391 comment "I2C GPIO expanders:"
394 tristate "Wolfson Microelectronics Arizona class devices"
395 depends on MFD_ARIZONA
397 Support for GPIOs on Wolfson Arizona class devices.
400 tristate "Maxim MAX7300 GPIO expander"
404 GPIO driver for Maxim MAX7300 I2C-based GPIO expander.
407 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
410 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
411 Port Expanders. Each IO port on these chips has a fixed role of
412 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
413 Input and Output (designed by 'P'). The combinations are listed
416 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
417 max7322 (4I4O), max7323 (4P4O)
419 16 bits: max7324 (8I8O), max7325 (8P8O),
420 max7326 (4I12O), max7327 (4P12O)
422 Board setup code must specify the model to use, and the start
423 number for these GPIOs.
425 config GPIO_MAX732X_IRQ
426 bool "Interrupt controller support for MAX732x"
427 depends on GPIO_MAX732X=y
429 Say yes here to enable the max732x to be used as an interrupt
430 controller. It requires the driver to be built in the kernel.
432 config GPIO_MC9S08DZ60
433 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
434 depends on I2C=y && MACH_MX35_3DS
436 Select this to enable the MC9S08DZ60 GPIO driver
439 tristate "PCA953x, PCA955x, PCA957x, TCA64xx, and MAX7310 I/O ports"
442 Say yes here to provide access to several register-oriented
443 SMBus I/O expanders, made mostly by NXP or TI. Compatible
446 4 bits: pca9536, pca9537
448 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
449 pca9556, pca9557, pca9574, tca6408
451 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
454 config GPIO_PCA953X_IRQ
455 bool "Interrupt controller support for PCA953x"
456 depends on GPIO_PCA953X=y
458 Say yes here to enable the pca953x to be used as an interrupt
459 controller. It requires the driver to be built in the kernel.
462 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
466 Say yes here to provide access to most "quasi-bidirectional" I2C
467 GPIO expanders used for additional digital outputs or inputs.
468 Most of these parts are from NXP, though TI is a second source for
469 some of them. Compatible models include:
471 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
472 pca9670, pca9672, pca9674, pca9674a,
475 16 bits: pcf8575, pcf8575c, pca8575,
476 pca9671, pca9673, pca9675
478 Your board setup code will need to declare the expanders in
479 use, and assign numbers to the GPIOs they expose. Those GPIOs
480 can then be used from drivers and other kernel code, just like
481 other GPIOs, but only accessible from task contexts.
483 This driver provides an in-kernel interface to those GPIOs using
484 platform-neutral GPIO calls.
487 bool "RICOH RC5T583 GPIO"
488 depends on MFD_RC5T583
490 Select this option to enable GPIO driver for the Ricoh RC5T583
492 This driver provides the support for driving/reading the gpio pins
493 of RC5T583 device through standard gpio library.
496 bool "Semtech SX150x I2C GPIO expander"
500 Say yes here to provide support for Semtech SX150-series I2C
501 GPIO expanders. Compatible models include:
510 This enables support for the GPIOs found on the STMPE I/O
514 bool "XWAY STP GPIOs"
517 This enables support for the Serial To Parallel (STP) unit found on
518 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
519 that can be up to 24 bit. This peripheral is aimed at driving leds.
520 Some of the gpios/leds can be auto updated by the soc with dsl and
525 depends on MFD_TC3589X
527 This enables support for the GPIOs found on the TC3589X
531 tristate "TI TPS65912 GPIO"
532 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
534 This driver supports TPS65912 gpio chip
537 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
538 depends on TWL4030_CORE
540 Say yes here to access the GPIO signals of various multi-function
541 power management chips from Texas Instruments.
544 tristate "TWL6040 GPO"
545 depends on TWL6040_CORE
547 Say yes here to access the GPO signals of twl6040
548 audio chip from Texas Instruments.
551 tristate "WM831x GPIOs"
552 depends on MFD_WM831X
554 Say yes here to access the GPIO signals of WM831x power management
555 chips from Wolfson Microelectronics.
558 tristate "WM8350 GPIOs"
559 depends on MFD_WM8350
561 Say yes here to access the GPIO signals of WM8350 power management
562 chips from Wolfson Microelectronics.
565 tristate "WM8994 GPIOs"
566 depends on MFD_WM8994
568 Say yes here to access the GPIO signals of WM8994 audio hub
569 CODECs from Wolfson Microelectronics.
572 tristate "GPIO Support for ADP5520 PMIC"
573 depends on PMIC_ADP5520
575 This option enables support for on-chip GPIO found
576 on Analog Devices ADP5520 PMICs.
579 tristate "ADP5588 I2C GPIO expander"
582 This option enables support for 18 GPIOs found
583 on Analog Devices ADP5588 GPIO Expanders.
585 config GPIO_ADP5588_IRQ
586 bool "Interrupt controller support for ADP5588"
587 depends on GPIO_ADP5588=y
589 Say yes here to enable the adp5588 to be used as an interrupt
590 controller. It requires the driver to be built in the kernel.
593 tristate "Avionic Design N-bit GPIO expander"
594 depends on I2C && OF_GPIO
596 This option enables support for N GPIOs found on Avionic Design
597 I2C GPIO expanders. The register space will be extended by powers
598 of two, so the controller will need to accommodate for that. For
599 example: if a controller provides 48 pins, 6 registers will be
600 enough to represent all pins, but the driver will assume a
601 register layout for 64 pins (8 registers).
603 comment "PCI GPIO expanders:"
606 tristate "AMD CS5535/CS5536 GPIO support"
607 depends on PCI && X86 && MFD_CS5535
609 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
610 can be used for quite a number of things. The CS5535/6 is found on
611 AMD Geode and Lemote Yeeloong devices.
616 tristate "BT8XX GPIO abuser"
617 depends on PCI && VIDEO_BT848=n
619 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
620 as a cheap PCI GPIO card.
622 This chip can be found on Miro, Hauppauge and STB TV-cards.
624 The card needs to be physically altered for using it as a
625 GPIO card. For more information on how to build a GPIO card
626 from a BT8xx TV card, see the documentation file at
627 Documentation/bt8xxgpio.txt
632 tristate "AMD 8111 GPIO driver"
635 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
637 Note, that usually system firmware/ACPI handles GPIO pins on their
638 own and users might easily break their systems with uncarefull usage
643 config GPIO_INTEL_MID
644 bool "Intel Mid GPIO support"
645 depends on PCI && X86
648 Say Y here to support Intel Mid GPIO.
651 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
652 depends on PCI && X86
653 select GENERIC_IRQ_CHIP
655 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
656 which is an IOH(Input/Output Hub) for x86 embedded processor.
657 This driver can access PCH GPIO device.
659 This driver also can be used for LAPIS Semiconductor IOH(Input/
660 Output Hub), ML7223 and ML7831.
661 ML7223 IOH is for MP(Media Phone) use.
662 ML7831 IOH is for general purpose use.
663 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
664 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
667 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
669 select GENERIC_IRQ_CHIP
671 ML7213 is companion chip for Intel Atom E6xx series.
672 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
673 Hub) which is for IVI(In-Vehicle Infotainment) use.
674 This driver can access the IOH's GPIO device.
676 config GPIO_SODAVILLE
677 bool "Intel Sodaville GPIO support"
678 depends on X86 && PCI && OF
680 select GENERIC_IRQ_CHIP
682 Say Y here to support Intel Sodaville GPIO.
684 config GPIO_TIMBERDALE
685 bool "Support for timberdale GPIO IP"
686 depends on MFD_TIMBERDALE && HAS_IOMEM
688 Add support for the GPIO IP in the timberdale FPGA.
691 tristate "RDC R-321x GPIO support"
696 Support for the RDC R321x SoC GPIOs over southbridge
697 PCI configuration space.
699 comment "SPI GPIO expanders:"
702 tristate "Maxim MAX7301 GPIO expander"
703 depends on SPI_MASTER
706 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
709 tristate "Microchip MCP23xxx I/O expander"
710 depends on (SPI_MASTER && !I2C) || I2C
712 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
714 This provides a GPIO interface supporting inputs and outputs.
717 tristate "Freescale MC33880 high-side/low-side switch"
718 depends on SPI_MASTER
720 SPI driver for Freescale MC33880 high-side/low-side switch.
721 This provides GPIO interface supporting inputs and outputs.
724 tristate "74x164 serial-in/parallel-out 8-bits shift register"
725 depends on SPI_MASTER && OF
727 Driver for 74x164 compatible serial-in/parallel-out 8-outputs
728 shift registers. This driver can be used to provide access
729 to more gpio outputs.
731 comment "AC97 GPIO expanders:"
734 tristate "Philips UCB1400 GPIO"
735 depends on UCB1400_CORE
737 This enables support for the Philips UCB1400 GPIO pins.
738 The UCB1400 is an AC97 audio codec.
740 comment "LPC GPIO expanders:"
743 tristate "Kontron ETX / COMexpress GPIO"
744 depends on MFD_KEMPLD
746 This enables support for the PLD GPIO interface on some Kontron ETX
747 and COMexpress (ETXexpress) modules.
749 This driver can also be built as a module. If so, the module will be
752 comment "MODULbus GPIO expanders:"
755 tristate "Janz VMOD-TTL Digital IO Module"
756 depends on MFD_JANZ_CMODIO
758 This enables support for the Janz VMOD-TTL Digital IO module.
759 This driver provides support for driving the pins in output
760 mode only. Input mode is not supported.
763 bool "TI PALMAS series PMICs GPIO"
764 depends on MFD_PALMAS
766 Select this option to enable GPIO driver for the TI PALMAS
771 depends on MFD_TPS6586X
773 Select this option to enable GPIO driver for the TPS6586X
778 depends on MFD_TPS65910
780 Select this option to enable GPIO driver for the TPS65910
784 bool "Intel MSIC mixed signal gpio support"
785 depends on MFD_INTEL_MSIC
787 Enable support for GPIO on intel MSIC controllers found in
791 bool "Broadcom Kona GPIO"
794 Turn on GPIO support for Broadcom "Kona" chips.
796 comment "USB GPIO expanders:"
798 config GPIO_VIPERBOARD
799 tristate "Viperboard GPIO a & b support"
800 depends on MFD_VIPERBOARD && USB
802 Say yes here to access the GPIO signals of Nano River
803 Technologies Viperboard. There are two GPIO chips on the
804 board: gpioa and gpiob.
805 See viperboard API specification and Nano
806 River Tech's viperboard.h for detailed meaning
807 of the module parameters.