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"
117 select GPIOLIB_IRQCHIP
119 Say Y or M here to build support for the Altera PIO device.
121 If driver is built as a module it will be called gpio-altera.
124 bool "Broadcom Kona GPIO"
125 depends on OF_GPIO && (ARCH_BCM_MOBILE || COMPILE_TEST)
127 Turn on GPIO support for Broadcom "Kona" chips.
130 tristate "BRCMSTB GPIO support"
131 default y if ARCH_BRCMSTB
132 depends on OF_GPIO && (ARCH_BRCMSTB || COMPILE_TEST)
135 Say yes here to enable GPIO support for Broadcom STB (BCM7XXX) SoCs.
138 tristate "CLPS711X GPIO support"
139 depends on ARCH_CLPS711X || COMPILE_TEST
142 Say yes here to support GPIO on CLPS711X SoCs.
145 bool "TI Davinci/Keystone GPIO support"
146 default y if ARCH_DAVINCI
147 depends on ARM && (ARCH_DAVINCI || ARCH_KEYSTONE)
149 Say yes here to enable GPIO support for TI Davinci/Keystone SoCs.
152 tristate "Synopsys DesignWare APB GPIO driver"
154 select GENERIC_IRQ_CHIP
156 Say Y or M here to build support for the Synopsys DesignWare APB
160 tristate "Emma Mobile GPIO"
161 depends on ARM && OF_GPIO
163 Say yes here to support GPIO on Renesas Emma Mobile SoCs.
167 depends on ARCH_EP93XX
171 bool "Axis ETRAX FS General I/O"
172 depends on CRIS || COMPILE_TEST
176 Say yes here to support the GPIO controller on Axis ETRAX FS SoCs.
179 tristate "F71869, F71869A, F71882FG and F71889F GPIO support"
182 This option enables support for GPIOs found on Fintek Super-I/O
183 chips F71869, F71869A, F71882FG and F71889F.
185 To compile this driver as a module, choose M here: the module will
186 be called f7188x-gpio.
189 bool "GE FPGA based GPIO"
193 Support for common GPIO functionality provided on some GE Single Board
196 This driver provides basic support (configure as input or output, read
197 and write pin state) for GPIO implemented in a number of GE single
200 config GPIO_GENERIC_PLATFORM
201 tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
204 Say yes here to support basic platform_device memory-mapped GPIO controllers.
207 tristate "Aeroflex Gaisler GRGPIO support"
212 Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
213 VHDL IP core library.
216 tristate "Intel ICH GPIO"
217 depends on PCI && X86
221 Say yes here to support the GPIO functionality of a number of Intel
222 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
223 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
224 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
229 tristate "Intel IOP GPIO"
230 depends on ARM && (ARCH_IOP32X || ARCH_IOP33X)
232 Say yes here to support the GPIO functionality of a number of Intel
238 tristate "IT8761E GPIO support"
239 depends on X86 # unconditional access to IO space.
241 Say yes here to support GPIO functionality of IT8761E super I/O chip.
244 bool "Loongson-2/3 GPIO support"
245 depends on CPU_LOONGSON2 || CPU_LOONGSON3
247 driver for GPIO functionality on Loongson-2F/3A/3B processors.
250 bool "NXP LPC18XX/43XX GPIO support"
251 default y if ARCH_LPC18XX
252 depends on OF_GPIO && (ARCH_LPC18XX || COMPILE_TEST)
254 Select this option to enable GPIO driver for
255 NXP LPC18XX/43XX devices.
257 config GPIO_LYNXPOINT
258 tristate "Intel Lynxpoint GPIO support"
259 depends on ACPI && X86
260 select GPIOLIB_IRQCHIP
262 driver for GPIO functionality on Intel Lynxpoint PCH chipset
263 Requires ACPI device enumeration code to set up a platform device.
266 bool "GPIO support for Fujitsu MB86S7x Platforms"
267 depends on ARCH_MB86S7X
269 Say yes here to support the GPIO controller in Fujitsu MB86S70 SoCs.
271 config GPIO_MM_LANTIQ
272 bool "Lantiq Memory mapped GPIOs"
273 depends on LANTIQ && SOC_XWAY
275 This enables support for memory mapped GPIOs on the External Bus Unit
276 (EBU) found on Lantiq SoCs. The gpios are output only as they are
277 created by attaching a 16bit latch to the bus.
280 bool "MOXART GPIO support"
281 depends on ARCH_MOXART
284 Select this option to enable GPIO driver for
285 MOXA ART SoC devices.
289 depends on PPC_MPC52xx
292 bool "MPC512x/MPC8xxx GPIO support"
293 depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \
294 FSL_SOC_BOOKE || PPC_86xx
296 Say Y here if you're going to use hardware that connects to the
297 MPC512x/831x/834x/837x/8572/8610 GPIOs.
300 tristate "Qualcomm MSM GPIO v2"
301 depends on GPIOLIB && OF && ARCH_QCOM
303 Say yes here to support the GPIO interface on ARM v7 based
304 Qualcomm MSM chips. Most of the pins on the MSM can be
305 selected for GPIO, and are controlled by this driver.
309 depends on PLAT_ORION
312 select GENERIC_IRQ_CHIP
318 select GENERIC_IRQ_CHIP
324 select GENERIC_IRQ_CHIP
327 tristate "Cavium OCTEON GPIO"
328 depends on GPIOLIB && CAVIUM_OCTEON_SOC
331 Say yes here to support the on-chip GPIO lines on the OCTEON
335 tristate "TI OMAP GPIO support" if ARCH_OMAP2PLUS || COMPILE_TEST
336 default y if ARCH_OMAP
338 select GENERIC_IRQ_CHIP
339 select GPIOLIB_IRQCHIP
341 Say yes here to enable GPIO support for TI OMAP SoCs.
344 bool "PrimeCell PL061 GPIO support"
347 select GPIOLIB_IRQCHIP
349 Say yes here to support the PrimeCell PL061 GPIO device
352 bool "PXA GPIO support"
353 depends on ARCH_PXA || ARCH_MMP
355 Say yes here to support the PXA GPIO device
358 tristate "Renesas R-Car GPIO"
359 depends on ARM && (ARCH_SHMOBILE || COMPILE_TEST)
360 select GPIOLIB_IRQCHIP
362 Say yes here to support GPIO on Renesas R-Car SoCs.
366 depends on PLAT_SAMSUNG
368 Legacy GPIO support. Use only for platforms without support for
372 tristate "Intel SCH/TunnelCreek/Centerton/Quark X1000 GPIO"
373 depends on PCI && X86
377 Say yes here to support GPIO interface on Intel Poulsbo SCH,
378 Intel Tunnel Creek processor, Intel Centerton processor or
379 Intel Quark X1000 SoC.
381 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
382 powered by the core power rail and are turned off during sleep
383 modes (S3 and higher). The remaining four GPIOs are powered by
384 the Intel SCH suspend power supply. These GPIOs remain
385 active during S3. The suspend powered GPIOs can be used to wake the
386 system from the Suspend-to-RAM state.
388 The Intel Tunnel Creek processor has 5 GPIOs powered by the
389 core power rail and 9 from suspend power supply.
391 The Intel Centerton processor has a total of 30 GPIO pins.
392 Twenty-one are powered by the core power rail and 9 from the
393 suspend power supply.
395 The Intel Quark X1000 SoC has 2 GPIOs powered by the core
396 power well and 6 from the suspend power well.
399 tristate "SMSC SCH311x SuperI/O GPIO"
401 Driver to enable the GPIOs found on SMSC SMSC SCH3112, SCH3114 and
402 SCH3116 "Super I/O" chipsets.
404 To compile this driver as a module, choose M here: the module will
405 be called gpio-sch311x.
407 config GPIO_SPEAR_SPICS
408 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
409 depends on PLAT_SPEAR
410 select GENERIC_IRQ_CHIP
412 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
415 bool "STA2x11/ConneXt GPIO support"
416 depends on MFD_STA2X11
417 select GENERIC_IRQ_CHIP
419 Say yes here to support the STA2x11/ConneXt GPIO device.
420 The GPIO module has 128 GPIO pins with alternate functions.
423 bool "XWAY STP GPIOs"
426 This enables support for the Serial To Parallel (STP) unit found on
427 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
428 that can be up to 24 bit. This peripheral is aimed at driving leds.
429 Some of the gpios/leds can be auto updated by the soc with dsl and
433 tristate "GPIO based on SYSCON"
434 depends on MFD_SYSCON && OF
436 Say yes here to support GPIO functionality though SYSCON driver.
440 select GENERIC_IRQ_CHIP
444 tristate "TS-5500 DIO blocks and compatibles"
445 depends on TS5500 || COMPILE_TEST
447 This driver supports Digital I/O exposed by pin blocks found on some
448 Technologic Systems platforms. It includes, but is not limited to, 3
449 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
453 bool "Toumaz Xenif TZ1090 GPIO support"
454 depends on SOC_TZ1090
455 select GENERIC_IRQ_CHIP
458 Say yes here to support Toumaz Xenif TZ1090 GPIOs.
460 config GPIO_TZ1090_PDC
461 bool "Toumaz Xenif TZ1090 PDC GPIO support"
462 depends on SOC_TZ1090
465 Say yes here to support Toumaz Xenif TZ1090 PDC GPIOs.
469 depends on ARCH_MXC && SOC_VF610
470 select GPIOLIB_IRQCHIP
472 Say yes here to support Vybrid vf610 GPIOs.
475 tristate "NEC VR4100 series General-purpose I/O Uint support"
476 depends on CPU_VR41XX
478 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
481 tristate "VIA VX855/VX875 GPIO"
486 Support access to the VX855/VX875 GPIO lines through the gpio library.
488 This driver provides common support for accessing the device,
489 additional drivers must be enabled in order to use the
490 functionality of the device.
493 bool "APM X-Gene GPIO controller support"
494 depends on ARM64 && OF_GPIO
496 This driver is to support the GPIO block within the APM X-Gene SoC
497 platform's generic flash controller. The GPIO pins are muxed with
498 the generic flash controller's address and data pins. Say yes
499 here to enable the GFC GPIO functionality.
502 tristate "APM X-Gene GPIO standby controller support"
503 depends on ARCH_XGENE && OF_GPIO
506 This driver supports the GPIO block within the APM X-Gene
507 Standby Domain. Say yes here to enable the GPIO functionality.
510 tristate "Xilinx GPIO support"
511 depends on OF_GPIO && (PPC || MICROBLAZE || ARCH_ZYNQ || X86)
513 Say yes here to support the Xilinx FPGA GPIO device
516 tristate "Netlogic XLP GPIO support"
518 select GPIOLIB_IRQCHIP
520 This driver provides support for GPIO interface on Netlogic XLP MIPS64
521 SoCs. Currently supported XLP variants are XLP8XX, XLP3XX, XLP2XX,
527 bool "Xtensa GPIO32 support"
529 depends on HAVE_XTENSA_GPIO32
532 Say yes here to support the Xtensa internal GPIO32 IMPWIRE (input)
533 and EXPSTATE (output) ports
536 bool "LSI ZEVIO SoC memory mapped GPIOs"
537 depends on ARM && OF_GPIO
539 Say yes here to support the GPIO controller in LSI ZEVIO SoCs.
542 tristate "Xilinx Zynq GPIO support"
543 depends on ARCH_ZYNQ || ARCH_ZYNQMP
544 select GPIOLIB_IRQCHIP
546 Say yes here to support Xilinx Zynq GPIO controller.
550 menu "I2C GPIO expanders"
554 tristate "ADP5588 I2C GPIO expander"
557 This option enables support for 18 GPIOs found
558 on Analog Devices ADP5588 GPIO Expanders.
560 config GPIO_ADP5588_IRQ
561 bool "Interrupt controller support for ADP5588"
562 depends on GPIO_ADP5588=y
564 Say yes here to enable the adp5588 to be used as an interrupt
565 controller. It requires the driver to be built in the kernel.
568 tristate "Avionic Design N-bit GPIO expander"
569 depends on I2C && OF_GPIO
570 select GPIOLIB_IRQCHIP
572 This option enables support for N GPIOs found on Avionic Design
573 I2C GPIO expanders. The register space will be extended by powers
574 of two, so the controller will need to accommodate for that. For
575 example: if a controller provides 48 pins, 6 registers will be
576 enough to represent all pins, but the driver will assume a
577 register layout for 64 pins (8 registers).
580 tristate "Maxim MAX7300 GPIO expander"
584 GPIO driver for Maxim MAX7300 I2C-based GPIO expander.
587 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
590 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
591 Port Expanders. Each IO port on these chips has a fixed role of
592 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
593 Input and Output (designed by 'P'). The combinations are listed
596 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
597 max7322 (4I4O), max7323 (4P4O)
599 16 bits: max7324 (8I8O), max7325 (8P8O),
600 max7326 (4I12O), max7327 (4P12O)
602 Board setup code must specify the model to use, and the start
603 number for these GPIOs.
605 config GPIO_MAX732X_IRQ
606 bool "Interrupt controller support for MAX732x"
607 depends on GPIO_MAX732X=y
608 select GPIOLIB_IRQCHIP
610 Say yes here to enable the max732x to be used as an interrupt
611 controller. It requires the driver to be built in the kernel.
613 config GPIO_MC9S08DZ60
614 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
615 depends on I2C=y && MACH_MX35_3DS
617 Select this to enable the MC9S08DZ60 GPIO driver
620 tristate "PCA95[357]x, PCA9698, TCA64xx, and MAX7310 I/O ports"
623 Say yes here to provide access to several register-oriented
624 SMBus I/O expanders, made mostly by NXP or TI. Compatible
627 4 bits: pca9536, pca9537
629 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
630 pca9556, pca9557, pca9574, tca6408, xra1202
632 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
637 40 bits: pca9505, pca9698
639 config GPIO_PCA953X_IRQ
640 bool "Interrupt controller support for PCA953x"
641 depends on GPIO_PCA953X=y
642 select GPIOLIB_IRQCHIP
644 Say yes here to enable the pca953x to be used as an interrupt
645 controller. It requires the driver to be built in the kernel.
648 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
650 select GPIOLIB_IRQCHIP
653 Say yes here to provide access to most "quasi-bidirectional" I2C
654 GPIO expanders used for additional digital outputs or inputs.
655 Most of these parts are from NXP, though TI is a second source for
656 some of them. Compatible models include:
658 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
659 pca9670, pca9672, pca9674, pca9674a,
662 16 bits: pcf8575, pcf8575c, pca8575,
663 pca9671, pca9673, pca9675
665 Your board setup code will need to declare the expanders in
666 use, and assign numbers to the GPIOs they expose. Those GPIOs
667 can then be used from drivers and other kernel code, just like
668 other GPIOs, but only accessible from task contexts.
670 This driver provides an in-kernel interface to those GPIOs using
671 platform-neutral GPIO calls.
674 bool "Semtech SX150x I2C GPIO expander"
676 select GPIOLIB_IRQCHIP
679 Say yes here to provide support for Semtech SX150-series I2C
680 GPIO expanders. Compatible models include:
687 menu "MFD GPIO expanders"
690 tristate "GPIO Support for ADP5520 PMIC"
691 depends on PMIC_ADP5520
693 This option enables support for on-chip GPIO found
694 on Analog Devices ADP5520 PMICs.
697 tristate "Wolfson Microelectronics Arizona class devices"
698 depends on MFD_ARIZONA
700 Support for GPIOs on Wolfson Arizona class devices.
702 config GPIO_CRYSTAL_COVE
703 tristate "GPIO support for Crystal Cove PMIC"
704 depends on INTEL_SOC_PMIC
705 select GPIOLIB_IRQCHIP
707 Support for GPIO pins on Crystal Cove PMIC.
709 Say Yes if you have a Intel SoC based tablet with Crystal Cove PMIC
712 This driver can also be built as a module. If so, the module will be
713 called gpio-crystalcove.
716 tristate "AMD CS5535/CS5536 GPIO support"
717 depends on MFD_CS5535
719 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
720 can be used for quite a number of things. The CS5535/6 is found on
721 AMD Geode and Lemote Yeeloong devices.
726 tristate "Dialog DA9052 GPIO"
727 depends on PMIC_DA9052
729 Say yes here to enable the GPIO driver for the DA9052 chip.
732 tristate "Dialog Semiconductor DA9055 GPIO"
733 depends on MFD_DA9055
735 Say yes here to enable the GPIO driver for the DA9055 chip.
737 The Dialog DA9055 PMIC chip has 3 GPIO pins that can be
738 be controller by this driver.
740 If driver is built as a module it will be called gpio-da9055.
743 tristate "Diolan DLN2 GPIO support"
745 select GPIOLIB_IRQCHIP
748 Select this option to enable GPIO driver for the Diolan DLN2
751 This driver can also be built as a module. If so, the module
752 will be called gpio-dln2.
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 tristate "Kontron ETX / COMexpress GPIO"
764 depends on MFD_KEMPLD
766 This enables support for the PLD GPIO interface on some Kontron ETX
767 and COMexpress (ETXexpress) modules.
769 This driver can also be built as a module. If so, the module will be
773 tristate "TI/National Semiconductor LP3943 GPIO expander"
774 depends on MFD_LP3943
776 GPIO driver for LP3943 MFD.
777 LP3943 can be used as a GPIO expander which provides up to 16 GPIOs.
778 Open drain outputs are required for this usage.
781 bool "Intel MSIC mixed signal gpio support"
782 depends on MFD_INTEL_MSIC
784 Enable support for GPIO on intel MSIC controllers found in
788 bool "TI PALMAS series PMICs GPIO"
789 depends on MFD_PALMAS
791 Select this option to enable GPIO driver for the TI PALMAS
795 bool "RICOH RC5T583 GPIO"
796 depends on MFD_RC5T583
798 Select this option to enable GPIO driver for the Ricoh RC5T583
800 This driver provides the support for driving/reading the gpio pins
801 of RC5T583 device through standard gpio library.
807 select GPIOLIB_IRQCHIP
809 This enables support for the GPIOs found on the STMPE I/O
814 depends on MFD_TC3589X
816 select GPIOLIB_IRQCHIP
818 This enables support for the GPIOs found on the TC3589X
821 config GPIO_TIMBERDALE
822 bool "Support for timberdale GPIO IP"
823 depends on MFD_TIMBERDALE
825 Add support for the GPIO IP in the timberdale FPGA.
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 tristate "TI TPS65912 GPIO"
843 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
845 This driver supports TPS65912 gpio chip
848 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
849 depends on TWL4030_CORE
851 Say yes here to access the GPIO signals of various multi-function
852 power management chips from Texas Instruments.
855 tristate "TWL6040 GPO"
856 depends on TWL6040_CORE
858 Say yes here to access the GPO signals of twl6040
859 audio chip from Texas Instruments.
862 tristate "Philips UCB1400 GPIO"
863 depends on UCB1400_CORE
865 This enables support for the Philips UCB1400 GPIO pins.
866 The UCB1400 is an AC97 audio codec.
869 tristate "WM831x GPIOs"
870 depends on MFD_WM831X
872 Say yes here to access the GPIO signals of WM831x power management
873 chips from Wolfson Microelectronics.
876 tristate "WM8350 GPIOs"
877 depends on MFD_WM8350
879 Say yes here to access the GPIO signals of WM8350 power management
880 chips from Wolfson Microelectronics.
883 tristate "WM8994 GPIOs"
884 depends on MFD_WM8994
886 Say yes here to access the GPIO signals of WM8994 audio hub
887 CODECs from Wolfson Microelectronics.
891 menu "PCI GPIO expanders"
895 tristate "AMD 8111 GPIO driver"
898 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
900 Note, that usually system firmware/ACPI handles GPIO pins on their
901 own and users might easily break their systems with uncarefull usage
907 tristate "BT8XX GPIO abuser"
908 depends on PCI && VIDEO_BT848=n
910 The BT8xx frame grabber chip has 24 GPIO pins that can be abused
911 as a cheap PCI GPIO card.
913 This chip can be found on Miro, Hauppauge and STB TV-cards.
915 The card needs to be physically altered for using it as a
916 GPIO card. For more information on how to build a GPIO card
917 from a BT8xx TV card, see the documentation file at
918 Documentation/bt8xxgpio.txt
922 config GPIO_INTEL_MID
923 bool "Intel Mid GPIO support"
924 depends on PCI && X86
925 select GPIOLIB_IRQCHIP
927 Say Y here to support Intel Mid GPIO.
930 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
932 select GENERIC_IRQ_CHIP
934 ML7213 is companion chip for Intel Atom E6xx series.
935 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
936 Hub) which is for IVI(In-Vehicle Infotainment) use.
937 This driver can access the IOH's GPIO device.
940 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
941 depends on PCI && (X86_32 || COMPILE_TEST)
942 select GENERIC_IRQ_CHIP
944 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
945 which is an IOH(Input/Output Hub) for x86 embedded processor.
946 This driver can access PCH GPIO device.
948 This driver also can be used for LAPIS Semiconductor IOH(Input/
949 Output Hub), ML7223 and ML7831.
950 ML7223 IOH is for MP(Media Phone) use.
951 ML7831 IOH is for general purpose use.
952 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
953 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
956 tristate "RDC R-321x GPIO support"
961 Support for the RDC R321x SoC GPIOs over southbridge
962 PCI configuration space.
964 config GPIO_SODAVILLE
965 bool "Intel Sodaville GPIO support"
966 depends on X86 && PCI && OF
968 select GENERIC_IRQ_CHIP
970 Say Y here to support Intel Sodaville GPIO.
974 menu "SPI GPIO expanders"
975 depends on SPI_MASTER
978 tristate "74x164 serial-in/parallel-out 8-bits shift register"
979 depends on SPI_MASTER && OF
981 Driver for 74x164 compatible serial-in/parallel-out 8-outputs
982 shift registers. This driver can be used to provide access
983 to more gpio outputs.
986 tristate "Maxim MAX7301 GPIO expander"
987 depends on SPI_MASTER
990 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
993 tristate "Microchip MCP23xxx I/O expander"
994 depends on (SPI_MASTER && !I2C) || I2C
996 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
998 This provides a GPIO interface supporting inputs and outputs.
999 The I2C versions of the chips can be used as interrupt-controller.
1002 tristate "Freescale MC33880 high-side/low-side switch"
1003 depends on SPI_MASTER
1005 SPI driver for Freescale MC33880 high-side/low-side switch.
1006 This provides GPIO interface supporting inputs and outputs.
1010 menu "USB GPIO expanders"
1013 config GPIO_VIPERBOARD
1014 tristate "Viperboard GPIO a & b support"
1015 depends on MFD_VIPERBOARD && USB
1017 Say yes here to access the GPIO signals of Nano River
1018 Technologies Viperboard. There are two GPIO chips on the
1019 board: gpioa and gpiob.
1020 See viperboard API specification and Nano
1021 River Tech's viperboard.h for detailed meaning
1022 of the module parameters.