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 bool "Broadcom Kona GPIO"
124 depends on OF_GPIO && (ARCH_BCM_MOBILE || COMPILE_TEST)
126 Turn on GPIO support for Broadcom "Kona" chips.
129 tristate "BRCMSTB GPIO support"
130 default y if ARCH_BRCMSTB
131 depends on OF_GPIO && (ARCH_BRCMSTB || COMPILE_TEST)
134 Say yes here to enable GPIO support for Broadcom STB (BCM7XXX) SoCs.
137 tristate "CLPS711X GPIO support"
138 depends on ARCH_CLPS711X || COMPILE_TEST
141 Say yes here to support GPIO on CLPS711X SoCs.
144 bool "TI Davinci/Keystone GPIO support"
145 default y if ARCH_DAVINCI
146 depends on ARM && (ARCH_DAVINCI || ARCH_KEYSTONE)
148 Say yes here to enable GPIO support for TI Davinci/Keystone SoCs.
151 tristate "Synopsys DesignWare APB GPIO driver"
153 select GENERIC_IRQ_CHIP
155 Say Y or M here to build support for the Synopsys DesignWare APB
159 tristate "Emma Mobile GPIO"
160 depends on ARM && OF_GPIO
162 Say yes here to support GPIO on Renesas Emma Mobile SoCs.
166 depends on ARCH_EP93XX
170 bool "Axis ETRAX FS General I/O"
171 depends on CRIS || COMPILE_TEST
175 Say yes here to support the GPIO controller on Axis ETRAX FS SoCs.
178 tristate "F71869, F71869A, F71882FG and F71889F GPIO support"
181 This option enables support for GPIOs found on Fintek Super-I/O
182 chips F71869, F71869A, F71882FG and F71889F.
184 To compile this driver as a module, choose M here: the module will
185 be called f7188x-gpio.
188 bool "GE FPGA based GPIO"
192 Support for common GPIO functionality provided on some GE Single Board
195 This driver provides basic support (configure as input or output, read
196 and write pin state) for GPIO implemented in a number of GE single
199 config GPIO_GENERIC_PLATFORM
200 tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
203 Say yes here to support basic platform_device memory-mapped GPIO controllers.
206 tristate "Aeroflex Gaisler GRGPIO support"
211 Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
212 VHDL IP core library.
215 tristate "Intel ICH GPIO"
216 depends on PCI && X86
220 Say yes here to support the GPIO functionality of a number of Intel
221 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
222 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
223 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
228 tristate "Intel IOP GPIO"
229 depends on ARM && (ARCH_IOP32X || ARCH_IOP33X)
231 Say yes here to support the GPIO functionality of a number of Intel
237 tristate "IT8761E GPIO support"
238 depends on X86 # unconditional access to IO space.
240 Say yes here to support GPIO functionality of IT8761E super I/O chip.
243 bool "Loongson-2/3 GPIO support"
244 depends on CPU_LOONGSON2 || CPU_LOONGSON3
246 driver for GPIO functionality on Loongson-2F/3A/3B processors.
249 bool "NXP LPC18XX/43XX GPIO support"
250 default y if ARCH_LPC18XX
251 depends on OF_GPIO && (ARCH_LPC18XX || COMPILE_TEST)
253 Select this option to enable GPIO driver for
254 NXP LPC18XX/43XX devices.
256 config GPIO_LYNXPOINT
257 tristate "Intel Lynxpoint GPIO support"
258 depends on ACPI && X86
259 select GPIOLIB_IRQCHIP
261 driver for GPIO functionality on Intel Lynxpoint PCH chipset
262 Requires ACPI device enumeration code to set up a platform device.
265 bool "GPIO support for Fujitsu MB86S7x Platforms"
266 depends on ARCH_MB86S7X
268 Say yes here to support the GPIO controller in Fujitsu MB86S70 SoCs.
270 config GPIO_MM_LANTIQ
271 bool "Lantiq Memory mapped GPIOs"
272 depends on LANTIQ && SOC_XWAY
274 This enables support for memory mapped GPIOs on the External Bus Unit
275 (EBU) found on Lantiq SoCs. The gpios are output only as they are
276 created by attaching a 16bit latch to the bus.
279 bool "MOXART GPIO support"
280 depends on ARCH_MOXART
283 Select this option to enable GPIO driver for
284 MOXA ART SoC devices.
288 depends on PPC_MPC52xx
291 bool "MPC512x/MPC8xxx GPIO support"
292 depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \
293 FSL_SOC_BOOKE || PPC_86xx
295 Say Y here if you're going to use hardware that connects to the
296 MPC512x/831x/834x/837x/8572/8610 GPIOs.
299 tristate "Qualcomm MSM GPIO v2"
300 depends on GPIOLIB && OF && ARCH_QCOM
302 Say yes here to support the GPIO interface on ARM v7 based
303 Qualcomm MSM chips. Most of the pins on the MSM can be
304 selected for GPIO, and are controlled by this driver.
308 depends on PLAT_ORION
310 select GENERIC_IRQ_CHIP
316 select GENERIC_IRQ_CHIP
322 select GENERIC_IRQ_CHIP
325 tristate "Cavium OCTEON GPIO"
326 depends on GPIOLIB && CAVIUM_OCTEON_SOC
329 Say yes here to support the on-chip GPIO lines on the OCTEON
333 tristate "TI OMAP GPIO support" if ARCH_OMAP2PLUS || COMPILE_TEST
334 default y if ARCH_OMAP
336 select GENERIC_IRQ_CHIP
337 select GPIOLIB_IRQCHIP
339 Say yes here to enable GPIO support for TI OMAP SoCs.
342 bool "PrimeCell PL061 GPIO support"
345 select GPIOLIB_IRQCHIP
347 Say yes here to support the PrimeCell PL061 GPIO device
350 bool "PXA GPIO support"
351 depends on ARCH_PXA || ARCH_MMP
353 Say yes here to support the PXA GPIO device
356 tristate "Renesas R-Car GPIO"
357 depends on ARM && (ARCH_SHMOBILE || COMPILE_TEST)
358 select GPIOLIB_IRQCHIP
360 Say yes here to support GPIO on Renesas R-Car SoCs.
364 depends on PLAT_SAMSUNG
366 Legacy GPIO support. Use only for platforms without support for
370 tristate "Intel SCH/TunnelCreek/Centerton/Quark X1000 GPIO"
371 depends on PCI && X86
375 Say yes here to support GPIO interface on Intel Poulsbo SCH,
376 Intel Tunnel Creek processor, Intel Centerton processor or
377 Intel Quark X1000 SoC.
379 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
380 powered by the core power rail and are turned off during sleep
381 modes (S3 and higher). The remaining four GPIOs are powered by
382 the Intel SCH suspend power supply. These GPIOs remain
383 active during S3. The suspend powered GPIOs can be used to wake the
384 system from the Suspend-to-RAM state.
386 The Intel Tunnel Creek processor has 5 GPIOs powered by the
387 core power rail and 9 from suspend power supply.
389 The Intel Centerton processor has a total of 30 GPIO pins.
390 Twenty-one are powered by the core power rail and 9 from the
391 suspend power supply.
393 The Intel Quark X1000 SoC has 2 GPIOs powered by the core
394 power well and 6 from the suspend power well.
397 tristate "SMSC SCH311x SuperI/O GPIO"
399 Driver to enable the GPIOs found on SMSC SMSC SCH3112, SCH3114 and
400 SCH3116 "Super I/O" chipsets.
402 To compile this driver as a module, choose M here: the module will
403 be called gpio-sch311x.
405 config GPIO_SPEAR_SPICS
406 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
407 depends on PLAT_SPEAR
408 select GENERIC_IRQ_CHIP
410 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
413 bool "STA2x11/ConneXt GPIO support"
414 depends on MFD_STA2X11
415 select GENERIC_IRQ_CHIP
417 Say yes here to support the STA2x11/ConneXt GPIO device.
418 The GPIO module has 128 GPIO pins with alternate functions.
421 bool "XWAY STP GPIOs"
424 This enables support for the Serial To Parallel (STP) unit found on
425 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
426 that can be up to 24 bit. This peripheral is aimed at driving leds.
427 Some of the gpios/leds can be auto updated by the soc with dsl and
431 tristate "GPIO based on SYSCON"
432 depends on MFD_SYSCON && OF
434 Say yes here to support GPIO functionality though SYSCON driver.
438 select GENERIC_IRQ_CHIP
442 tristate "TS-5500 DIO blocks and compatibles"
443 depends on TS5500 || COMPILE_TEST
445 This driver supports Digital I/O exposed by pin blocks found on some
446 Technologic Systems platforms. It includes, but is not limited to, 3
447 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
451 bool "Toumaz Xenif TZ1090 GPIO support"
452 depends on SOC_TZ1090
453 select GENERIC_IRQ_CHIP
456 Say yes here to support Toumaz Xenif TZ1090 GPIOs.
458 config GPIO_TZ1090_PDC
459 bool "Toumaz Xenif TZ1090 PDC GPIO support"
460 depends on SOC_TZ1090
463 Say yes here to support Toumaz Xenif TZ1090 PDC GPIOs.
467 depends on ARCH_MXC && SOC_VF610
468 select GPIOLIB_IRQCHIP
470 Say yes here to support Vybrid vf610 GPIOs.
473 tristate "NEC VR4100 series General-purpose I/O Uint support"
474 depends on CPU_VR41XX
476 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
479 tristate "VIA VX855/VX875 GPIO"
484 Support access to the VX855/VX875 GPIO lines through the gpio library.
486 This driver provides common support for accessing the device,
487 additional drivers must be enabled in order to use the
488 functionality of the device.
491 bool "APM X-Gene GPIO controller support"
492 depends on ARM64 && OF_GPIO
494 This driver is to support the GPIO block within the APM X-Gene SoC
495 platform's generic flash controller. The GPIO pins are muxed with
496 the generic flash controller's address and data pins. Say yes
497 here to enable the GFC GPIO functionality.
500 tristate "APM X-Gene GPIO standby controller support"
501 depends on ARCH_XGENE && OF_GPIO
504 This driver supports the GPIO block within the APM X-Gene
505 Standby Domain. Say yes here to enable the GPIO functionality.
508 tristate "Xilinx GPIO support"
509 depends on OF_GPIO && (PPC || MICROBLAZE || ARCH_ZYNQ || X86)
511 Say yes here to support the Xilinx FPGA GPIO device
514 tristate "Netlogic XLP GPIO support"
516 select GPIOLIB_IRQCHIP
518 This driver provides support for GPIO interface on Netlogic XLP MIPS64
519 SoCs. Currently supported XLP variants are XLP8XX, XLP3XX, XLP2XX,
525 bool "Xtensa GPIO32 support"
527 depends on HAVE_XTENSA_GPIO32
530 Say yes here to support the Xtensa internal GPIO32 IMPWIRE (input)
531 and EXPSTATE (output) ports
534 bool "LSI ZEVIO SoC memory mapped GPIOs"
535 depends on ARM && OF_GPIO
537 Say yes here to support the GPIO controller in LSI ZEVIO SoCs.
540 tristate "Xilinx Zynq GPIO support"
541 depends on ARCH_ZYNQ || ARCH_ZYNQMP
542 select GPIOLIB_IRQCHIP
544 Say yes here to support Xilinx Zynq GPIO controller.
548 menu "I2C GPIO expanders"
552 tristate "ADP5588 I2C GPIO expander"
555 This option enables support for 18 GPIOs found
556 on Analog Devices ADP5588 GPIO Expanders.
558 config GPIO_ADP5588_IRQ
559 bool "Interrupt controller support for ADP5588"
560 depends on GPIO_ADP5588=y
562 Say yes here to enable the adp5588 to be used as an interrupt
563 controller. It requires the driver to be built in the kernel.
566 tristate "Avionic Design N-bit GPIO expander"
567 depends on I2C && OF_GPIO
568 select GPIOLIB_IRQCHIP
570 This option enables support for N GPIOs found on Avionic Design
571 I2C GPIO expanders. The register space will be extended by powers
572 of two, so the controller will need to accommodate for that. For
573 example: if a controller provides 48 pins, 6 registers will be
574 enough to represent all pins, but the driver will assume a
575 register layout for 64 pins (8 registers).
578 tristate "Maxim MAX7300 GPIO expander"
582 GPIO driver for Maxim MAX7300 I2C-based GPIO expander.
585 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
588 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
589 Port Expanders. Each IO port on these chips has a fixed role of
590 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
591 Input and Output (designed by 'P'). The combinations are listed
594 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
595 max7322 (4I4O), max7323 (4P4O)
597 16 bits: max7324 (8I8O), max7325 (8P8O),
598 max7326 (4I12O), max7327 (4P12O)
600 Board setup code must specify the model to use, and the start
601 number for these GPIOs.
603 config GPIO_MAX732X_IRQ
604 bool "Interrupt controller support for MAX732x"
605 depends on GPIO_MAX732X=y
606 select GPIOLIB_IRQCHIP
608 Say yes here to enable the max732x to be used as an interrupt
609 controller. It requires the driver to be built in the kernel.
611 config GPIO_MC9S08DZ60
612 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
613 depends on I2C=y && MACH_MX35_3DS
615 Select this to enable the MC9S08DZ60 GPIO driver
618 tristate "PCA95[357]x, PCA9698, TCA64xx, and MAX7310 I/O ports"
621 Say yes here to provide access to several register-oriented
622 SMBus I/O expanders, made mostly by NXP or TI. Compatible
625 4 bits: pca9536, pca9537
627 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
628 pca9556, pca9557, pca9574, tca6408, xra1202
630 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
635 40 bits: pca9505, pca9698
637 config GPIO_PCA953X_IRQ
638 bool "Interrupt controller support for PCA953x"
639 depends on GPIO_PCA953X=y
640 select GPIOLIB_IRQCHIP
642 Say yes here to enable the pca953x to be used as an interrupt
643 controller. It requires the driver to be built in the kernel.
646 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
648 select GPIOLIB_IRQCHIP
651 Say yes here to provide access to most "quasi-bidirectional" I2C
652 GPIO expanders used for additional digital outputs or inputs.
653 Most of these parts are from NXP, though TI is a second source for
654 some of them. Compatible models include:
656 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
657 pca9670, pca9672, pca9674, pca9674a,
660 16 bits: pcf8575, pcf8575c, pca8575,
661 pca9671, pca9673, pca9675
663 Your board setup code will need to declare the expanders in
664 use, and assign numbers to the GPIOs they expose. Those GPIOs
665 can then be used from drivers and other kernel code, just like
666 other GPIOs, but only accessible from task contexts.
668 This driver provides an in-kernel interface to those GPIOs using
669 platform-neutral GPIO calls.
672 bool "Semtech SX150x I2C GPIO expander"
674 select GPIOLIB_IRQCHIP
677 Say yes here to provide support for Semtech SX150-series I2C
678 GPIO expanders. Compatible models include:
685 menu "MFD GPIO expanders"
688 tristate "GPIO Support for ADP5520 PMIC"
689 depends on PMIC_ADP5520
691 This option enables support for on-chip GPIO found
692 on Analog Devices ADP5520 PMICs.
695 tristate "Wolfson Microelectronics Arizona class devices"
696 depends on MFD_ARIZONA
698 Support for GPIOs on Wolfson Arizona class devices.
700 config GPIO_CRYSTAL_COVE
701 tristate "GPIO support for Crystal Cove PMIC"
702 depends on INTEL_SOC_PMIC
703 select GPIOLIB_IRQCHIP
705 Support for GPIO pins on Crystal Cove PMIC.
707 Say Yes if you have a Intel SoC based tablet with Crystal Cove PMIC
710 This driver can also be built as a module. If so, the module will be
711 called gpio-crystalcove.
714 tristate "AMD CS5535/CS5536 GPIO support"
715 depends on MFD_CS5535
717 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
718 can be used for quite a number of things. The CS5535/6 is found on
719 AMD Geode and Lemote Yeeloong devices.
724 tristate "Dialog DA9052 GPIO"
725 depends on PMIC_DA9052
727 Say yes here to enable the GPIO driver for the DA9052 chip.
730 tristate "Dialog Semiconductor DA9055 GPIO"
731 depends on MFD_DA9055
733 Say yes here to enable the GPIO driver for the DA9055 chip.
735 The Dialog DA9055 PMIC chip has 3 GPIO pins that can be
736 be controller by this driver.
738 If driver is built as a module it will be called gpio-da9055.
741 tristate "Diolan DLN2 GPIO support"
743 select GPIOLIB_IRQCHIP
746 Select this option to enable GPIO driver for the Diolan DLN2
749 This driver can also be built as a module. If so, the module
750 will be called gpio-dln2.
753 tristate "Janz VMOD-TTL Digital IO Module"
754 depends on MFD_JANZ_CMODIO
756 This enables support for the Janz VMOD-TTL Digital IO module.
757 This driver provides support for driving the pins in output
758 mode only. Input mode is not supported.
761 tristate "Kontron ETX / COMexpress GPIO"
762 depends on MFD_KEMPLD
764 This enables support for the PLD GPIO interface on some Kontron ETX
765 and COMexpress (ETXexpress) modules.
767 This driver can also be built as a module. If so, the module will be
771 tristate "TI/National Semiconductor LP3943 GPIO expander"
772 depends on MFD_LP3943
774 GPIO driver for LP3943 MFD.
775 LP3943 can be used as a GPIO expander which provides up to 16 GPIOs.
776 Open drain outputs are required for this usage.
779 bool "Intel MSIC mixed signal gpio support"
780 depends on MFD_INTEL_MSIC
782 Enable support for GPIO on intel MSIC controllers found in
786 bool "TI PALMAS series PMICs GPIO"
787 depends on MFD_PALMAS
789 Select this option to enable GPIO driver for the TI PALMAS
793 bool "RICOH RC5T583 GPIO"
794 depends on MFD_RC5T583
796 Select this option to enable GPIO driver for the Ricoh RC5T583
798 This driver provides the support for driving/reading the gpio pins
799 of RC5T583 device through standard gpio library.
805 select GPIOLIB_IRQCHIP
807 This enables support for the GPIOs found on the STMPE I/O
812 depends on MFD_TC3589X
814 select GPIOLIB_IRQCHIP
816 This enables support for the GPIOs found on the TC3589X
819 config GPIO_TIMBERDALE
820 bool "Support for timberdale GPIO IP"
821 depends on MFD_TIMBERDALE
823 Add support for the GPIO IP in the timberdale FPGA.
827 depends on MFD_TPS6586X
829 Select this option to enable GPIO driver for the TPS6586X
834 depends on MFD_TPS65910
836 Select this option to enable GPIO driver for the TPS65910
840 tristate "TI TPS65912 GPIO"
841 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
843 This driver supports TPS65912 gpio chip
846 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
847 depends on TWL4030_CORE
849 Say yes here to access the GPIO signals of various multi-function
850 power management chips from Texas Instruments.
853 tristate "TWL6040 GPO"
854 depends on TWL6040_CORE
856 Say yes here to access the GPO signals of twl6040
857 audio chip from Texas Instruments.
860 tristate "Philips UCB1400 GPIO"
861 depends on UCB1400_CORE
863 This enables support for the Philips UCB1400 GPIO pins.
864 The UCB1400 is an AC97 audio codec.
867 tristate "WM831x GPIOs"
868 depends on MFD_WM831X
870 Say yes here to access the GPIO signals of WM831x power management
871 chips from Wolfson Microelectronics.
874 tristate "WM8350 GPIOs"
875 depends on MFD_WM8350
877 Say yes here to access the GPIO signals of WM8350 power management
878 chips from Wolfson Microelectronics.
881 tristate "WM8994 GPIOs"
882 depends on MFD_WM8994
884 Say yes here to access the GPIO signals of WM8994 audio hub
885 CODECs from Wolfson Microelectronics.
889 menu "PCI GPIO expanders"
893 tristate "AMD 8111 GPIO driver"
896 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
898 Note, that usually system firmware/ACPI handles GPIO pins on their
899 own and users might easily break their systems with uncarefull usage
905 tristate "BT8XX GPIO abuser"
906 depends on PCI && VIDEO_BT848=n
908 The BT8xx frame grabber chip has 24 GPIO pins that can be abused
909 as a cheap PCI GPIO card.
911 This chip can be found on Miro, Hauppauge and STB TV-cards.
913 The card needs to be physically altered for using it as a
914 GPIO card. For more information on how to build a GPIO card
915 from a BT8xx TV card, see the documentation file at
916 Documentation/bt8xxgpio.txt
920 config GPIO_INTEL_MID
921 bool "Intel Mid GPIO support"
922 depends on PCI && X86
923 select GPIOLIB_IRQCHIP
925 Say Y here to support Intel Mid GPIO.
928 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
930 select GENERIC_IRQ_CHIP
932 ML7213 is companion chip for Intel Atom E6xx series.
933 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
934 Hub) which is for IVI(In-Vehicle Infotainment) use.
935 This driver can access the IOH's GPIO device.
938 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
939 depends on PCI && (X86_32 || COMPILE_TEST)
940 select GENERIC_IRQ_CHIP
942 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
943 which is an IOH(Input/Output Hub) for x86 embedded processor.
944 This driver can access PCH GPIO device.
946 This driver also can be used for LAPIS Semiconductor IOH(Input/
947 Output Hub), ML7223 and ML7831.
948 ML7223 IOH is for MP(Media Phone) use.
949 ML7831 IOH is for general purpose use.
950 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
951 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
954 tristate "RDC R-321x GPIO support"
959 Support for the RDC R321x SoC GPIOs over southbridge
960 PCI configuration space.
962 config GPIO_SODAVILLE
963 bool "Intel Sodaville GPIO support"
964 depends on X86 && PCI && OF
966 select GENERIC_IRQ_CHIP
968 Say Y here to support Intel Sodaville GPIO.
972 menu "SPI GPIO expanders"
973 depends on SPI_MASTER
976 tristate "74x164 serial-in/parallel-out 8-bits shift register"
977 depends on SPI_MASTER && OF
979 Driver for 74x164 compatible serial-in/parallel-out 8-outputs
980 shift registers. This driver can be used to provide access
981 to more gpio outputs.
984 tristate "Maxim MAX7301 GPIO expander"
985 depends on SPI_MASTER
988 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
991 tristate "Microchip MCP23xxx I/O expander"
992 depends on (SPI_MASTER && !I2C) || I2C
994 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
996 This provides a GPIO interface supporting inputs and outputs.
997 The I2C versions of the chips can be used as interrupt-controller.
1000 tristate "Freescale MC33880 high-side/low-side switch"
1001 depends on SPI_MASTER
1003 SPI driver for Freescale MC33880 high-side/low-side switch.
1004 This provides GPIO interface supporting inputs and outputs.
1007 bool "ZTE ZX GPIO support"
1008 select GPIOLIB_IRQCHIP
1010 Say yes here to support the GPIO device on ZTE ZX SoCs.
1014 menu "USB GPIO expanders"
1017 config GPIO_VIPERBOARD
1018 tristate "Viperboard GPIO a & b support"
1019 depends on MFD_VIPERBOARD && USB
1021 Say yes here to access the GPIO signals of Nano River
1022 Technologies Viperboard. There are two GPIO chips on the
1023 board: gpioa and gpiob.
1024 See viperboard API specification and Nano
1025 River Tech's viperboard.h for detailed meaning
1026 of the module parameters.