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 tristate "NEC VR4100 series General-purpose I/O Uint support"
293 depends on CPU_VR41XX
295 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
298 tristate "Intel SCH/TunnelCreek/Centerton GPIO"
299 depends on PCI && X86
303 Say yes here to support GPIO interface on Intel Poulsbo SCH,
304 Intel Tunnel Creek processor or Intel Centerton processor.
305 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
306 powered by the core power rail and are turned off during sleep
307 modes (S3 and higher). The remaining four GPIOs are powered by
308 the Intel SCH suspend power supply. These GPIOs remain
309 active during S3. The suspend powered GPIOs can be used to wake the
310 system from the Suspend-to-RAM state.
311 The Intel Tunnel Creek processor has 5 GPIOs powered by the
312 core power rail and 9 from suspend power supply.
313 The Intel Centerton processor has a total of 30 GPIO pins.
314 Twenty-one are powered by the core power rail and 9 from the
315 suspend power supply.
318 tristate "Intel ICH GPIO"
319 depends on PCI && X86
323 Say yes here to support the GPIO functionality of a number of Intel
324 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
325 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
326 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
331 tristate "Intel IOP GPIO"
332 depends on ARM && (ARCH_IOP32X || ARCH_IOP33X)
334 Say yes here to support the GPIO functionality of a number of Intel
340 tristate "VIA VX855/VX875 GPIO"
345 Support access to the VX855/VX875 GPIO lines through the gpio library.
347 This driver provides common support for accessing the device,
348 additional drivers must be enabled in order to use the
349 functionality of the device.
352 bool "GE FPGA based GPIO"
355 Support for common GPIO functionality provided on some GE Single Board
358 This driver provides basic support (configure as input or output, read
359 and write pin state) for GPIO implemented in a number of GE single
362 config GPIO_LYNXPOINT
363 tristate "Intel Lynxpoint GPIO support"
364 depends on ACPI && X86
367 driver for GPIO functionality on Intel Lynxpoint PCH chipset
368 Requires ACPI device enumeration code to set up a platform device.
371 tristate "Aeroflex Gaisler GRGPIO support"
376 Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
377 VHDL IP core library.
383 comment "I2C GPIO expanders:"
386 tristate "Wolfson Microelectronics Arizona class devices"
387 depends on MFD_ARIZONA
389 Support for GPIOs on Wolfson Arizona class devices.
392 tristate "Maxim MAX7300 GPIO expander"
396 GPIO driver for Maxim MAX7300 I2C-based GPIO expander.
399 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
402 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
403 Port Expanders. Each IO port on these chips has a fixed role of
404 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
405 Input and Output (designed by 'P'). The combinations are listed
408 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
409 max7322 (4I4O), max7323 (4P4O)
411 16 bits: max7324 (8I8O), max7325 (8P8O),
412 max7326 (4I12O), max7327 (4P12O)
414 Board setup code must specify the model to use, and the start
415 number for these GPIOs.
417 config GPIO_MAX732X_IRQ
418 bool "Interrupt controller support for MAX732x"
419 depends on GPIO_MAX732X=y
421 Say yes here to enable the max732x to be used as an interrupt
422 controller. It requires the driver to be built in the kernel.
424 config GPIO_MC9S08DZ60
425 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
426 depends on I2C=y && MACH_MX35_3DS
428 Select this to enable the MC9S08DZ60 GPIO driver
431 tristate "PCA953x, PCA955x, PCA957x, TCA64xx, and MAX7310 I/O ports"
434 Say yes here to provide access to several register-oriented
435 SMBus I/O expanders, made mostly by NXP or TI. Compatible
438 4 bits: pca9536, pca9537
440 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
441 pca9556, pca9557, pca9574, tca6408
443 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
446 config GPIO_PCA953X_IRQ
447 bool "Interrupt controller support for PCA953x"
448 depends on GPIO_PCA953X=y
450 Say yes here to enable the pca953x to be used as an interrupt
451 controller. It requires the driver to be built in the kernel.
454 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
458 Say yes here to provide access to most "quasi-bidirectional" I2C
459 GPIO expanders used for additional digital outputs or inputs.
460 Most of these parts are from NXP, though TI is a second source for
461 some of them. Compatible models include:
463 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
464 pca9670, pca9672, pca9674, pca9674a,
467 16 bits: pcf8575, pcf8575c, pca8575,
468 pca9671, pca9673, pca9675
470 Your board setup code will need to declare the expanders in
471 use, and assign numbers to the GPIOs they expose. Those GPIOs
472 can then be used from drivers and other kernel code, just like
473 other GPIOs, but only accessible from task contexts.
475 This driver provides an in-kernel interface to those GPIOs using
476 platform-neutral GPIO calls.
479 bool "RICOH RC5T583 GPIO"
480 depends on MFD_RC5T583
482 Select this option to enable GPIO driver for the Ricoh RC5T583
484 This driver provides the support for driving/reading the gpio pins
485 of RC5T583 device through standard gpio library.
488 bool "Semtech SX150x I2C GPIO expander"
492 Say yes here to provide support for Semtech SX150-series I2C
493 GPIO expanders. Compatible models include:
502 This enables support for the GPIOs found on the STMPE I/O
506 bool "XWAY STP GPIOs"
509 This enables support for the Serial To Parallel (STP) unit found on
510 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
511 that can be up to 24 bit. This peripheral is aimed at driving leds.
512 Some of the gpios/leds can be auto updated by the soc with dsl and
517 depends on MFD_TC3589X
519 This enables support for the GPIOs found on the TC3589X
523 tristate "TI TPS65912 GPIO"
524 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
526 This driver supports TPS65912 gpio chip
529 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
530 depends on TWL4030_CORE
532 Say yes here to access the GPIO signals of various multi-function
533 power management chips from Texas Instruments.
536 tristate "TWL6040 GPO"
537 depends on TWL6040_CORE
539 Say yes here to access the GPO signals of twl6040
540 audio chip from Texas Instruments.
543 tristate "WM831x GPIOs"
544 depends on MFD_WM831X
546 Say yes here to access the GPIO signals of WM831x power management
547 chips from Wolfson Microelectronics.
550 tristate "WM8350 GPIOs"
551 depends on MFD_WM8350
553 Say yes here to access the GPIO signals of WM8350 power management
554 chips from Wolfson Microelectronics.
557 tristate "WM8994 GPIOs"
558 depends on MFD_WM8994
560 Say yes here to access the GPIO signals of WM8994 audio hub
561 CODECs from Wolfson Microelectronics.
564 tristate "GPIO Support for ADP5520 PMIC"
565 depends on PMIC_ADP5520
567 This option enables support for on-chip GPIO found
568 on Analog Devices ADP5520 PMICs.
571 tristate "ADP5588 I2C GPIO expander"
574 This option enables support for 18 GPIOs found
575 on Analog Devices ADP5588 GPIO Expanders.
577 config GPIO_ADP5588_IRQ
578 bool "Interrupt controller support for ADP5588"
579 depends on GPIO_ADP5588=y
581 Say yes here to enable the adp5588 to be used as an interrupt
582 controller. It requires the driver to be built in the kernel.
585 tristate "Avionic Design N-bit GPIO expander"
586 depends on I2C && OF_GPIO
588 This option enables support for N GPIOs found on Avionic Design
589 I2C GPIO expanders. The register space will be extended by powers
590 of two, so the controller will need to accommodate for that. For
591 example: if a controller provides 48 pins, 6 registers will be
592 enough to represent all pins, but the driver will assume a
593 register layout for 64 pins (8 registers).
595 comment "PCI GPIO expanders:"
598 tristate "AMD CS5535/CS5536 GPIO support"
599 depends on PCI && X86 && MFD_CS5535
601 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
602 can be used for quite a number of things. The CS5535/6 is found on
603 AMD Geode and Lemote Yeeloong devices.
608 tristate "BT8XX GPIO abuser"
609 depends on PCI && VIDEO_BT848=n
611 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
612 as a cheap PCI GPIO card.
614 This chip can be found on Miro, Hauppauge and STB TV-cards.
616 The card needs to be physically altered for using it as a
617 GPIO card. For more information on how to build a GPIO card
618 from a BT8xx TV card, see the documentation file at
619 Documentation/bt8xxgpio.txt
624 tristate "AMD 8111 GPIO driver"
627 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
629 Note, that usually system firmware/ACPI handles GPIO pins on their
630 own and users might easily break their systems with uncarefull usage
635 config GPIO_INTEL_MID
636 bool "Intel Mid GPIO support"
637 depends on PCI && X86
640 Say Y here to support Intel Mid GPIO.
643 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
644 depends on PCI && X86
645 select GENERIC_IRQ_CHIP
647 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
648 which is an IOH(Input/Output Hub) for x86 embedded processor.
649 This driver can access PCH GPIO device.
651 This driver also can be used for LAPIS Semiconductor IOH(Input/
652 Output Hub), ML7223 and ML7831.
653 ML7223 IOH is for MP(Media Phone) use.
654 ML7831 IOH is for general purpose use.
655 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
656 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
659 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
661 select GENERIC_IRQ_CHIP
663 ML7213 is companion chip for Intel Atom E6xx series.
664 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
665 Hub) which is for IVI(In-Vehicle Infotainment) use.
666 This driver can access the IOH's GPIO device.
668 config GPIO_SODAVILLE
669 bool "Intel Sodaville GPIO support"
670 depends on X86 && PCI && OF
672 select GENERIC_IRQ_CHIP
674 Say Y here to support Intel Sodaville GPIO.
676 config GPIO_TIMBERDALE
677 bool "Support for timberdale GPIO IP"
678 depends on MFD_TIMBERDALE && HAS_IOMEM
680 Add support for the GPIO IP in the timberdale FPGA.
683 tristate "RDC R-321x GPIO support"
688 Support for the RDC R321x SoC GPIOs over southbridge
689 PCI configuration space.
691 comment "SPI GPIO expanders:"
694 tristate "Maxim MAX7301 GPIO expander"
695 depends on SPI_MASTER
698 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
701 tristate "Microchip MCP23xxx I/O expander"
702 depends on (SPI_MASTER && !I2C) || I2C
704 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
706 This provides a GPIO interface supporting inputs and outputs.
709 tristate "Freescale MC33880 high-side/low-side switch"
710 depends on SPI_MASTER
712 SPI driver for Freescale MC33880 high-side/low-side switch.
713 This provides GPIO interface supporting inputs and outputs.
716 tristate "74x164 serial-in/parallel-out 8-bits shift register"
717 depends on SPI_MASTER
719 Platform driver for 74x164 compatible serial-in/parallel-out
720 8-outputs shift registers. This driver can be used to provide access
721 to more gpio outputs.
723 comment "AC97 GPIO expanders:"
726 tristate "Philips UCB1400 GPIO"
727 depends on UCB1400_CORE
729 This enables support for the Philips UCB1400 GPIO pins.
730 The UCB1400 is an AC97 audio codec.
732 comment "LPC GPIO expanders:"
735 tristate "Kontron ETX / COMexpress GPIO"
736 depends on MFD_KEMPLD
738 This enables support for the PLD GPIO interface on some Kontron ETX
739 and COMexpress (ETXexpress) modules.
741 This driver can also be built as a module. If so, the module will be
744 comment "MODULbus GPIO expanders:"
747 tristate "Janz VMOD-TTL Digital IO Module"
748 depends on MFD_JANZ_CMODIO
750 This enables support for the Janz VMOD-TTL Digital IO module.
751 This driver provides support for driving the pins in output
752 mode only. Input mode is not supported.
755 bool "TI PALMAS series PMICs GPIO"
756 depends on MFD_PALMAS
758 Select this option to enable GPIO driver for the TI PALMAS
763 depends on MFD_TPS6586X
765 Select this option to enable GPIO driver for the TPS6586X
770 depends on MFD_TPS65910
772 Select this option to enable GPIO driver for the TPS65910
776 bool "Intel MSIC mixed signal gpio support"
777 depends on MFD_INTEL_MSIC
779 Enable support for GPIO on intel MSIC controllers found in
783 bool "Broadcom Kona GPIO"
786 Turn on GPIO support for Broadcom "Kona" chips.
788 comment "USB GPIO expanders:"
790 config GPIO_VIPERBOARD
791 tristate "Viperboard GPIO a & b support"
792 depends on MFD_VIPERBOARD && USB
794 Say yes here to access the GPIO signals of Nano River
795 Technologies Viperboard. There are two GPIO chips on the
796 board: gpioa and gpiob.
797 See viperboard API specification and Nano
798 River Tech's viperboard.h for detailed meaning
799 of the module parameters.