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
94 tristate "Dialog DA9052 GPIO"
95 depends on PMIC_DA9052
97 Say yes here to enable the GPIO driver for the DA9052 chip.
100 tristate "Dialog Semiconductor DA9055 GPIO"
101 depends on MFD_DA9055
103 Say yes here to enable the GPIO driver for the DA9055 chip.
105 The Dialog DA9055 PMIC chip has 3 GPIO pins that can be
106 be controller by this driver.
108 If driver is built as a module it will be called gpio-da9055.
113 comment "Memory mapped GPIO drivers:"
115 config GPIO_74XX_MMIO
116 tristate "GPIO driver for 74xx-ICs with MMIO access"
120 Say yes here to support GPIO functionality for 74xx-compatible ICs
121 with MMIO access. Compatible models include:
122 1 bit: 741G125 (Input), 741G74 (Output)
123 2 bits: 742G125 (Input), 7474 (Output)
124 4 bits: 74125 (Input), 74175 (Output)
125 6 bits: 74365 (Input), 74174 (Output)
126 8 bits: 74244 (Input), 74273 (Output)
127 16 bits: 741624 (Input), 7416374 (Output)
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.
143 config GPIO_GENERIC_PLATFORM
144 tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
147 Say yes here to support basic platform_device memory-mapped GPIO controllers.
150 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 "Altera GPIO"
163 select GPIOLIB_IRQCHIP
165 Say Y or M here to build support for the Altera PIO device.
167 If driver is built as a module it will be called gpio-altera.
170 tristate "IT8761E GPIO support"
171 depends on X86 # unconditional access to IO space.
173 Say yes here to support GPIO functionality of IT8761E super I/O chip.
176 tristate "Emma Mobile GPIO"
177 depends on ARM && OF_GPIO
179 Say yes here to support GPIO on Renesas Emma Mobile SoCs.
183 depends on ARCH_EP93XX
187 bool "LSI ZEVIO SoC memory mapped GPIOs"
188 depends on ARM && OF_GPIO
190 Say yes here to support the GPIO controller in LSI ZEVIO SoCs.
192 config GPIO_MM_LANTIQ
193 bool "Lantiq Memory mapped GPIOs"
194 depends on LANTIQ && SOC_XWAY
196 This enables support for memory mapped GPIOs on the External Bus Unit
197 (EBU) found on Lantiq SoCs. The gpios are output only as they are
198 created by attaching a 16bit latch to the bus.
201 tristate "F71882FG and F71889F GPIO support"
204 This option enables support for GPIOs found on Fintek Super-I/O
205 chips F71882FG and F71889F.
207 To compile this driver as a module, choose M here: the module will
208 be called f7188x-gpio.
211 bool "GPIO support for Fujitsu MB86S7x Platforms"
212 depends on ARCH_MB86S7X
214 Say yes here to support the GPIO controller in Fujitsu MB86S70 SoCs.
217 bool "MOXART GPIO support"
218 depends on ARCH_MOXART
221 Select this option to enable GPIO driver for
222 MOXA ART SoC devices.
226 depends on PPC_MPC52xx
229 bool "MPC512x/MPC8xxx GPIO support"
230 depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \
231 FSL_SOC_BOOKE || PPC_86xx
233 Say Y here if you're going to use hardware that connects to the
234 MPC512x/831x/834x/837x/8572/8610 GPIOs.
237 tristate "Qualcomm MSM GPIO v1"
238 depends on GPIOLIB && ARCH_MSM && (ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50)
240 Say yes here to support the GPIO interface on ARM v6 based
241 Qualcomm MSM chips. Most of the pins on the MSM can be
242 selected for GPIO, and are controlled by this driver.
245 tristate "Qualcomm MSM GPIO v2"
246 depends on GPIOLIB && OF && ARCH_QCOM
248 Say yes here to support the GPIO interface on ARM v7 based
249 Qualcomm MSM chips. Most of the pins on the MSM can be
250 selected for GPIO, and are controlled by this driver.
254 depends on PLAT_ORION
257 select GENERIC_IRQ_CHIP
263 select GENERIC_IRQ_CHIP
269 select GENERIC_IRQ_CHIP
272 tristate "Cavium OCTEON GPIO"
273 depends on GPIOLIB && CAVIUM_OCTEON_SOC
276 Say yes here to support the on-chip GPIO lines on the OCTEON
280 bool "TI OMAP GPIO support" if COMPILE_TEST && !ARCH_OMAP2PLUS
281 default y if ARCH_OMAP
283 select GENERIC_IRQ_CHIP
284 select GPIOLIB_IRQCHIP
286 Say yes here to enable GPIO support for TI OMAP SoCs.
289 bool "PrimeCell PL061 GPIO support"
292 select GPIOLIB_IRQCHIP
294 Say yes here to support the PrimeCell PL061 GPIO device
297 bool "PXA GPIO support"
298 depends on ARCH_PXA || ARCH_MMP
300 Say yes here to support the PXA GPIO device
303 tristate "Renesas R-Car GPIO"
304 depends on ARM && (ARCH_SHMOBILE || COMPILE_TEST)
305 select GPIOLIB_IRQCHIP
307 Say yes here to support GPIO on Renesas R-Car SoCs.
311 depends on PLAT_SAMSUNG
313 Legacy GPIO support. Use only for platforms without support for
317 tristate "SMSC SCH311x SuperI/O GPIO"
319 Driver to enable the GPIOs found on SMSC SMSC SCH3112, SCH3114 and
320 SCH3116 "Super I/O" chipsets.
322 To compile this driver as a module, choose M here: the module will
323 be called gpio-sch311x.
325 config GPIO_SPEAR_SPICS
326 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
327 depends on PLAT_SPEAR
328 select GENERIC_IRQ_CHIP
330 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
333 bool "STA2x11/ConneXt GPIO support"
334 depends on MFD_STA2X11
335 select GENERIC_IRQ_CHIP
337 Say yes here to support the STA2x11/ConneXt GPIO device.
338 The GPIO module has 128 GPIO pins with alternate functions.
341 tristate "GPIO based on SYSCON"
342 depends on MFD_SYSCON && OF
344 Say yes here to support GPIO functionality though SYSCON driver.
347 tristate "TS-5500 DIO blocks and compatibles"
348 depends on TS5500 || COMPILE_TEST
350 This driver supports Digital I/O exposed by pin blocks found on some
351 Technologic Systems platforms. It includes, but is not limited to, 3
352 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
356 bool "Toumaz Xenif TZ1090 GPIO support"
357 depends on SOC_TZ1090
358 select GENERIC_IRQ_CHIP
361 Say yes here to support Toumaz Xenif TZ1090 GPIOs.
363 config GPIO_TZ1090_PDC
364 bool "Toumaz Xenif TZ1090 PDC GPIO support"
365 depends on SOC_TZ1090
368 Say yes here to support Toumaz Xenif TZ1090 PDC GPIOs.
372 depends on ARCH_MXC && SOC_VF610
373 select GPIOLIB_IRQCHIP
375 Say yes here to support Vybrid vf610 GPIOs.
378 bool "APM X-Gene GPIO controller support"
379 depends on ARM64 && OF_GPIO
381 This driver is to support the GPIO block within the APM X-Gene SoC
382 platform's generic flash controller. The GPIO pins are muxed with
383 the generic flash controller's address and data pins. Say yes
384 here to enable the GFC GPIO functionality.
387 tristate "APM X-Gene GPIO standby controller support"
388 depends on ARCH_XGENE && OF_GPIO
391 This driver supports the GPIO block within the APM X-Gene
392 Standby Domain. Say yes here to enable the GPIO functionality.
395 tristate "Xilinx GPIO support"
396 depends on OF_GPIO && (PPC || MICROBLAZE || ARCH_ZYNQ || X86)
398 Say yes here to support the Xilinx FPGA GPIO device
401 tristate "Xilinx Zynq GPIO support"
403 select GPIOLIB_IRQCHIP
405 Say yes here to support Xilinx Zynq GPIO controller.
408 bool "Xtensa GPIO32 support"
410 depends on HAVE_XTENSA_GPIO32
413 Say yes here to support the Xtensa internal GPIO32 IMPWIRE (input)
414 and EXPSTATE (output) ports
417 tristate "NEC VR4100 series General-purpose I/O Uint support"
418 depends on CPU_VR41XX
420 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
423 tristate "Intel SCH/TunnelCreek/Centerton/Quark X1000 GPIO"
424 depends on PCI && X86
428 Say yes here to support GPIO interface on Intel Poulsbo SCH,
429 Intel Tunnel Creek processor, Intel Centerton processor or
430 Intel Quark X1000 SoC.
432 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
433 powered by the core power rail and are turned off during sleep
434 modes (S3 and higher). The remaining four GPIOs are powered by
435 the Intel SCH suspend power supply. These GPIOs remain
436 active during S3. The suspend powered GPIOs can be used to wake the
437 system from the Suspend-to-RAM state.
439 The Intel Tunnel Creek processor has 5 GPIOs powered by the
440 core power rail and 9 from suspend power supply.
442 The Intel Centerton processor has a total of 30 GPIO pins.
443 Twenty-one are powered by the core power rail and 9 from the
444 suspend power supply.
446 The Intel Quark X1000 SoC has 2 GPIOs powered by the core
447 power well and 6 from the suspend power well.
450 tristate "Intel ICH GPIO"
451 depends on PCI && X86
455 Say yes here to support the GPIO functionality of a number of Intel
456 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
457 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
458 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
463 tristate "Intel IOP GPIO"
464 depends on ARM && (ARCH_IOP32X || ARCH_IOP33X)
466 Say yes here to support the GPIO functionality of a number of Intel
472 tristate "VIA VX855/VX875 GPIO"
477 Support access to the VX855/VX875 GPIO lines through the gpio library.
479 This driver provides common support for accessing the device,
480 additional drivers must be enabled in order to use the
481 functionality of the device.
484 bool "GE FPGA based GPIO"
488 Support for common GPIO functionality provided on some GE Single Board
491 This driver provides basic support (configure as input or output, read
492 and write pin state) for GPIO implemented in a number of GE single
495 config GPIO_LYNXPOINT
496 tristate "Intel Lynxpoint GPIO support"
497 depends on ACPI && X86
498 select GPIOLIB_IRQCHIP
500 driver for GPIO functionality on Intel Lynxpoint PCH chipset
501 Requires ACPI device enumeration code to set up a platform device.
504 tristate "Aeroflex Gaisler GRGPIO support"
509 Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
510 VHDL IP core library.
514 select GENERIC_IRQ_CHIP
517 comment "I2C GPIO expanders:"
520 tristate "Wolfson Microelectronics Arizona class devices"
521 depends on MFD_ARIZONA
523 Support for GPIOs on Wolfson Arizona class devices.
525 config GPIO_CRYSTAL_COVE
526 tristate "GPIO support for Crystal Cove PMIC"
527 depends on INTEL_SOC_PMIC
528 select GPIOLIB_IRQCHIP
530 Support for GPIO pins on Crystal Cove PMIC.
532 Say Yes if you have a Intel SoC based tablet with Crystal Cove PMIC
535 This driver can also be built as a module. If so, the module will be
536 called gpio-crystalcove.
539 tristate "TI/National Semiconductor LP3943 GPIO expander"
540 depends on MFD_LP3943
542 GPIO driver for LP3943 MFD.
543 LP3943 can be used as a GPIO expander which provides up to 16 GPIOs.
544 Open drain outputs are required for this usage.
547 tristate "Maxim MAX7300 GPIO expander"
551 GPIO driver for Maxim MAX7300 I2C-based GPIO expander.
554 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
557 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
558 Port Expanders. Each IO port on these chips has a fixed role of
559 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
560 Input and Output (designed by 'P'). The combinations are listed
563 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
564 max7322 (4I4O), max7323 (4P4O)
566 16 bits: max7324 (8I8O), max7325 (8P8O),
567 max7326 (4I12O), max7327 (4P12O)
569 Board setup code must specify the model to use, and the start
570 number for these GPIOs.
572 config GPIO_MAX732X_IRQ
573 bool "Interrupt controller support for MAX732x"
574 depends on GPIO_MAX732X=y
575 select GPIOLIB_IRQCHIP
577 Say yes here to enable the max732x to be used as an interrupt
578 controller. It requires the driver to be built in the kernel.
580 config GPIO_MC9S08DZ60
581 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
582 depends on I2C=y && MACH_MX35_3DS
584 Select this to enable the MC9S08DZ60 GPIO driver
587 tristate "PCA95[357]x, PCA9698, TCA64xx, and MAX7310 I/O ports"
590 Say yes here to provide access to several register-oriented
591 SMBus I/O expanders, made mostly by NXP or TI. Compatible
594 4 bits: pca9536, pca9537
596 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
597 pca9556, pca9557, pca9574, tca6408, xra1202
599 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
604 40 bits: pca9505, pca9698
606 config GPIO_PCA953X_IRQ
607 bool "Interrupt controller support for PCA953x"
608 depends on GPIO_PCA953X=y
609 select GPIOLIB_IRQCHIP
611 Say yes here to enable the pca953x to be used as an interrupt
612 controller. It requires the driver to be built in the kernel.
615 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
617 select GPIOLIB_IRQCHIP
620 Say yes here to provide access to most "quasi-bidirectional" I2C
621 GPIO expanders used for additional digital outputs or inputs.
622 Most of these parts are from NXP, though TI is a second source for
623 some of them. Compatible models include:
625 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
626 pca9670, pca9672, pca9674, pca9674a,
629 16 bits: pcf8575, pcf8575c, pca8575,
630 pca9671, pca9673, pca9675
632 Your board setup code will need to declare the expanders in
633 use, and assign numbers to the GPIOs they expose. Those GPIOs
634 can then be used from drivers and other kernel code, just like
635 other GPIOs, but only accessible from task contexts.
637 This driver provides an in-kernel interface to those GPIOs using
638 platform-neutral GPIO calls.
641 bool "RICOH RC5T583 GPIO"
642 depends on MFD_RC5T583
644 Select this option to enable GPIO driver for the Ricoh RC5T583
646 This driver provides the support for driving/reading the gpio pins
647 of RC5T583 device through standard gpio library.
650 bool "Semtech SX150x I2C GPIO expander"
652 select GPIOLIB_IRQCHIP
655 Say yes here to provide support for Semtech SX150-series I2C
656 GPIO expanders. Compatible models include:
665 select GPIOLIB_IRQCHIP
667 This enables support for the GPIOs found on the STMPE I/O
671 bool "XWAY STP GPIOs"
674 This enables support for the Serial To Parallel (STP) unit found on
675 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
676 that can be up to 24 bit. This peripheral is aimed at driving leds.
677 Some of the gpios/leds can be auto updated by the soc with dsl and
682 depends on MFD_TC3589X
683 select GPIOLIB_IRQCHIP
685 This enables support for the GPIOs found on the TC3589X
689 tristate "TI TPS65912 GPIO"
690 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
692 This driver supports TPS65912 gpio chip
695 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
696 depends on TWL4030_CORE
698 Say yes here to access the GPIO signals of various multi-function
699 power management chips from Texas Instruments.
702 tristate "TWL6040 GPO"
703 depends on TWL6040_CORE
705 Say yes here to access the GPO signals of twl6040
706 audio chip from Texas Instruments.
709 tristate "WM831x GPIOs"
710 depends on MFD_WM831X
712 Say yes here to access the GPIO signals of WM831x power management
713 chips from Wolfson Microelectronics.
716 tristate "WM8350 GPIOs"
717 depends on MFD_WM8350
719 Say yes here to access the GPIO signals of WM8350 power management
720 chips from Wolfson Microelectronics.
723 tristate "WM8994 GPIOs"
724 depends on MFD_WM8994
726 Say yes here to access the GPIO signals of WM8994 audio hub
727 CODECs from Wolfson Microelectronics.
730 tristate "GPIO Support for ADP5520 PMIC"
731 depends on PMIC_ADP5520
733 This option enables support for on-chip GPIO found
734 on Analog Devices ADP5520 PMICs.
737 tristate "ADP5588 I2C GPIO expander"
740 This option enables support for 18 GPIOs found
741 on Analog Devices ADP5588 GPIO Expanders.
743 config GPIO_ADP5588_IRQ
744 bool "Interrupt controller support for ADP5588"
745 depends on GPIO_ADP5588=y
747 Say yes here to enable the adp5588 to be used as an interrupt
748 controller. It requires the driver to be built in the kernel.
751 tristate "Avionic Design N-bit GPIO expander"
752 depends on I2C && OF_GPIO
753 select GPIOLIB_IRQCHIP
755 This option enables support for N GPIOs found on Avionic Design
756 I2C GPIO expanders. The register space will be extended by powers
757 of two, so the controller will need to accommodate for that. For
758 example: if a controller provides 48 pins, 6 registers will be
759 enough to represent all pins, but the driver will assume a
760 register layout for 64 pins (8 registers).
762 comment "PCI GPIO expanders:"
765 tristate "AMD CS5535/CS5536 GPIO support"
766 depends on MFD_CS5535
768 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
769 can be used for quite a number of things. The CS5535/6 is found on
770 AMD Geode and Lemote Yeeloong devices.
775 tristate "BT8XX GPIO abuser"
776 depends on PCI && VIDEO_BT848=n
778 The BT8xx frame grabber chip has 24 GPIO pins that can be abused
779 as a cheap PCI GPIO card.
781 This chip can be found on Miro, Hauppauge and STB TV-cards.
783 The card needs to be physically altered for using it as a
784 GPIO card. For more information on how to build a GPIO card
785 from a BT8xx TV card, see the documentation file at
786 Documentation/bt8xxgpio.txt
791 tristate "AMD 8111 GPIO driver"
794 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
796 Note, that usually system firmware/ACPI handles GPIO pins on their
797 own and users might easily break their systems with uncarefull usage
802 config GPIO_INTEL_MID
803 bool "Intel Mid GPIO support"
804 depends on PCI && X86
805 select GPIOLIB_IRQCHIP
807 Say Y here to support Intel Mid GPIO.
810 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
811 depends on PCI && (X86_32 || COMPILE_TEST)
812 select GENERIC_IRQ_CHIP
814 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
815 which is an IOH(Input/Output Hub) for x86 embedded processor.
816 This driver can access PCH GPIO device.
818 This driver also can be used for LAPIS Semiconductor IOH(Input/
819 Output Hub), ML7223 and ML7831.
820 ML7223 IOH is for MP(Media Phone) use.
821 ML7831 IOH is for general purpose use.
822 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
823 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
826 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
828 select GENERIC_IRQ_CHIP
830 ML7213 is companion chip for Intel Atom E6xx series.
831 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
832 Hub) which is for IVI(In-Vehicle Infotainment) use.
833 This driver can access the IOH's GPIO device.
835 config GPIO_SODAVILLE
836 bool "Intel Sodaville GPIO support"
837 depends on X86 && PCI && OF
839 select GENERIC_IRQ_CHIP
841 Say Y here to support Intel Sodaville GPIO.
843 config GPIO_TIMBERDALE
844 bool "Support for timberdale GPIO IP"
845 depends on MFD_TIMBERDALE
847 Add support for the GPIO IP in the timberdale FPGA.
850 tristate "RDC R-321x GPIO support"
855 Support for the RDC R321x SoC GPIOs over southbridge
856 PCI configuration space.
858 comment "SPI GPIO expanders:"
861 tristate "Maxim MAX7301 GPIO expander"
862 depends on SPI_MASTER
865 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
868 tristate "Microchip MCP23xxx I/O expander"
869 depends on (SPI_MASTER && !I2C) || I2C
871 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
873 This provides a GPIO interface supporting inputs and outputs.
874 The I2C versions of the chips can be used as interrupt-controller.
877 tristate "Freescale MC33880 high-side/low-side switch"
878 depends on SPI_MASTER
880 SPI driver for Freescale MC33880 high-side/low-side switch.
881 This provides GPIO interface supporting inputs and outputs.
884 tristate "74x164 serial-in/parallel-out 8-bits shift register"
885 depends on SPI_MASTER && OF
887 Driver for 74x164 compatible serial-in/parallel-out 8-outputs
888 shift registers. This driver can be used to provide access
889 to more gpio outputs.
891 comment "AC97 GPIO expanders:"
894 tristate "Philips UCB1400 GPIO"
895 depends on UCB1400_CORE
897 This enables support for the Philips UCB1400 GPIO pins.
898 The UCB1400 is an AC97 audio codec.
900 comment "LPC GPIO expanders:"
903 tristate "Kontron ETX / COMexpress GPIO"
904 depends on MFD_KEMPLD
906 This enables support for the PLD GPIO interface on some Kontron ETX
907 and COMexpress (ETXexpress) modules.
909 This driver can also be built as a module. If so, the module will be
912 comment "MODULbus GPIO expanders:"
915 tristate "Janz VMOD-TTL Digital IO Module"
916 depends on MFD_JANZ_CMODIO
918 This enables support for the Janz VMOD-TTL Digital IO module.
919 This driver provides support for driving the pins in output
920 mode only. Input mode is not supported.
923 bool "TI PALMAS series PMICs GPIO"
924 depends on MFD_PALMAS
926 Select this option to enable GPIO driver for the TI PALMAS
931 depends on MFD_TPS6586X
933 Select this option to enable GPIO driver for the TPS6586X
938 depends on MFD_TPS65910
940 Select this option to enable GPIO driver for the TPS65910
944 bool "Intel MSIC mixed signal gpio support"
945 depends on MFD_INTEL_MSIC
947 Enable support for GPIO on intel MSIC controllers found in
951 bool "Broadcom Kona GPIO"
952 depends on OF_GPIO && (ARCH_BCM_MOBILE || COMPILE_TEST)
954 Turn on GPIO support for Broadcom "Kona" chips.
956 comment "USB GPIO expanders:"
958 config GPIO_VIPERBOARD
959 tristate "Viperboard GPIO a & b support"
960 depends on MFD_VIPERBOARD && USB
962 Say yes here to access the GPIO signals of Nano River
963 Technologies Viperboard. There are two GPIO chips on the
964 board: gpioa and gpiob.
965 See viperboard API specification and Nano
966 River Tech's viperboard.h for detailed meaning
967 of the module parameters.
970 tristate "Diolan DLN2 GPIO support"
972 select GPIOLIB_IRQCHIP
975 Select this option to enable GPIO driver for the Diolan DLN2
978 This driver can also be built as a module. If so, the module
979 will be called gpio-dln2.