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.
58 config GPIOLIB_IRQCHIP
62 bool "Debug GPIO calls"
63 depends on DEBUG_KERNEL
65 Say Y here to add some extra checks and diagnostics to GPIO calls.
66 These checks help ensure that GPIOs have been properly initialized
67 before they are used, and that sleeping calls are not made from
68 non-sleeping contexts. They can make bitbanged serial protocols
69 slower. The diagnostics help catch the type of setup errors
70 that are most common when setting up new platforms or boards.
73 bool "/sys/class/gpio/... (sysfs interface)"
76 Say Y here to add a sysfs interface for GPIOs.
78 This is mostly useful to work around omissions in a system's
79 kernel support. Those are common in custom and semicustom
80 hardware assembled using standard kernels with a minimum of
81 custom patches. In those cases, userspace code may import
82 a given GPIO from the kernel, if no kernel driver requested it.
84 Kernel drivers may also request that a particular GPIO be
85 exported to userspace; this can be useful when debugging.
90 # put drivers in the right section, in alphabetical order
93 tristate "Dialog DA9052 GPIO"
94 depends on PMIC_DA9052
96 Say yes here to enable the GPIO driver for the DA9052 chip.
99 tristate "Dialog Semiconductor DA9055 GPIO"
100 depends on MFD_DA9055
102 Say yes here to enable the GPIO driver for the DA9055 chip.
104 The Dialog DA9055 PMIC chip has 3 GPIO pins that can be
105 be controller by this driver.
107 If driver is built as a module it will be called gpio-da9055.
112 comment "Memory mapped GPIO drivers:"
115 tristate "CLPS711X GPIO support"
116 depends on ARCH_CLPS711X || COMPILE_TEST
119 Say yes here to support GPIO on CLPS711X SoCs.
122 bool "TI Davinci/Keystone GPIO support"
123 default y if ARCH_DAVINCI
124 depends on ARM && (ARCH_DAVINCI || ARCH_KEYSTONE)
126 Say yes here to enable GPIO support for TI Davinci/Keystone SoCs.
128 config GPIO_GENERIC_PLATFORM
129 tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
132 Say yes here to support basic platform_device memory-mapped GPIO controllers.
135 tristate "Synopsys DesignWare APB GPIO driver"
137 select GENERIC_IRQ_CHIP
140 Say Y or M here to build support for the Synopsys DesignWare APB
144 tristate "IT8761E GPIO support"
145 depends on X86 # unconditional access to IO space.
147 Say yes here to support GPIO functionality of IT8761E super I/O chip.
150 tristate "Emma Mobile GPIO"
151 depends on ARM && OF_GPIO
153 Say yes here to support GPIO on Renesas Emma Mobile SoCs.
157 depends on ARCH_EP93XX
161 bool "LSI ZEVIO SoC memory mapped GPIOs"
162 depends on ARM && OF_GPIO
164 Say yes here to support the GPIO controller in LSI ZEVIO SoCs.
166 config GPIO_MM_LANTIQ
167 bool "Lantiq Memory mapped GPIOs"
168 depends on LANTIQ && SOC_XWAY
170 This enables support for memory mapped GPIOs on the External Bus Unit
171 (EBU) found on Lantiq SoCs. The gpios are output only as they are
172 created by attaching a 16bit latch to the bus.
175 tristate "F71882FG and F71889F GPIO support"
178 This option enables support for GPIOs found on Fintek Super-I/O
179 chips F71882FG and F71889F.
181 To compile this driver as a module, choose M here: the module will
182 be called f7188x-gpio.
185 bool "MOXART GPIO support"
186 depends on ARCH_MOXART
188 Select this option to enable GPIO driver for
189 MOXA ART SoC devices.
193 depends on PPC_MPC52xx
196 bool "MPC512x/MPC8xxx GPIO support"
197 depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \
198 FSL_SOC_BOOKE || PPC_86xx
200 Say Y here if you're going to use hardware that connects to the
201 MPC512x/831x/834x/837x/8572/8610 GPIOs.
204 tristate "Qualcomm MSM GPIO v1"
205 depends on GPIOLIB && ARCH_MSM && (ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50)
207 Say yes here to support the GPIO interface on ARM v6 based
208 Qualcomm MSM chips. Most of the pins on the MSM can be
209 selected for GPIO, and are controlled by this driver.
212 tristate "Qualcomm MSM GPIO v2"
213 depends on GPIOLIB && OF && ARCH_MSM
215 Say yes here to support the GPIO interface on ARM v7 based
216 Qualcomm MSM chips. Most of the pins on the MSM can be
217 selected for GPIO, and are controlled by this driver.
221 depends on PLAT_ORION
224 select GENERIC_IRQ_CHIP
230 select GENERIC_IRQ_CHIP
236 select GENERIC_IRQ_CHIP
239 tristate "Cavium OCTEON GPIO"
240 depends on GPIOLIB && CAVIUM_OCTEON_SOC
243 Say yes here to support the on-chip GPIO lines on the OCTEON
247 bool "PrimeCell PL061 GPIO support"
250 select GPIOLIB_IRQCHIP
252 Say yes here to support the PrimeCell PL061 GPIO device
255 bool "PXA GPIO support"
256 depends on ARCH_PXA || ARCH_MMP
258 Say yes here to support the PXA GPIO device
261 tristate "Renesas R-Car GPIO"
264 Say yes here to support GPIO on Renesas R-Car SoCs.
268 depends on PLAT_SAMSUNG
270 Legacy GPIO support. Use only for platforms without support for
274 tristate "SMSC SCH311x SuperI/O GPIO"
276 Driver to enable the GPIOs found on SMSC SMSC SCH3112, SCH3114 and
277 SCH3116 "Super I/O" chipsets.
279 To compile this driver as a module, choose M here: the module will
280 be called gpio-sch311x.
282 config GPIO_SPEAR_SPICS
283 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
284 depends on PLAT_SPEAR
285 select GENERIC_IRQ_CHIP
287 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
290 bool "STA2x11/ConneXt GPIO support"
291 depends on MFD_STA2X11
292 select GENERIC_IRQ_CHIP
294 Say yes here to support the STA2x11/ConneXt GPIO device.
295 The GPIO module has 128 GPIO pins with alternate functions.
298 tristate "GPIO based on SYSCON"
299 depends on MFD_SYSCON && OF
301 Say yes here to support GPIO functionality though SYSCON driver.
304 tristate "TS-5500 DIO blocks and compatibles"
305 depends on TS5500 || COMPILE_TEST
307 This driver supports Digital I/O exposed by pin blocks found on some
308 Technologic Systems platforms. It includes, but is not limited to, 3
309 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
313 bool "Toumaz Xenif TZ1090 GPIO support"
314 depends on SOC_TZ1090
315 select GENERIC_IRQ_CHIP
318 Say yes here to support Toumaz Xenif TZ1090 GPIOs.
320 config GPIO_TZ1090_PDC
321 bool "Toumaz Xenif TZ1090 PDC GPIO support"
322 depends on SOC_TZ1090
325 Say yes here to support Toumaz Xenif TZ1090 PDC GPIOs.
328 bool "Xilinx GPIO support"
329 depends on PPC_OF || MICROBLAZE || ARCH_ZYNQ
331 Say yes here to support the Xilinx FPGA GPIO device
334 bool "Xtensa GPIO32 support"
336 depends on HAVE_XTENSA_GPIO32
339 Say yes here to support the Xtensa internal GPIO32 IMPWIRE (input)
340 and EXPSTATE (output) ports
343 tristate "NEC VR4100 series General-purpose I/O Uint support"
344 depends on CPU_VR41XX
346 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
349 tristate "Intel SCH/TunnelCreek/Centerton GPIO"
350 depends on PCI && X86
354 Say yes here to support GPIO interface on Intel Poulsbo SCH,
355 Intel Tunnel Creek processor or Intel Centerton processor.
356 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
357 powered by the core power rail and are turned off during sleep
358 modes (S3 and higher). The remaining four GPIOs are powered by
359 the Intel SCH suspend power supply. These GPIOs remain
360 active during S3. The suspend powered GPIOs can be used to wake the
361 system from the Suspend-to-RAM state.
362 The Intel Tunnel Creek processor has 5 GPIOs powered by the
363 core power rail and 9 from suspend power supply.
364 The Intel Centerton processor has a total of 30 GPIO pins.
365 Twenty-one are powered by the core power rail and 9 from the
366 suspend power supply.
369 tristate "Intel ICH GPIO"
370 depends on PCI && X86
374 Say yes here to support the GPIO functionality of a number of Intel
375 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
376 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
377 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
382 tristate "Intel IOP GPIO"
383 depends on ARM && (ARCH_IOP32X || ARCH_IOP33X)
385 Say yes here to support the GPIO functionality of a number of Intel
391 tristate "VIA VX855/VX875 GPIO"
396 Support access to the VX855/VX875 GPIO lines through the gpio library.
398 This driver provides common support for accessing the device,
399 additional drivers must be enabled in order to use the
400 functionality of the device.
403 bool "GE FPGA based GPIO"
406 Support for common GPIO functionality provided on some GE Single Board
409 This driver provides basic support (configure as input or output, read
410 and write pin state) for GPIO implemented in a number of GE single
413 config GPIO_LYNXPOINT
414 tristate "Intel Lynxpoint GPIO support"
415 depends on ACPI && X86
418 driver for GPIO functionality on Intel Lynxpoint PCH chipset
419 Requires ACPI device enumeration code to set up a platform device.
422 tristate "Aeroflex Gaisler GRGPIO support"
427 Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
428 VHDL IP core library.
432 select GENERIC_IRQ_CHIP
435 comment "I2C GPIO expanders:"
438 tristate "Wolfson Microelectronics Arizona class devices"
439 depends on MFD_ARIZONA
441 Support for GPIOs on Wolfson Arizona class devices.
444 tristate "TI/National Semiconductor LP3943 GPIO expander"
445 depends on MFD_LP3943
447 GPIO driver for LP3943 MFD.
448 LP3943 can be used as a GPIO expander which provides up to 16 GPIOs.
449 Open drain outputs are required for this usage.
452 tristate "Maxim MAX7300 GPIO expander"
456 GPIO driver for Maxim MAX7300 I2C-based GPIO expander.
459 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
462 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
463 Port Expanders. Each IO port on these chips has a fixed role of
464 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
465 Input and Output (designed by 'P'). The combinations are listed
468 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
469 max7322 (4I4O), max7323 (4P4O)
471 16 bits: max7324 (8I8O), max7325 (8P8O),
472 max7326 (4I12O), max7327 (4P12O)
474 Board setup code must specify the model to use, and the start
475 number for these GPIOs.
477 config GPIO_MAX732X_IRQ
478 bool "Interrupt controller support for MAX732x"
479 depends on GPIO_MAX732X=y
481 Say yes here to enable the max732x to be used as an interrupt
482 controller. It requires the driver to be built in the kernel.
484 config GPIO_MC9S08DZ60
485 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
486 depends on I2C=y && MACH_MX35_3DS
488 Select this to enable the MC9S08DZ60 GPIO driver
491 tristate "PCA95[357]x, PCA9698, TCA64xx, and MAX7310 I/O ports"
494 Say yes here to provide access to several register-oriented
495 SMBus I/O expanders, made mostly by NXP or TI. Compatible
498 4 bits: pca9536, pca9537
500 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
501 pca9556, pca9557, pca9574, tca6408, xra1202
503 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
508 40 bits: pca9505, pca9698
510 config GPIO_PCA953X_IRQ
511 bool "Interrupt controller support for PCA953x"
512 depends on GPIO_PCA953X=y
514 Say yes here to enable the pca953x to be used as an interrupt
515 controller. It requires the driver to be built in the kernel.
518 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
522 Say yes here to provide access to most "quasi-bidirectional" I2C
523 GPIO expanders used for additional digital outputs or inputs.
524 Most of these parts are from NXP, though TI is a second source for
525 some of them. Compatible models include:
527 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
528 pca9670, pca9672, pca9674, pca9674a,
531 16 bits: pcf8575, pcf8575c, pca8575,
532 pca9671, pca9673, pca9675
534 Your board setup code will need to declare the expanders in
535 use, and assign numbers to the GPIOs they expose. Those GPIOs
536 can then be used from drivers and other kernel code, just like
537 other GPIOs, but only accessible from task contexts.
539 This driver provides an in-kernel interface to those GPIOs using
540 platform-neutral GPIO calls.
543 bool "RICOH RC5T583 GPIO"
544 depends on MFD_RC5T583
546 Select this option to enable GPIO driver for the Ricoh RC5T583
548 This driver provides the support for driving/reading the gpio pins
549 of RC5T583 device through standard gpio library.
552 bool "Semtech SX150x I2C GPIO expander"
556 Say yes here to provide support for Semtech SX150-series I2C
557 GPIO expanders. Compatible models include:
566 This enables support for the GPIOs found on the STMPE I/O
570 bool "XWAY STP GPIOs"
573 This enables support for the Serial To Parallel (STP) unit found on
574 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
575 that can be up to 24 bit. This peripheral is aimed at driving leds.
576 Some of the gpios/leds can be auto updated by the soc with dsl and
581 depends on MFD_TC3589X
583 This enables support for the GPIOs found on the TC3589X
587 tristate "TI TPS65912 GPIO"
588 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
590 This driver supports TPS65912 gpio chip
593 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
594 depends on TWL4030_CORE
596 Say yes here to access the GPIO signals of various multi-function
597 power management chips from Texas Instruments.
600 tristate "TWL6040 GPO"
601 depends on TWL6040_CORE
603 Say yes here to access the GPO signals of twl6040
604 audio chip from Texas Instruments.
607 tristate "WM831x GPIOs"
608 depends on MFD_WM831X
610 Say yes here to access the GPIO signals of WM831x power management
611 chips from Wolfson Microelectronics.
614 tristate "WM8350 GPIOs"
615 depends on MFD_WM8350
617 Say yes here to access the GPIO signals of WM8350 power management
618 chips from Wolfson Microelectronics.
621 tristate "WM8994 GPIOs"
622 depends on MFD_WM8994
624 Say yes here to access the GPIO signals of WM8994 audio hub
625 CODECs from Wolfson Microelectronics.
628 tristate "GPIO Support for ADP5520 PMIC"
629 depends on PMIC_ADP5520
631 This option enables support for on-chip GPIO found
632 on Analog Devices ADP5520 PMICs.
635 tristate "ADP5588 I2C GPIO expander"
638 This option enables support for 18 GPIOs found
639 on Analog Devices ADP5588 GPIO Expanders.
641 config GPIO_ADP5588_IRQ
642 bool "Interrupt controller support for ADP5588"
643 depends on GPIO_ADP5588=y
645 Say yes here to enable the adp5588 to be used as an interrupt
646 controller. It requires the driver to be built in the kernel.
649 tristate "Avionic Design N-bit GPIO expander"
650 depends on I2C && OF_GPIO
652 This option enables support for N GPIOs found on Avionic Design
653 I2C GPIO expanders. The register space will be extended by powers
654 of two, so the controller will need to accommodate for that. For
655 example: if a controller provides 48 pins, 6 registers will be
656 enough to represent all pins, but the driver will assume a
657 register layout for 64 pins (8 registers).
659 comment "PCI GPIO expanders:"
662 tristate "AMD CS5535/CS5536 GPIO support"
663 depends on MFD_CS5535
665 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
666 can be used for quite a number of things. The CS5535/6 is found on
667 AMD Geode and Lemote Yeeloong devices.
672 tristate "BT8XX GPIO abuser"
673 depends on PCI && VIDEO_BT848=n
675 The BT8xx frame grabber chip has 24 GPIO pins that can be abused
676 as a cheap PCI GPIO card.
678 This chip can be found on Miro, Hauppauge and STB TV-cards.
680 The card needs to be physically altered for using it as a
681 GPIO card. For more information on how to build a GPIO card
682 from a BT8xx TV card, see the documentation file at
683 Documentation/bt8xxgpio.txt
688 tristate "AMD 8111 GPIO driver"
691 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
693 Note, that usually system firmware/ACPI handles GPIO pins on their
694 own and users might easily break their systems with uncarefull usage
699 config GPIO_INTEL_MID
700 bool "Intel Mid GPIO support"
701 depends on PCI && X86
704 Say Y here to support Intel Mid GPIO.
707 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
708 depends on PCI && X86
709 select GENERIC_IRQ_CHIP
711 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
712 which is an IOH(Input/Output Hub) for x86 embedded processor.
713 This driver can access PCH GPIO device.
715 This driver also can be used for LAPIS Semiconductor IOH(Input/
716 Output Hub), ML7223 and ML7831.
717 ML7223 IOH is for MP(Media Phone) use.
718 ML7831 IOH is for general purpose use.
719 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
720 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
723 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
725 select GENERIC_IRQ_CHIP
727 ML7213 is companion chip for Intel Atom E6xx series.
728 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
729 Hub) which is for IVI(In-Vehicle Infotainment) use.
730 This driver can access the IOH's GPIO device.
732 config GPIO_SODAVILLE
733 bool "Intel Sodaville GPIO support"
734 depends on X86 && PCI && OF
736 select GENERIC_IRQ_CHIP
738 Say Y here to support Intel Sodaville GPIO.
740 config GPIO_TIMBERDALE
741 bool "Support for timberdale GPIO IP"
742 depends on MFD_TIMBERDALE && HAS_IOMEM
744 Add support for the GPIO IP in the timberdale FPGA.
747 tristate "RDC R-321x GPIO support"
752 Support for the RDC R321x SoC GPIOs over southbridge
753 PCI configuration space.
755 comment "SPI GPIO expanders:"
758 tristate "Maxim MAX7301 GPIO expander"
759 depends on SPI_MASTER
762 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
765 tristate "Microchip MCP23xxx I/O expander"
767 depends on (SPI_MASTER && !I2C) || I2C
769 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
771 This provides a GPIO interface supporting inputs and outputs.
772 The I2C versions of the chips can be used as interrupt-controller.
775 tristate "Freescale MC33880 high-side/low-side switch"
776 depends on SPI_MASTER
778 SPI driver for Freescale MC33880 high-side/low-side switch.
779 This provides GPIO interface supporting inputs and outputs.
782 tristate "74x164 serial-in/parallel-out 8-bits shift register"
783 depends on SPI_MASTER && OF
785 Driver for 74x164 compatible serial-in/parallel-out 8-outputs
786 shift registers. This driver can be used to provide access
787 to more gpio outputs.
789 comment "AC97 GPIO expanders:"
792 tristate "Philips UCB1400 GPIO"
793 depends on UCB1400_CORE
795 This enables support for the Philips UCB1400 GPIO pins.
796 The UCB1400 is an AC97 audio codec.
798 comment "LPC GPIO expanders:"
801 tristate "Kontron ETX / COMexpress GPIO"
802 depends on MFD_KEMPLD
804 This enables support for the PLD GPIO interface on some Kontron ETX
805 and COMexpress (ETXexpress) modules.
807 This driver can also be built as a module. If so, the module will be
810 comment "MODULbus GPIO expanders:"
813 tristate "Janz VMOD-TTL Digital IO Module"
814 depends on MFD_JANZ_CMODIO
816 This enables support for the Janz VMOD-TTL Digital IO module.
817 This driver provides support for driving the pins in output
818 mode only. Input mode is not supported.
821 bool "TI PALMAS series PMICs GPIO"
822 depends on MFD_PALMAS
824 Select this option to enable GPIO driver for the TI PALMAS
829 depends on MFD_TPS6586X
831 Select this option to enable GPIO driver for the TPS6586X
836 depends on MFD_TPS65910
838 Select this option to enable GPIO driver for the TPS65910
842 bool "Intel MSIC mixed signal gpio support"
843 depends on MFD_INTEL_MSIC
845 Enable support for GPIO on intel MSIC controllers found in
849 bool "Broadcom Kona GPIO"
852 Turn on GPIO support for Broadcom "Kona" chips.
854 comment "USB GPIO expanders:"
856 config GPIO_VIPERBOARD
857 tristate "Viperboard GPIO a & b support"
858 depends on MFD_VIPERBOARD && USB
860 Say yes here to access the GPIO signals of Nano River
861 Technologies Viperboard. There are two GPIO chips on the
862 board: gpioa and gpiob.
863 See viperboard API specification and Nano
864 River Tech's viperboard.h for detailed meaning
865 of the module parameters.