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 "CLPS711X GPIO support"
131 depends on ARCH_CLPS711X || COMPILE_TEST
134 Say yes here to support GPIO on CLPS711X SoCs.
137 bool "TI Davinci/Keystone GPIO support"
138 default y if ARCH_DAVINCI
139 depends on ARM && (ARCH_DAVINCI || ARCH_KEYSTONE)
141 Say yes here to enable GPIO support for TI Davinci/Keystone SoCs.
144 tristate "Synopsys DesignWare APB GPIO driver"
145 depends on ((ARM || ARM64) && OF_GPIO) || X86_INTEL_QUARK
147 select GENERIC_IRQ_CHIP
149 Say Y or M here to build support for the Synopsys DesignWare APB
153 tristate "Emma Mobile GPIO"
154 depends on ARM && OF_GPIO
156 Say yes here to support GPIO on Renesas Emma Mobile SoCs.
160 depends on ARCH_EP93XX
164 tristate "F71869, F71869A, F71882FG and F71889F GPIO support"
167 This option enables support for GPIOs found on Fintek Super-I/O
168 chips F71869, F71869A, F71882FG and F71889F.
170 To compile this driver as a module, choose M here: the module will
171 be called f7188x-gpio.
174 bool "GE FPGA based GPIO"
178 Support for common GPIO functionality provided on some GE Single Board
181 This driver provides basic support (configure as input or output, read
182 and write pin state) for GPIO implemented in a number of GE single
185 config GPIO_GENERIC_PLATFORM
186 tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
189 Say yes here to support basic platform_device memory-mapped GPIO controllers.
192 tristate "Aeroflex Gaisler GRGPIO support"
197 Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
198 VHDL IP core library.
201 tristate "Intel ICH GPIO"
202 depends on PCI && X86
206 Say yes here to support the GPIO functionality of a number of Intel
207 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
208 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
209 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
214 tristate "Intel IOP GPIO"
215 depends on ARM && (ARCH_IOP32X || ARCH_IOP33X)
217 Say yes here to support the GPIO functionality of a number of Intel
223 tristate "IT8761E GPIO support"
224 depends on X86 # unconditional access to IO space.
226 Say yes here to support GPIO functionality of IT8761E super I/O chip.
229 bool "Loongson-2/3 GPIO support"
230 depends on CPU_LOONGSON2 || CPU_LOONGSON3
232 driver for GPIO functionality on Loongson-2F/3A/3B processors.
234 config GPIO_LYNXPOINT
235 tristate "Intel Lynxpoint GPIO support"
236 depends on ACPI && X86
237 select GPIOLIB_IRQCHIP
239 driver for GPIO functionality on Intel Lynxpoint PCH chipset
240 Requires ACPI device enumeration code to set up a platform device.
243 bool "GPIO support for Fujitsu MB86S7x Platforms"
244 depends on ARCH_MB86S7X
246 Say yes here to support the GPIO controller in Fujitsu MB86S70 SoCs.
248 config GPIO_MM_LANTIQ
249 bool "Lantiq Memory mapped GPIOs"
250 depends on LANTIQ && SOC_XWAY
252 This enables support for memory mapped GPIOs on the External Bus Unit
253 (EBU) found on Lantiq SoCs. The gpios are output only as they are
254 created by attaching a 16bit latch to the bus.
257 bool "MOXART GPIO support"
258 depends on ARCH_MOXART
261 Select this option to enable GPIO driver for
262 MOXA ART SoC devices.
266 depends on PPC_MPC52xx
269 bool "MPC512x/MPC8xxx GPIO support"
270 depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \
271 FSL_SOC_BOOKE || PPC_86xx
273 Say Y here if you're going to use hardware that connects to the
274 MPC512x/831x/834x/837x/8572/8610 GPIOs.
277 tristate "Qualcomm MSM GPIO v1"
278 depends on GPIOLIB && ARCH_MSM && (ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50)
280 Say yes here to support the GPIO interface on ARM v6 based
281 Qualcomm MSM chips. Most of the pins on the MSM can be
282 selected for GPIO, and are controlled by this driver.
285 tristate "Qualcomm MSM GPIO v2"
286 depends on GPIOLIB && OF && ARCH_QCOM
288 Say yes here to support the GPIO interface on ARM v7 based
289 Qualcomm MSM chips. Most of the pins on the MSM can be
290 selected for GPIO, and are controlled by this driver.
294 depends on PLAT_ORION
297 select GENERIC_IRQ_CHIP
303 select GENERIC_IRQ_CHIP
309 select GENERIC_IRQ_CHIP
312 tristate "Cavium OCTEON GPIO"
313 depends on GPIOLIB && CAVIUM_OCTEON_SOC
316 Say yes here to support the on-chip GPIO lines on the OCTEON
320 bool "TI OMAP GPIO support" if COMPILE_TEST && !ARCH_OMAP2PLUS
321 default y if ARCH_OMAP
323 select GENERIC_IRQ_CHIP
324 select GPIOLIB_IRQCHIP
326 Say yes here to enable GPIO support for TI OMAP SoCs.
329 bool "PrimeCell PL061 GPIO support"
332 select GPIOLIB_IRQCHIP
334 Say yes here to support the PrimeCell PL061 GPIO device
337 bool "PXA GPIO support"
338 depends on ARCH_PXA || ARCH_MMP
340 Say yes here to support the PXA GPIO device
343 tristate "Renesas R-Car GPIO"
344 depends on ARM && (ARCH_SHMOBILE || COMPILE_TEST)
345 select GPIOLIB_IRQCHIP
347 Say yes here to support GPIO on Renesas R-Car SoCs.
351 depends on PLAT_SAMSUNG
353 Legacy GPIO support. Use only for platforms without support for
357 tristate "Intel SCH/TunnelCreek/Centerton/Quark X1000 GPIO"
358 depends on PCI && X86
362 Say yes here to support GPIO interface on Intel Poulsbo SCH,
363 Intel Tunnel Creek processor, Intel Centerton processor or
364 Intel Quark X1000 SoC.
366 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
367 powered by the core power rail and are turned off during sleep
368 modes (S3 and higher). The remaining four GPIOs are powered by
369 the Intel SCH suspend power supply. These GPIOs remain
370 active during S3. The suspend powered GPIOs can be used to wake the
371 system from the Suspend-to-RAM state.
373 The Intel Tunnel Creek processor has 5 GPIOs powered by the
374 core power rail and 9 from suspend power supply.
376 The Intel Centerton processor has a total of 30 GPIO pins.
377 Twenty-one are powered by the core power rail and 9 from the
378 suspend power supply.
380 The Intel Quark X1000 SoC has 2 GPIOs powered by the core
381 power well and 6 from the suspend power well.
384 tristate "SMSC SCH311x SuperI/O GPIO"
386 Driver to enable the GPIOs found on SMSC SMSC SCH3112, SCH3114 and
387 SCH3116 "Super I/O" chipsets.
389 To compile this driver as a module, choose M here: the module will
390 be called gpio-sch311x.
392 config GPIO_SPEAR_SPICS
393 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
394 depends on PLAT_SPEAR
395 select GENERIC_IRQ_CHIP
397 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
400 bool "STA2x11/ConneXt GPIO support"
401 depends on MFD_STA2X11
402 select GENERIC_IRQ_CHIP
404 Say yes here to support the STA2x11/ConneXt GPIO device.
405 The GPIO module has 128 GPIO pins with alternate functions.
408 bool "XWAY STP GPIOs"
411 This enables support for the Serial To Parallel (STP) unit found on
412 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
413 that can be up to 24 bit. This peripheral is aimed at driving leds.
414 Some of the gpios/leds can be auto updated by the soc with dsl and
418 tristate "GPIO based on SYSCON"
419 depends on MFD_SYSCON && OF
421 Say yes here to support GPIO functionality though SYSCON driver.
425 select GENERIC_IRQ_CHIP
429 tristate "TS-5500 DIO blocks and compatibles"
430 depends on TS5500 || COMPILE_TEST
432 This driver supports Digital I/O exposed by pin blocks found on some
433 Technologic Systems platforms. It includes, but is not limited to, 3
434 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
438 bool "Toumaz Xenif TZ1090 GPIO support"
439 depends on SOC_TZ1090
440 select GENERIC_IRQ_CHIP
443 Say yes here to support Toumaz Xenif TZ1090 GPIOs.
445 config GPIO_TZ1090_PDC
446 bool "Toumaz Xenif TZ1090 PDC GPIO support"
447 depends on SOC_TZ1090
450 Say yes here to support Toumaz Xenif TZ1090 PDC GPIOs.
454 depends on ARCH_MXC && SOC_VF610
455 select GPIOLIB_IRQCHIP
457 Say yes here to support Vybrid vf610 GPIOs.
460 tristate "NEC VR4100 series General-purpose I/O Uint support"
461 depends on CPU_VR41XX
463 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
466 tristate "VIA VX855/VX875 GPIO"
471 Support access to the VX855/VX875 GPIO lines through the gpio library.
473 This driver provides common support for accessing the device,
474 additional drivers must be enabled in order to use the
475 functionality of the device.
478 bool "APM X-Gene GPIO controller support"
479 depends on ARM64 && OF_GPIO
481 This driver is to support the GPIO block within the APM X-Gene SoC
482 platform's generic flash controller. The GPIO pins are muxed with
483 the generic flash controller's address and data pins. Say yes
484 here to enable the GFC GPIO functionality.
487 tristate "APM X-Gene GPIO standby controller support"
488 depends on ARCH_XGENE && OF_GPIO
491 This driver supports the GPIO block within the APM X-Gene
492 Standby Domain. Say yes here to enable the GPIO functionality.
495 tristate "Xilinx GPIO support"
496 depends on OF_GPIO && (PPC || MICROBLAZE || ARCH_ZYNQ || X86)
498 Say yes here to support the Xilinx FPGA GPIO device
501 bool "Xtensa GPIO32 support"
503 depends on HAVE_XTENSA_GPIO32
506 Say yes here to support the Xtensa internal GPIO32 IMPWIRE (input)
507 and EXPSTATE (output) ports
510 bool "LSI ZEVIO SoC memory mapped GPIOs"
511 depends on ARM && OF_GPIO
513 Say yes here to support the GPIO controller in LSI ZEVIO SoCs.
516 tristate "Xilinx Zynq GPIO support"
518 select GPIOLIB_IRQCHIP
520 Say yes here to support Xilinx Zynq GPIO controller.
524 menu "I2C GPIO expanders"
528 tristate "ADP5588 I2C GPIO expander"
531 This option enables support for 18 GPIOs found
532 on Analog Devices ADP5588 GPIO Expanders.
534 config GPIO_ADP5588_IRQ
535 bool "Interrupt controller support for ADP5588"
536 depends on GPIO_ADP5588=y
538 Say yes here to enable the adp5588 to be used as an interrupt
539 controller. It requires the driver to be built in the kernel.
542 tristate "Avionic Design N-bit GPIO expander"
543 depends on I2C && OF_GPIO
544 select GPIOLIB_IRQCHIP
546 This option enables support for N GPIOs found on Avionic Design
547 I2C GPIO expanders. The register space will be extended by powers
548 of two, so the controller will need to accommodate for that. For
549 example: if a controller provides 48 pins, 6 registers will be
550 enough to represent all pins, but the driver will assume a
551 register layout for 64 pins (8 registers).
554 tristate "Maxim MAX7300 GPIO expander"
558 GPIO driver for Maxim MAX7300 I2C-based GPIO expander.
561 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
564 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
565 Port Expanders. Each IO port on these chips has a fixed role of
566 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
567 Input and Output (designed by 'P'). The combinations are listed
570 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
571 max7322 (4I4O), max7323 (4P4O)
573 16 bits: max7324 (8I8O), max7325 (8P8O),
574 max7326 (4I12O), max7327 (4P12O)
576 Board setup code must specify the model to use, and the start
577 number for these GPIOs.
579 config GPIO_MAX732X_IRQ
580 bool "Interrupt controller support for MAX732x"
581 depends on GPIO_MAX732X=y
582 select GPIOLIB_IRQCHIP
584 Say yes here to enable the max732x to be used as an interrupt
585 controller. It requires the driver to be built in the kernel.
587 config GPIO_MC9S08DZ60
588 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
589 depends on I2C=y && MACH_MX35_3DS
591 Select this to enable the MC9S08DZ60 GPIO driver
594 tristate "PCA95[357]x, PCA9698, TCA64xx, and MAX7310 I/O ports"
597 Say yes here to provide access to several register-oriented
598 SMBus I/O expanders, made mostly by NXP or TI. Compatible
601 4 bits: pca9536, pca9537
603 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
604 pca9556, pca9557, pca9574, tca6408, xra1202
606 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
611 40 bits: pca9505, pca9698
613 config GPIO_PCA953X_IRQ
614 bool "Interrupt controller support for PCA953x"
615 depends on GPIO_PCA953X=y
616 select GPIOLIB_IRQCHIP
618 Say yes here to enable the pca953x to be used as an interrupt
619 controller. It requires the driver to be built in the kernel.
622 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
624 select GPIOLIB_IRQCHIP
627 Say yes here to provide access to most "quasi-bidirectional" I2C
628 GPIO expanders used for additional digital outputs or inputs.
629 Most of these parts are from NXP, though TI is a second source for
630 some of them. Compatible models include:
632 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
633 pca9670, pca9672, pca9674, pca9674a,
636 16 bits: pcf8575, pcf8575c, pca8575,
637 pca9671, pca9673, pca9675
639 Your board setup code will need to declare the expanders in
640 use, and assign numbers to the GPIOs they expose. Those GPIOs
641 can then be used from drivers and other kernel code, just like
642 other GPIOs, but only accessible from task contexts.
644 This driver provides an in-kernel interface to those GPIOs using
645 platform-neutral GPIO calls.
648 bool "Semtech SX150x I2C GPIO expander"
650 select GPIOLIB_IRQCHIP
653 Say yes here to provide support for Semtech SX150-series I2C
654 GPIO expanders. Compatible models include:
661 menu "MFD GPIO expanders"
664 tristate "GPIO Support for ADP5520 PMIC"
665 depends on PMIC_ADP5520
667 This option enables support for on-chip GPIO found
668 on Analog Devices ADP5520 PMICs.
671 tristate "Wolfson Microelectronics Arizona class devices"
672 depends on MFD_ARIZONA
674 Support for GPIOs on Wolfson Arizona class devices.
676 config GPIO_CRYSTAL_COVE
677 tristate "GPIO support for Crystal Cove PMIC"
678 depends on INTEL_SOC_PMIC
679 select GPIOLIB_IRQCHIP
681 Support for GPIO pins on Crystal Cove PMIC.
683 Say Yes if you have a Intel SoC based tablet with Crystal Cove PMIC
686 This driver can also be built as a module. If so, the module will be
687 called gpio-crystalcove.
690 tristate "AMD CS5535/CS5536 GPIO support"
691 depends on MFD_CS5535
693 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
694 can be used for quite a number of things. The CS5535/6 is found on
695 AMD Geode and Lemote Yeeloong devices.
700 tristate "Dialog DA9052 GPIO"
701 depends on PMIC_DA9052
703 Say yes here to enable the GPIO driver for the DA9052 chip.
706 tristate "Dialog Semiconductor DA9055 GPIO"
707 depends on MFD_DA9055
709 Say yes here to enable the GPIO driver for the DA9055 chip.
711 The Dialog DA9055 PMIC chip has 3 GPIO pins that can be
712 be controller by this driver.
714 If driver is built as a module it will be called gpio-da9055.
717 tristate "Diolan DLN2 GPIO support"
719 select GPIOLIB_IRQCHIP
722 Select this option to enable GPIO driver for the Diolan DLN2
725 This driver can also be built as a module. If so, the module
726 will be called gpio-dln2.
729 tristate "Janz VMOD-TTL Digital IO Module"
730 depends on MFD_JANZ_CMODIO
732 This enables support for the Janz VMOD-TTL Digital IO module.
733 This driver provides support for driving the pins in output
734 mode only. Input mode is not supported.
737 tristate "Kontron ETX / COMexpress GPIO"
738 depends on MFD_KEMPLD
740 This enables support for the PLD GPIO interface on some Kontron ETX
741 and COMexpress (ETXexpress) modules.
743 This driver can also be built as a module. If so, the module will be
747 tristate "TI/National Semiconductor LP3943 GPIO expander"
748 depends on MFD_LP3943
750 GPIO driver for LP3943 MFD.
751 LP3943 can be used as a GPIO expander which provides up to 16 GPIOs.
752 Open drain outputs are required for this usage.
755 bool "Intel MSIC mixed signal gpio support"
756 depends on MFD_INTEL_MSIC
758 Enable support for GPIO on intel MSIC controllers found in
762 bool "TI PALMAS series PMICs GPIO"
763 depends on MFD_PALMAS
765 Select this option to enable GPIO driver for the TI PALMAS
769 bool "RICOH RC5T583 GPIO"
770 depends on MFD_RC5T583
772 Select this option to enable GPIO driver for the Ricoh RC5T583
774 This driver provides the support for driving/reading the gpio pins
775 of RC5T583 device through standard gpio library.
781 select GPIOLIB_IRQCHIP
783 This enables support for the GPIOs found on the STMPE I/O
788 depends on MFD_TC3589X
789 select GPIOLIB_IRQCHIP
791 This enables support for the GPIOs found on the TC3589X
794 config GPIO_TIMBERDALE
795 bool "Support for timberdale GPIO IP"
796 depends on MFD_TIMBERDALE
798 Add support for the GPIO IP in the timberdale FPGA.
802 depends on MFD_TPS6586X
804 Select this option to enable GPIO driver for the TPS6586X
809 depends on MFD_TPS65910
811 Select this option to enable GPIO driver for the TPS65910
815 tristate "TI TPS65912 GPIO"
816 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
818 This driver supports TPS65912 gpio chip
821 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
822 depends on TWL4030_CORE
824 Say yes here to access the GPIO signals of various multi-function
825 power management chips from Texas Instruments.
828 tristate "TWL6040 GPO"
829 depends on TWL6040_CORE
831 Say yes here to access the GPO signals of twl6040
832 audio chip from Texas Instruments.
835 tristate "Philips UCB1400 GPIO"
836 depends on UCB1400_CORE
838 This enables support for the Philips UCB1400 GPIO pins.
839 The UCB1400 is an AC97 audio codec.
842 tristate "WM831x GPIOs"
843 depends on MFD_WM831X
845 Say yes here to access the GPIO signals of WM831x power management
846 chips from Wolfson Microelectronics.
849 tristate "WM8350 GPIOs"
850 depends on MFD_WM8350
852 Say yes here to access the GPIO signals of WM8350 power management
853 chips from Wolfson Microelectronics.
856 tristate "WM8994 GPIOs"
857 depends on MFD_WM8994
859 Say yes here to access the GPIO signals of WM8994 audio hub
860 CODECs from Wolfson Microelectronics.
864 menu "PCI GPIO expanders"
868 tristate "AMD 8111 GPIO driver"
871 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
873 Note, that usually system firmware/ACPI handles GPIO pins on their
874 own and users might easily break their systems with uncarefull usage
880 tristate "BT8XX GPIO abuser"
881 depends on PCI && VIDEO_BT848=n
883 The BT8xx frame grabber chip has 24 GPIO pins that can be abused
884 as a cheap PCI GPIO card.
886 This chip can be found on Miro, Hauppauge and STB TV-cards.
888 The card needs to be physically altered for using it as a
889 GPIO card. For more information on how to build a GPIO card
890 from a BT8xx TV card, see the documentation file at
891 Documentation/bt8xxgpio.txt
895 config GPIO_INTEL_MID
896 bool "Intel Mid GPIO support"
897 depends on PCI && X86
898 select GPIOLIB_IRQCHIP
900 Say Y here to support Intel Mid GPIO.
903 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
905 select GENERIC_IRQ_CHIP
907 ML7213 is companion chip for Intel Atom E6xx series.
908 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
909 Hub) which is for IVI(In-Vehicle Infotainment) use.
910 This driver can access the IOH's GPIO device.
913 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
914 depends on PCI && (X86_32 || COMPILE_TEST)
915 select GENERIC_IRQ_CHIP
917 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
918 which is an IOH(Input/Output Hub) for x86 embedded processor.
919 This driver can access PCH GPIO device.
921 This driver also can be used for LAPIS Semiconductor IOH(Input/
922 Output Hub), ML7223 and ML7831.
923 ML7223 IOH is for MP(Media Phone) use.
924 ML7831 IOH is for general purpose use.
925 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
926 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
929 tristate "RDC R-321x GPIO support"
934 Support for the RDC R321x SoC GPIOs over southbridge
935 PCI configuration space.
937 config GPIO_SODAVILLE
938 bool "Intel Sodaville GPIO support"
939 depends on X86 && PCI && OF
941 select GENERIC_IRQ_CHIP
943 Say Y here to support Intel Sodaville GPIO.
947 menu "SPI GPIO expanders"
948 depends on SPI_MASTER
951 tristate "74x164 serial-in/parallel-out 8-bits shift register"
952 depends on SPI_MASTER && OF
954 Driver for 74x164 compatible serial-in/parallel-out 8-outputs
955 shift registers. This driver can be used to provide access
956 to more gpio outputs.
959 tristate "Maxim MAX7301 GPIO expander"
960 depends on SPI_MASTER
963 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
966 tristate "Microchip MCP23xxx I/O expander"
967 depends on (SPI_MASTER && !I2C) || I2C
969 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
971 This provides a GPIO interface supporting inputs and outputs.
972 The I2C versions of the chips can be used as interrupt-controller.
975 tristate "Freescale MC33880 high-side/low-side switch"
976 depends on SPI_MASTER
978 SPI driver for Freescale MC33880 high-side/low-side switch.
979 This provides GPIO interface supporting inputs and outputs.
983 menu "USB GPIO expanders"
986 config GPIO_VIPERBOARD
987 tristate "Viperboard GPIO a & b support"
988 depends on MFD_VIPERBOARD && USB
990 Say yes here to access the GPIO signals of Nano River
991 Technologies Viperboard. There are two GPIO chips on the
992 board: gpioa and gpiob.
993 See viperboard API specification and Nano
994 River Tech's viperboard.h for detailed meaning
995 of the module parameters.