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 tristate "F71869, F71869A, F71882FG and F71889F GPIO support"
174 This option enables support for GPIOs found on Fintek Super-I/O
175 chips F71869, F71869A, F71882FG and F71889F.
177 To compile this driver as a module, choose M here: the module will
178 be called f7188x-gpio.
181 bool "GE FPGA based GPIO"
185 Support for common GPIO functionality provided on some GE Single Board
188 This driver provides basic support (configure as input or output, read
189 and write pin state) for GPIO implemented in a number of GE single
192 config GPIO_GENERIC_PLATFORM
193 tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
196 Say yes here to support basic platform_device memory-mapped GPIO controllers.
199 tristate "Aeroflex Gaisler GRGPIO support"
204 Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
205 VHDL IP core library.
208 tristate "Intel ICH GPIO"
209 depends on PCI && X86
213 Say yes here to support the GPIO functionality of a number of Intel
214 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
215 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
216 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
221 tristate "Intel IOP GPIO"
222 depends on ARM && (ARCH_IOP32X || ARCH_IOP33X)
224 Say yes here to support the GPIO functionality of a number of Intel
230 tristate "IT8761E GPIO support"
231 depends on X86 # unconditional access to IO space.
233 Say yes here to support GPIO functionality of IT8761E super I/O chip.
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.
292 tristate "Qualcomm MSM GPIO v2"
293 depends on GPIOLIB && OF && ARCH_QCOM
295 Say yes here to support the GPIO interface on ARM v7 based
296 Qualcomm MSM chips. Most of the pins on the MSM can be
297 selected for GPIO, and are controlled by this driver.
301 depends on PLAT_ORION
304 select GENERIC_IRQ_CHIP
310 select GENERIC_IRQ_CHIP
316 select GENERIC_IRQ_CHIP
319 tristate "Cavium OCTEON GPIO"
320 depends on GPIOLIB && CAVIUM_OCTEON_SOC
323 Say yes here to support the on-chip GPIO lines on the OCTEON
327 tristate "TI OMAP GPIO support" if ARCH_OMAP2PLUS || COMPILE_TEST
328 default y if ARCH_OMAP
330 select GENERIC_IRQ_CHIP
331 select GPIOLIB_IRQCHIP
333 Say yes here to enable GPIO support for TI OMAP SoCs.
336 bool "PrimeCell PL061 GPIO support"
339 select GPIOLIB_IRQCHIP
341 Say yes here to support the PrimeCell PL061 GPIO device
344 bool "PXA GPIO support"
345 depends on ARCH_PXA || ARCH_MMP
347 Say yes here to support the PXA GPIO device
350 tristate "Renesas R-Car GPIO"
351 depends on ARM && (ARCH_SHMOBILE || COMPILE_TEST)
352 select GPIOLIB_IRQCHIP
354 Say yes here to support GPIO on Renesas R-Car SoCs.
358 depends on PLAT_SAMSUNG
360 Legacy GPIO support. Use only for platforms without support for
364 tristate "Intel SCH/TunnelCreek/Centerton/Quark X1000 GPIO"
365 depends on PCI && X86
369 Say yes here to support GPIO interface on Intel Poulsbo SCH,
370 Intel Tunnel Creek processor, Intel Centerton processor or
371 Intel Quark X1000 SoC.
373 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
374 powered by the core power rail and are turned off during sleep
375 modes (S3 and higher). The remaining four GPIOs are powered by
376 the Intel SCH suspend power supply. These GPIOs remain
377 active during S3. The suspend powered GPIOs can be used to wake the
378 system from the Suspend-to-RAM state.
380 The Intel Tunnel Creek processor has 5 GPIOs powered by the
381 core power rail and 9 from suspend power supply.
383 The Intel Centerton processor has a total of 30 GPIO pins.
384 Twenty-one are powered by the core power rail and 9 from the
385 suspend power supply.
387 The Intel Quark X1000 SoC has 2 GPIOs powered by the core
388 power well and 6 from the suspend power well.
391 tristate "SMSC SCH311x SuperI/O GPIO"
393 Driver to enable the GPIOs found on SMSC SMSC SCH3112, SCH3114 and
394 SCH3116 "Super I/O" chipsets.
396 To compile this driver as a module, choose M here: the module will
397 be called gpio-sch311x.
399 config GPIO_SPEAR_SPICS
400 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
401 depends on PLAT_SPEAR
402 select GENERIC_IRQ_CHIP
404 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
407 bool "STA2x11/ConneXt GPIO support"
408 depends on MFD_STA2X11
409 select GENERIC_IRQ_CHIP
411 Say yes here to support the STA2x11/ConneXt GPIO device.
412 The GPIO module has 128 GPIO pins with alternate functions.
415 bool "XWAY STP GPIOs"
418 This enables support for the Serial To Parallel (STP) unit found on
419 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
420 that can be up to 24 bit. This peripheral is aimed at driving leds.
421 Some of the gpios/leds can be auto updated by the soc with dsl and
425 tristate "GPIO based on SYSCON"
426 depends on MFD_SYSCON && OF
428 Say yes here to support GPIO functionality though SYSCON driver.
432 select GENERIC_IRQ_CHIP
436 tristate "TS-5500 DIO blocks and compatibles"
437 depends on TS5500 || COMPILE_TEST
439 This driver supports Digital I/O exposed by pin blocks found on some
440 Technologic Systems platforms. It includes, but is not limited to, 3
441 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
445 bool "Toumaz Xenif TZ1090 GPIO support"
446 depends on SOC_TZ1090
447 select GENERIC_IRQ_CHIP
450 Say yes here to support Toumaz Xenif TZ1090 GPIOs.
452 config GPIO_TZ1090_PDC
453 bool "Toumaz Xenif TZ1090 PDC GPIO support"
454 depends on SOC_TZ1090
457 Say yes here to support Toumaz Xenif TZ1090 PDC GPIOs.
461 depends on ARCH_MXC && SOC_VF610
462 select GPIOLIB_IRQCHIP
464 Say yes here to support Vybrid vf610 GPIOs.
467 tristate "NEC VR4100 series General-purpose I/O Uint support"
468 depends on CPU_VR41XX
470 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
473 tristate "VIA VX855/VX875 GPIO"
478 Support access to the VX855/VX875 GPIO lines through the gpio library.
480 This driver provides common support for accessing the device,
481 additional drivers must be enabled in order to use the
482 functionality of the device.
485 bool "APM X-Gene GPIO controller support"
486 depends on ARM64 && OF_GPIO
488 This driver is to support the GPIO block within the APM X-Gene SoC
489 platform's generic flash controller. The GPIO pins are muxed with
490 the generic flash controller's address and data pins. Say yes
491 here to enable the GFC GPIO functionality.
494 tristate "APM X-Gene GPIO standby controller support"
495 depends on ARCH_XGENE && OF_GPIO
498 This driver supports the GPIO block within the APM X-Gene
499 Standby Domain. Say yes here to enable the GPIO functionality.
502 tristate "Xilinx GPIO support"
503 depends on OF_GPIO && (PPC || MICROBLAZE || ARCH_ZYNQ || X86)
505 Say yes here to support the Xilinx FPGA GPIO device
508 tristate "Netlogic XLP GPIO support"
510 select GPIOLIB_IRQCHIP
512 This driver provides support for GPIO interface on Netlogic XLP MIPS64
513 SoCs. Currently supported XLP variants are XLP8XX, XLP3XX, XLP2XX,
519 bool "Xtensa GPIO32 support"
521 depends on HAVE_XTENSA_GPIO32
524 Say yes here to support the Xtensa internal GPIO32 IMPWIRE (input)
525 and EXPSTATE (output) ports
528 bool "LSI ZEVIO SoC memory mapped GPIOs"
529 depends on ARM && OF_GPIO
531 Say yes here to support the GPIO controller in LSI ZEVIO SoCs.
534 tristate "Xilinx Zynq GPIO support"
536 select GPIOLIB_IRQCHIP
538 Say yes here to support Xilinx Zynq GPIO controller.
542 menu "I2C GPIO expanders"
546 tristate "ADP5588 I2C GPIO expander"
549 This option enables support for 18 GPIOs found
550 on Analog Devices ADP5588 GPIO Expanders.
552 config GPIO_ADP5588_IRQ
553 bool "Interrupt controller support for ADP5588"
554 depends on GPIO_ADP5588=y
556 Say yes here to enable the adp5588 to be used as an interrupt
557 controller. It requires the driver to be built in the kernel.
560 tristate "Avionic Design N-bit GPIO expander"
561 depends on I2C && OF_GPIO
562 select GPIOLIB_IRQCHIP
564 This option enables support for N GPIOs found on Avionic Design
565 I2C GPIO expanders. The register space will be extended by powers
566 of two, so the controller will need to accommodate for that. For
567 example: if a controller provides 48 pins, 6 registers will be
568 enough to represent all pins, but the driver will assume a
569 register layout for 64 pins (8 registers).
572 tristate "Maxim MAX7300 GPIO expander"
576 GPIO driver for Maxim MAX7300 I2C-based GPIO expander.
579 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
582 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
583 Port Expanders. Each IO port on these chips has a fixed role of
584 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
585 Input and Output (designed by 'P'). The combinations are listed
588 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
589 max7322 (4I4O), max7323 (4P4O)
591 16 bits: max7324 (8I8O), max7325 (8P8O),
592 max7326 (4I12O), max7327 (4P12O)
594 Board setup code must specify the model to use, and the start
595 number for these GPIOs.
597 config GPIO_MAX732X_IRQ
598 bool "Interrupt controller support for MAX732x"
599 depends on GPIO_MAX732X=y
600 select GPIOLIB_IRQCHIP
602 Say yes here to enable the max732x to be used as an interrupt
603 controller. It requires the driver to be built in the kernel.
605 config GPIO_MC9S08DZ60
606 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
607 depends on I2C=y && MACH_MX35_3DS
609 Select this to enable the MC9S08DZ60 GPIO driver
612 tristate "PCA95[357]x, PCA9698, TCA64xx, and MAX7310 I/O ports"
615 Say yes here to provide access to several register-oriented
616 SMBus I/O expanders, made mostly by NXP or TI. Compatible
619 4 bits: pca9536, pca9537
621 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
622 pca9556, pca9557, pca9574, tca6408, xra1202
624 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
629 40 bits: pca9505, pca9698
631 config GPIO_PCA953X_IRQ
632 bool "Interrupt controller support for PCA953x"
633 depends on GPIO_PCA953X=y
634 select GPIOLIB_IRQCHIP
636 Say yes here to enable the pca953x to be used as an interrupt
637 controller. It requires the driver to be built in the kernel.
640 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
642 select GPIOLIB_IRQCHIP
645 Say yes here to provide access to most "quasi-bidirectional" I2C
646 GPIO expanders used for additional digital outputs or inputs.
647 Most of these parts are from NXP, though TI is a second source for
648 some of them. Compatible models include:
650 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
651 pca9670, pca9672, pca9674, pca9674a,
654 16 bits: pcf8575, pcf8575c, pca8575,
655 pca9671, pca9673, pca9675
657 Your board setup code will need to declare the expanders in
658 use, and assign numbers to the GPIOs they expose. Those GPIOs
659 can then be used from drivers and other kernel code, just like
660 other GPIOs, but only accessible from task contexts.
662 This driver provides an in-kernel interface to those GPIOs using
663 platform-neutral GPIO calls.
666 bool "Semtech SX150x I2C GPIO expander"
668 select GPIOLIB_IRQCHIP
671 Say yes here to provide support for Semtech SX150-series I2C
672 GPIO expanders. Compatible models include:
679 menu "MFD GPIO expanders"
682 tristate "GPIO Support for ADP5520 PMIC"
683 depends on PMIC_ADP5520
685 This option enables support for on-chip GPIO found
686 on Analog Devices ADP5520 PMICs.
689 tristate "Wolfson Microelectronics Arizona class devices"
690 depends on MFD_ARIZONA
692 Support for GPIOs on Wolfson Arizona class devices.
694 config GPIO_CRYSTAL_COVE
695 tristate "GPIO support for Crystal Cove PMIC"
696 depends on INTEL_SOC_PMIC
697 select GPIOLIB_IRQCHIP
699 Support for GPIO pins on Crystal Cove PMIC.
701 Say Yes if you have a Intel SoC based tablet with Crystal Cove PMIC
704 This driver can also be built as a module. If so, the module will be
705 called gpio-crystalcove.
708 tristate "AMD CS5535/CS5536 GPIO support"
709 depends on MFD_CS5535
711 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
712 can be used for quite a number of things. The CS5535/6 is found on
713 AMD Geode and Lemote Yeeloong devices.
718 tristate "Dialog DA9052 GPIO"
719 depends on PMIC_DA9052
721 Say yes here to enable the GPIO driver for the DA9052 chip.
724 tristate "Dialog Semiconductor DA9055 GPIO"
725 depends on MFD_DA9055
727 Say yes here to enable the GPIO driver for the DA9055 chip.
729 The Dialog DA9055 PMIC chip has 3 GPIO pins that can be
730 be controller by this driver.
732 If driver is built as a module it will be called gpio-da9055.
735 tristate "Diolan DLN2 GPIO support"
737 select GPIOLIB_IRQCHIP
740 Select this option to enable GPIO driver for the Diolan DLN2
743 This driver can also be built as a module. If so, the module
744 will be called gpio-dln2.
747 tristate "Janz VMOD-TTL Digital IO Module"
748 depends on MFD_JANZ_CMODIO
750 This enables support for the Janz VMOD-TTL Digital IO module.
751 This driver provides support for driving the pins in output
752 mode only. Input mode is not supported.
755 tristate "Kontron ETX / COMexpress GPIO"
756 depends on MFD_KEMPLD
758 This enables support for the PLD GPIO interface on some Kontron ETX
759 and COMexpress (ETXexpress) modules.
761 This driver can also be built as a module. If so, the module will be
765 tristate "TI/National Semiconductor LP3943 GPIO expander"
766 depends on MFD_LP3943
768 GPIO driver for LP3943 MFD.
769 LP3943 can be used as a GPIO expander which provides up to 16 GPIOs.
770 Open drain outputs are required for this usage.
773 bool "Intel MSIC mixed signal gpio support"
774 depends on MFD_INTEL_MSIC
776 Enable support for GPIO on intel MSIC controllers found in
780 bool "TI PALMAS series PMICs GPIO"
781 depends on MFD_PALMAS
783 Select this option to enable GPIO driver for the TI PALMAS
787 bool "RICOH RC5T583 GPIO"
788 depends on MFD_RC5T583
790 Select this option to enable GPIO driver for the Ricoh RC5T583
792 This driver provides the support for driving/reading the gpio pins
793 of RC5T583 device through standard gpio library.
799 select GPIOLIB_IRQCHIP
801 This enables support for the GPIOs found on the STMPE I/O
806 depends on MFD_TC3589X
808 select GPIOLIB_IRQCHIP
810 This enables support for the GPIOs found on the TC3589X
813 config GPIO_TIMBERDALE
814 bool "Support for timberdale GPIO IP"
815 depends on MFD_TIMBERDALE
817 Add support for the GPIO IP in the timberdale FPGA.
821 depends on MFD_TPS6586X
823 Select this option to enable GPIO driver for the TPS6586X
828 depends on MFD_TPS65910
830 Select this option to enable GPIO driver for the TPS65910
834 tristate "TI TPS65912 GPIO"
835 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
837 This driver supports TPS65912 gpio chip
840 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
841 depends on TWL4030_CORE
843 Say yes here to access the GPIO signals of various multi-function
844 power management chips from Texas Instruments.
847 tristate "TWL6040 GPO"
848 depends on TWL6040_CORE
850 Say yes here to access the GPO signals of twl6040
851 audio chip from Texas Instruments.
854 tristate "Philips UCB1400 GPIO"
855 depends on UCB1400_CORE
857 This enables support for the Philips UCB1400 GPIO pins.
858 The UCB1400 is an AC97 audio codec.
861 tristate "WM831x GPIOs"
862 depends on MFD_WM831X
864 Say yes here to access the GPIO signals of WM831x power management
865 chips from Wolfson Microelectronics.
868 tristate "WM8350 GPIOs"
869 depends on MFD_WM8350
871 Say yes here to access the GPIO signals of WM8350 power management
872 chips from Wolfson Microelectronics.
875 tristate "WM8994 GPIOs"
876 depends on MFD_WM8994
878 Say yes here to access the GPIO signals of WM8994 audio hub
879 CODECs from Wolfson Microelectronics.
883 menu "PCI GPIO expanders"
887 tristate "AMD 8111 GPIO driver"
890 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
892 Note, that usually system firmware/ACPI handles GPIO pins on their
893 own and users might easily break their systems with uncarefull usage
899 tristate "BT8XX GPIO abuser"
900 depends on PCI && VIDEO_BT848=n
902 The BT8xx frame grabber chip has 24 GPIO pins that can be abused
903 as a cheap PCI GPIO card.
905 This chip can be found on Miro, Hauppauge and STB TV-cards.
907 The card needs to be physically altered for using it as a
908 GPIO card. For more information on how to build a GPIO card
909 from a BT8xx TV card, see the documentation file at
910 Documentation/bt8xxgpio.txt
914 config GPIO_INTEL_MID
915 bool "Intel Mid GPIO support"
916 depends on PCI && X86
917 select GPIOLIB_IRQCHIP
919 Say Y here to support Intel Mid GPIO.
922 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
924 select GENERIC_IRQ_CHIP
926 ML7213 is companion chip for Intel Atom E6xx series.
927 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
928 Hub) which is for IVI(In-Vehicle Infotainment) use.
929 This driver can access the IOH's GPIO device.
932 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
933 depends on PCI && (X86_32 || COMPILE_TEST)
934 select GENERIC_IRQ_CHIP
936 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
937 which is an IOH(Input/Output Hub) for x86 embedded processor.
938 This driver can access PCH GPIO device.
940 This driver also can be used for LAPIS Semiconductor IOH(Input/
941 Output Hub), ML7223 and ML7831.
942 ML7223 IOH is for MP(Media Phone) use.
943 ML7831 IOH is for general purpose use.
944 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
945 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
948 tristate "RDC R-321x GPIO support"
953 Support for the RDC R321x SoC GPIOs over southbridge
954 PCI configuration space.
956 config GPIO_SODAVILLE
957 bool "Intel Sodaville GPIO support"
958 depends on X86 && PCI && OF
960 select GENERIC_IRQ_CHIP
962 Say Y here to support Intel Sodaville GPIO.
966 menu "SPI GPIO expanders"
967 depends on SPI_MASTER
970 tristate "74x164 serial-in/parallel-out 8-bits shift register"
971 depends on SPI_MASTER && OF
973 Driver for 74x164 compatible serial-in/parallel-out 8-outputs
974 shift registers. This driver can be used to provide access
975 to more gpio outputs.
978 tristate "Maxim MAX7301 GPIO expander"
979 depends on SPI_MASTER
982 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
985 tristate "Microchip MCP23xxx I/O expander"
986 depends on (SPI_MASTER && !I2C) || I2C
988 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
990 This provides a GPIO interface supporting inputs and outputs.
991 The I2C versions of the chips can be used as interrupt-controller.
994 tristate "Freescale MC33880 high-side/low-side switch"
995 depends on SPI_MASTER
997 SPI driver for Freescale MC33880 high-side/low-side switch.
998 This provides GPIO interface supporting inputs and outputs.
1002 menu "USB GPIO expanders"
1005 config GPIO_VIPERBOARD
1006 tristate "Viperboard GPIO a & b support"
1007 depends on MFD_VIPERBOARD && USB
1009 Say yes here to access the GPIO signals of Nano River
1010 Technologies Viperboard. There are two GPIO chips on the
1011 board: gpioa and gpiob.
1012 See viperboard API specification and Nano
1013 River Tech's viperboard.h for detailed meaning
1014 of the module parameters.