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
63 bool "Debug GPIO calls"
64 depends on DEBUG_KERNEL
66 Say Y here to add some extra checks and diagnostics to GPIO calls.
67 These checks help ensure that GPIOs have been properly initialized
68 before they are used, and that sleeping calls are not made from
69 non-sleeping contexts. They can make bitbanged serial protocols
70 slower. The diagnostics help catch the type of setup errors
71 that are most common when setting up new platforms or boards.
74 bool "/sys/class/gpio/... (sysfs interface)"
77 Say Y here to add a sysfs interface for GPIOs.
79 This is mostly useful to work around omissions in a system's
80 kernel support. Those are common in custom and semicustom
81 hardware assembled using standard kernels with a minimum of
82 custom patches. In those cases, userspace code may import
83 a given GPIO from the kernel, if no kernel driver requested it.
85 Kernel drivers may also request that a particular GPIO be
86 exported to userspace; this can be useful when debugging.
91 # put drivers in the right section, in alphabetical order
93 # This symbol is selected by both I2C and SPI expanders
97 menu "Memory mapped GPIO drivers"
100 tristate "GPIO driver for 74xx-ICs with MMIO access"
104 Say yes here to support GPIO functionality for 74xx-compatible ICs
105 with MMIO access. Compatible models include:
106 1 bit: 741G125 (Input), 741G74 (Output)
107 2 bits: 742G125 (Input), 7474 (Output)
108 4 bits: 74125 (Input), 74175 (Output)
109 6 bits: 74365 (Input), 74174 (Output)
110 8 bits: 74244 (Input), 74273 (Output)
111 16 bits: 741624 (Input), 7416374 (Output)
114 tristate "Altera GPIO"
116 select GPIOLIB_IRQCHIP
118 Say Y or M here to build support for the Altera PIO device.
120 If driver is built as a module it will be called gpio-altera.
123 tristate "AMD Promontory GPIO support"
126 driver for GPIO functionality on Promontory IOHub
127 Require ACPI ASL code to enumerate as a platform device.
130 bool "Broadcom Kona GPIO"
131 depends on OF_GPIO && (ARCH_BCM_MOBILE || COMPILE_TEST)
133 Turn on GPIO support for Broadcom "Kona" chips.
136 tristate "BRCMSTB GPIO support"
137 default y if (ARCH_BRCMSTB || BMIPS_GENERIC)
138 depends on OF_GPIO && (ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST)
140 select GPIOLIB_IRQCHIP
142 Say yes here to enable GPIO support for Broadcom STB (BCM7XXX) SoCs.
145 tristate "CLPS711X GPIO support"
146 depends on ARCH_CLPS711X || COMPILE_TEST
149 Say yes here to support GPIO on CLPS711X SoCs.
152 bool "TI Davinci/Keystone GPIO support"
153 default y if ARCH_DAVINCI
154 depends on ARM && (ARCH_DAVINCI || ARCH_KEYSTONE)
156 Say yes here to enable GPIO support for TI Davinci/Keystone SoCs.
159 tristate "Synopsys DesignWare APB GPIO driver"
161 select GENERIC_IRQ_CHIP
163 Say Y or M here to build support for the Synopsys DesignWare APB
167 tristate "Emma Mobile GPIO"
168 depends on ARM && OF_GPIO
170 Say yes here to support GPIO on Renesas Emma Mobile SoCs.
174 depends on ARCH_EP93XX
178 bool "Axis ETRAX FS General I/O"
179 depends on CRIS || COMPILE_TEST
182 select GPIOLIB_IRQCHIP
184 Say yes here to support the GPIO controller on Axis ETRAX FS SoCs.
187 bool "GE FPGA based GPIO"
191 Support for common GPIO functionality provided on some GE Single Board
194 This driver provides basic support (configure as input or output, read
195 and write pin state) for GPIO implemented in a number of GE single
198 config GPIO_GENERIC_PLATFORM
199 tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
202 Say yes here to support basic platform_device memory-mapped GPIO controllers.
205 tristate "Aeroflex Gaisler GRGPIO support"
210 Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
211 VHDL IP core library.
214 tristate "Intel ICH GPIO"
215 depends on PCI && X86
219 Say yes here to support the GPIO functionality of a number of Intel
220 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
221 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
222 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
227 tristate "Intel IOP GPIO"
228 depends on ARM && (ARCH_IOP32X || ARCH_IOP33X)
230 Say yes here to support the GPIO functionality of a number of Intel
236 bool "Loongson-2/3 GPIO support"
237 depends on CPU_LOONGSON2 || CPU_LOONGSON3
239 driver for GPIO functionality on Loongson-2F/3A/3B processors.
242 bool "NXP LPC18XX/43XX GPIO support"
243 default y if ARCH_LPC18XX
244 depends on OF_GPIO && (ARCH_LPC18XX || COMPILE_TEST)
246 Select this option to enable GPIO driver for
247 NXP LPC18XX/43XX devices.
249 config GPIO_LYNXPOINT
250 tristate "Intel Lynxpoint GPIO support"
251 depends on ACPI && X86
252 select GPIOLIB_IRQCHIP
254 driver for GPIO functionality on Intel Lynxpoint PCH chipset
255 Requires ACPI device enumeration code to set up a platform device.
258 bool "GPIO support for Fujitsu MB86S7x Platforms"
259 depends on ARCH_MB86S7X
261 Say yes here to support the GPIO controller in Fujitsu MB86S70 SoCs.
263 config GPIO_MM_LANTIQ
264 bool "Lantiq Memory mapped GPIOs"
265 depends on LANTIQ && SOC_XWAY
267 This enables support for memory mapped GPIOs on the External Bus Unit
268 (EBU) found on Lantiq SoCs. The gpios are output only as they are
269 created by attaching a 16bit latch to the bus.
272 bool "MOXART GPIO support"
273 depends on ARCH_MOXART
276 Select this option to enable GPIO driver for
277 MOXA ART SoC devices.
281 depends on PPC_MPC52xx
284 bool "MPC512x/MPC8xxx GPIO support"
285 depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \
286 FSL_SOC_BOOKE || PPC_86xx
288 Say Y here if you're going to use hardware that connects to the
289 MPC512x/831x/834x/837x/8572/8610 GPIOs.
293 depends on PLAT_ORION
295 select GENERIC_IRQ_CHIP
301 select GENERIC_IRQ_CHIP
307 select GENERIC_IRQ_CHIP
310 tristate "Cavium OCTEON GPIO"
311 depends on GPIOLIB && CAVIUM_OCTEON_SOC
314 Say yes here to support the on-chip GPIO lines on the OCTEON
318 tristate "TI OMAP GPIO support" if ARCH_OMAP2PLUS || COMPILE_TEST
319 default y if ARCH_OMAP
321 select GENERIC_IRQ_CHIP
322 select GPIOLIB_IRQCHIP
324 Say yes here to enable GPIO support for TI OMAP SoCs.
327 bool "PrimeCell PL061 GPIO support"
330 select GPIOLIB_IRQCHIP
332 Say yes here to support the PrimeCell PL061 GPIO device
335 bool "PXA GPIO support"
336 depends on ARCH_PXA || ARCH_MMP
338 Say yes here to support the PXA GPIO device
341 tristate "Renesas R-Car GPIO"
342 depends on ARCH_SHMOBILE || COMPILE_TEST
343 select GPIOLIB_IRQCHIP
345 Say yes here to support GPIO on Renesas R-Car SoCs.
347 config GPIO_SPEAR_SPICS
348 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
349 depends on PLAT_SPEAR
350 select GENERIC_IRQ_CHIP
352 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
355 bool "STA2x11/ConneXt GPIO support"
356 depends on MFD_STA2X11
357 select GENERIC_IRQ_CHIP
359 Say yes here to support the STA2x11/ConneXt GPIO device.
360 The GPIO module has 128 GPIO pins with alternate functions.
363 bool "XWAY STP GPIOs"
366 This enables support for the Serial To Parallel (STP) unit found on
367 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
368 that can be up to 24 bit. This peripheral is aimed at driving leds.
369 Some of the gpios/leds can be auto updated by the soc with dsl and
373 tristate "GPIO based on SYSCON"
374 depends on MFD_SYSCON && OF
376 Say yes here to support GPIO functionality though SYSCON driver.
380 select GENERIC_IRQ_CHIP
384 bool "Toumaz Xenif TZ1090 GPIO support"
385 depends on SOC_TZ1090
386 select GENERIC_IRQ_CHIP
389 Say yes here to support Toumaz Xenif TZ1090 GPIOs.
391 config GPIO_TZ1090_PDC
392 bool "Toumaz Xenif TZ1090 PDC GPIO support"
393 depends on SOC_TZ1090
396 Say yes here to support Toumaz Xenif TZ1090 PDC GPIOs.
400 depends on ARCH_MXC && SOC_VF610
401 select GPIOLIB_IRQCHIP
403 Say yes here to support Vybrid vf610 GPIOs.
406 tristate "NEC VR4100 series General-purpose I/O Uint support"
407 depends on CPU_VR41XX
409 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
412 tristate "VIA VX855/VX875 GPIO"
417 Support access to the VX855/VX875 GPIO lines through the gpio library.
419 This driver provides common support for accessing the device,
420 additional drivers must be enabled in order to use the
421 functionality of the device.
424 bool "APM X-Gene GPIO controller support"
425 depends on ARM64 && OF_GPIO
427 This driver is to support the GPIO block within the APM X-Gene SoC
428 platform's generic flash controller. The GPIO pins are muxed with
429 the generic flash controller's address and data pins. Say yes
430 here to enable the GFC GPIO functionality.
433 tristate "APM X-Gene GPIO standby controller support"
434 depends on ARCH_XGENE && OF_GPIO
437 This driver supports the GPIO block within the APM X-Gene
438 Standby Domain. Say yes here to enable the GPIO functionality.
441 tristate "Xilinx GPIO support"
444 Say yes here to support the Xilinx FPGA GPIO device
447 tristate "Netlogic XLP GPIO support"
448 depends on CPU_XLP && OF_GPIO
449 select GPIOLIB_IRQCHIP
451 This driver provides support for GPIO interface on Netlogic XLP MIPS64
452 SoCs. Currently supported XLP variants are XLP8XX, XLP3XX, XLP2XX,
458 bool "Xtensa GPIO32 support"
460 depends on HAVE_XTENSA_GPIO32
463 Say yes here to support the Xtensa internal GPIO32 IMPWIRE (input)
464 and EXPSTATE (output) ports
467 bool "LSI ZEVIO SoC memory mapped GPIOs"
468 depends on ARM && OF_GPIO
470 Say yes here to support the GPIO controller in LSI ZEVIO SoCs.
473 tristate "Xilinx Zynq GPIO support"
474 depends on ARCH_ZYNQ || ARCH_ZYNQMP
475 select GPIOLIB_IRQCHIP
477 Say yes here to support Xilinx Zynq GPIO controller.
480 bool "ZTE ZX GPIO support"
481 select GPIOLIB_IRQCHIP
483 Say yes here to support the GPIO device on ZTE ZX SoCs.
487 menu "Port-mapped I/O GPIO drivers"
488 depends on X86 # Unconditional I/O space access
490 config GPIO_104_DIO_48E
491 tristate "ACCES 104-DIO-48E GPIO support"
492 select GPIOLIB_IRQCHIP
494 Enables GPIO support for the ACCES 104-DIO-48E family. The base port
495 address for the device may be configured via the dio_48e_base module
496 parameter. The interrupt line number for the device may be configured
497 via the dio_48e_irq module parameter.
499 config GPIO_104_IDIO_16
500 tristate "ACCES 104-IDIO-16 GPIO support"
501 select GPIOLIB_IRQCHIP
503 Enables GPIO support for the ACCES 104-IDIO-16 family. The base port
504 address for the device may be set via the idio_16_base module
505 parameter. The interrupt line number for the device may be set via the
506 idio_16_irq module parameter.
508 config GPIO_104_IDI_48
509 tristate "ACCES 104-IDI-48 GPIO support"
510 select GPIOLIB_IRQCHIP
512 Enables GPIO support for the ACCES 104-IDI-48 family. The base port
513 address for the device may be configured via the idi_48_base module
514 parameter. The interrupt line number for the device may be configured
515 via the idi_48_irq module parameter.
518 tristate "F71869, F71869A, F71882FG and F71889F GPIO support"
520 This option enables support for GPIOs found on Fintek Super-I/O
521 chips F71869, F71869A, F71882FG and F71889F.
523 To compile this driver as a module, choose M here: the module will
524 be called f7188x-gpio.
527 tristate "IT87xx GPIO support"
529 Say yes here to support GPIO functionality of IT87xx Super I/O chips.
531 This driver is tested with ITE IT8728 and IT8732 Super I/O chips, and
532 supports the IT8761E Super I/O chip as well.
534 To compile this driver as a module, choose M here: the module will
538 tristate "Intel SCH/TunnelCreek/Centerton/Quark X1000 GPIO"
543 Say yes here to support GPIO interface on Intel Poulsbo SCH,
544 Intel Tunnel Creek processor, Intel Centerton processor or
545 Intel Quark X1000 SoC.
547 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
548 powered by the core power rail and are turned off during sleep
549 modes (S3 and higher). The remaining four GPIOs are powered by
550 the Intel SCH suspend power supply. These GPIOs remain
551 active during S3. The suspend powered GPIOs can be used to wake the
552 system from the Suspend-to-RAM state.
554 The Intel Tunnel Creek processor has 5 GPIOs powered by the
555 core power rail and 9 from suspend power supply.
557 The Intel Centerton processor has a total of 30 GPIO pins.
558 Twenty-one are powered by the core power rail and 9 from the
559 suspend power supply.
561 The Intel Quark X1000 SoC has 2 GPIOs powered by the core
562 power well and 6 from the suspend power well.
565 tristate "SMSC SCH311x SuperI/O GPIO"
567 Driver to enable the GPIOs found on SMSC SMSC SCH3112, SCH3114 and
568 SCH3116 "Super I/O" chipsets.
570 To compile this driver as a module, choose M here: the module will
571 be called gpio-sch311x.
574 tristate "TS-5500 DIO blocks and compatibles"
575 depends on TS5500 || COMPILE_TEST
577 This driver supports Digital I/O exposed by pin blocks found on some
578 Technologic Systems platforms. It includes, but is not limited to, 3
579 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
583 tristate "WinSystems WS16C48 GPIO support"
584 select GPIOLIB_IRQCHIP
586 Enables GPIO support for the WinSystems WS16C48. The base port address
587 for the device may be configured via the ws16c48_base module
588 parameter. The interrupt line number for the device may be configured
589 via the ws16c48_irq module parameter.
593 menu "I2C GPIO expanders"
597 tristate "ADP5588 I2C GPIO expander"
599 This option enables support for 18 GPIOs found
600 on Analog Devices ADP5588 GPIO Expanders.
602 config GPIO_ADP5588_IRQ
603 bool "Interrupt controller support for ADP5588"
604 depends on GPIO_ADP5588=y
606 Say yes here to enable the adp5588 to be used as an interrupt
607 controller. It requires the driver to be built in the kernel.
610 tristate "Avionic Design N-bit GPIO expander"
612 select GPIOLIB_IRQCHIP
614 This option enables support for N GPIOs found on Avionic Design
615 I2C GPIO expanders. The register space will be extended by powers
616 of two, so the controller will need to accommodate for that. For
617 example: if a controller provides 48 pins, 6 registers will be
618 enough to represent all pins, but the driver will assume a
619 register layout for 64 pins (8 registers).
622 tristate "Maxim MAX7300 GPIO expander"
625 GPIO driver for Maxim MAX7300 I2C-based GPIO expander.
628 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
630 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
631 Port Expanders. Each IO port on these chips has a fixed role of
632 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
633 Input and Output (designed by 'P'). The combinations are listed
636 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
637 max7322 (4I4O), max7323 (4P4O)
639 16 bits: max7324 (8I8O), max7325 (8P8O),
640 max7326 (4I12O), max7327 (4P12O)
642 Board setup code must specify the model to use, and the start
643 number for these GPIOs.
645 config GPIO_MAX732X_IRQ
646 bool "Interrupt controller support for MAX732x"
647 depends on GPIO_MAX732X=y
648 select GPIOLIB_IRQCHIP
650 Say yes here to enable the max732x to be used as an interrupt
651 controller. It requires the driver to be built in the kernel.
653 config GPIO_MC9S08DZ60
654 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
655 depends on I2C=y && MACH_MX35_3DS
657 Select this to enable the MC9S08DZ60 GPIO driver
660 tristate "PCA95[357]x, PCA9698, TCA64xx, and MAX7310 I/O ports"
662 Say yes here to provide access to several register-oriented
663 SMBus I/O expanders, made mostly by NXP or TI. Compatible
666 4 bits: pca9536, pca9537
668 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
669 pca9556, pca9557, pca9574, tca6408, xra1202
671 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
676 40 bits: pca9505, pca9698
678 config GPIO_PCA953X_IRQ
679 bool "Interrupt controller support for PCA953x"
680 depends on GPIO_PCA953X=y
681 select GPIOLIB_IRQCHIP
683 Say yes here to enable the pca953x to be used as an interrupt
684 controller. It requires the driver to be built in the kernel.
687 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
688 select GPIOLIB_IRQCHIP
691 Say yes here to provide access to most "quasi-bidirectional" I2C
692 GPIO expanders used for additional digital outputs or inputs.
693 Most of these parts are from NXP, though TI is a second source for
694 some of them. Compatible models include:
696 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
697 pca9670, pca9672, pca9674, pca9674a,
700 16 bits: pcf8575, pcf8575c, pca8575,
701 pca9671, pca9673, pca9675
703 Your board setup code will need to declare the expanders in
704 use, and assign numbers to the GPIOs they expose. Those GPIOs
705 can then be used from drivers and other kernel code, just like
706 other GPIOs, but only accessible from task contexts.
708 This driver provides an in-kernel interface to those GPIOs using
709 platform-neutral GPIO calls.
712 bool "Semtech SX150x I2C GPIO expander"
714 select GPIOLIB_IRQCHIP
717 Say yes here to provide support for Semtech SX150-series I2C
718 GPIO expanders. Compatible models include:
725 menu "MFD GPIO expanders"
728 tristate "GPIO Support for ADP5520 PMIC"
729 depends on PMIC_ADP5520
731 This option enables support for on-chip GPIO found
732 on Analog Devices ADP5520 PMICs.
735 tristate "Wolfson Microelectronics Arizona class devices"
736 depends on MFD_ARIZONA
738 Support for GPIOs on Wolfson Arizona class devices.
740 config GPIO_CRYSTAL_COVE
741 tristate "GPIO support for Crystal Cove PMIC"
742 depends on INTEL_SOC_PMIC
743 select GPIOLIB_IRQCHIP
745 Support for GPIO pins on Crystal Cove PMIC.
747 Say Yes if you have a Intel SoC based tablet with Crystal Cove PMIC
750 This driver can also be built as a module. If so, the module will be
751 called gpio-crystalcove.
754 tristate "AMD CS5535/CS5536 GPIO support"
755 depends on MFD_CS5535
757 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
758 can be used for quite a number of things. The CS5535/6 is found on
759 AMD Geode and Lemote Yeeloong devices.
764 tristate "Dialog DA9052 GPIO"
765 depends on PMIC_DA9052
767 Say yes here to enable the GPIO driver for the DA9052 chip.
770 tristate "Dialog Semiconductor DA9055 GPIO"
771 depends on MFD_DA9055
773 Say yes here to enable the GPIO driver for the DA9055 chip.
775 The Dialog DA9055 PMIC chip has 3 GPIO pins that can be
776 be controller by this driver.
778 If driver is built as a module it will be called gpio-da9055.
781 tristate "Diolan DLN2 GPIO support"
783 select GPIOLIB_IRQCHIP
786 Select this option to enable GPIO driver for the Diolan DLN2
789 This driver can also be built as a module. If so, the module
790 will be called gpio-dln2.
793 tristate "Janz VMOD-TTL Digital IO Module"
794 depends on MFD_JANZ_CMODIO
796 This enables support for the Janz VMOD-TTL Digital IO module.
797 This driver provides support for driving the pins in output
798 mode only. Input mode is not supported.
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
811 tristate "TI/National Semiconductor LP3943 GPIO expander"
812 depends on MFD_LP3943
814 GPIO driver for LP3943 MFD.
815 LP3943 can be used as a GPIO expander which provides up to 16 GPIOs.
816 Open drain outputs are required for this usage.
819 bool "Intel MSIC mixed signal gpio support"
820 depends on MFD_INTEL_MSIC
822 Enable support for GPIO on intel MSIC controllers found in
826 bool "TI PALMAS series PMICs GPIO"
827 depends on MFD_PALMAS
829 Select this option to enable GPIO driver for the TI PALMAS
833 bool "RICOH RC5T583 GPIO"
834 depends on MFD_RC5T583
836 Select this option to enable GPIO driver for the Ricoh RC5T583
838 This driver provides the support for driving/reading the gpio pins
839 of RC5T583 device through standard gpio library.
845 select GPIOLIB_IRQCHIP
847 This enables support for the GPIOs found on the STMPE I/O
852 depends on MFD_TC3589X
854 select GPIOLIB_IRQCHIP
856 This enables support for the GPIOs found on the TC3589X
859 config GPIO_TIMBERDALE
860 bool "Support for timberdale GPIO IP"
861 depends on MFD_TIMBERDALE
863 Add support for the GPIO IP in the timberdale FPGA.
867 depends on MFD_TPS6586X
869 Select this option to enable GPIO driver for the TPS6586X
874 depends on MFD_TPS65910
876 Select this option to enable GPIO driver for the TPS65910
880 tristate "TI TPS65912 GPIO"
881 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
883 This driver supports TPS65912 gpio chip
886 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
887 depends on TWL4030_CORE
889 Say yes here to access the GPIO signals of various multi-function
890 power management chips from Texas Instruments.
893 tristate "TWL6040 GPO"
894 depends on TWL6040_CORE
896 Say yes here to access the GPO signals of twl6040
897 audio chip from Texas Instruments.
900 tristate "Philips UCB1400 GPIO"
901 depends on UCB1400_CORE
903 This enables support for the Philips UCB1400 GPIO pins.
904 The UCB1400 is an AC97 audio codec.
907 tristate "WM831x GPIOs"
908 depends on MFD_WM831X
910 Say yes here to access the GPIO signals of WM831x power management
911 chips from Wolfson Microelectronics.
914 tristate "WM8350 GPIOs"
915 depends on MFD_WM8350
917 Say yes here to access the GPIO signals of WM8350 power management
918 chips from Wolfson Microelectronics.
921 tristate "WM8994 GPIOs"
922 depends on MFD_WM8994
924 Say yes here to access the GPIO signals of WM8994 audio hub
925 CODECs from Wolfson Microelectronics.
929 menu "PCI GPIO expanders"
933 tristate "AMD 8111 GPIO driver"
935 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
937 Note, that usually system firmware/ACPI handles GPIO pins on their
938 own and users might easily break their systems with uncarefull usage
944 tristate "BT8XX GPIO abuser"
945 depends on VIDEO_BT848=n
947 The BT8xx frame grabber chip has 24 GPIO pins that can be abused
948 as a cheap PCI GPIO card.
950 This chip can be found on Miro, Hauppauge and STB TV-cards.
952 The card needs to be physically altered for using it as a
953 GPIO card. For more information on how to build a GPIO card
954 from a BT8xx TV card, see the documentation file at
955 Documentation/bt8xxgpio.txt
959 config GPIO_INTEL_MID
960 bool "Intel Mid GPIO support"
962 select GPIOLIB_IRQCHIP
964 Say Y here to support Intel Mid GPIO.
967 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
968 select GENERIC_IRQ_CHIP
970 ML7213 is companion chip for Intel Atom E6xx series.
971 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
972 Hub) which is for IVI(In-Vehicle Infotainment) use.
973 This driver can access the IOH's GPIO device.
976 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
977 depends on X86_32 || MIPS || COMPILE_TEST
978 select GENERIC_IRQ_CHIP
980 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
981 which is an IOH(Input/Output Hub) for x86 embedded processor.
982 This driver can access PCH GPIO device.
984 This driver also can be used for LAPIS Semiconductor IOH(Input/
985 Output Hub), ML7223 and ML7831.
986 ML7223 IOH is for MP(Media Phone) use.
987 ML7831 IOH is for general purpose use.
988 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
989 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
992 tristate "RDC R-321x GPIO support"
996 Support for the RDC R321x SoC GPIOs over southbridge
997 PCI configuration space.
999 config GPIO_SODAVILLE
1000 bool "Intel Sodaville GPIO support"
1001 depends on X86 && OF
1003 select GENERIC_IRQ_CHIP
1005 Say Y here to support Intel Sodaville GPIO.
1009 menu "SPI GPIO expanders"
1010 depends on SPI_MASTER
1013 tristate "74x164 serial-in/parallel-out 8-bits shift register"
1016 Driver for 74x164 compatible serial-in/parallel-out 8-outputs
1017 shift registers. This driver can be used to provide access
1018 to more gpio outputs.
1021 tristate "Maxim MAX7301 GPIO expander"
1024 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
1027 tristate "Freescale MC33880 high-side/low-side switch"
1029 SPI driver for Freescale MC33880 high-side/low-side switch.
1030 This provides GPIO interface supporting inputs and outputs.
1034 menu "SPI or I2C GPIO expanders"
1035 depends on (SPI_MASTER && !I2C) || I2C
1037 config GPIO_MCP23S08
1038 tristate "Microchip MCP23xxx I/O expander"
1040 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
1042 This provides a GPIO interface supporting inputs and outputs.
1043 The I2C versions of the chips can be used as interrupt-controller.
1047 menu "USB GPIO expanders"
1050 config GPIO_VIPERBOARD
1051 tristate "Viperboard GPIO a & b support"
1052 depends on MFD_VIPERBOARD
1054 Say yes here to access the GPIO signals of Nano River
1055 Technologies Viperboard. There are two GPIO chips on the
1056 board: gpioa and gpiob.
1057 See viperboard API specification and Nano
1058 River Tech's viperboard.h for detailed meaning
1059 of the module parameters.