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 "IT8761E GPIO support"
161 depends on X86 # unconditional access to IO space.
163 Say yes here to support GPIO functionality of IT8761E super I/O chip.
166 tristate "Emma Mobile GPIO"
167 depends on ARM && OF_GPIO
169 Say yes here to support GPIO on Renesas Emma Mobile SoCs.
173 depends on ARCH_EP93XX
177 bool "LSI ZEVIO SoC memory mapped GPIOs"
178 depends on ARM && OF_GPIO
180 Say yes here to support the GPIO controller in LSI ZEVIO SoCs.
182 config GPIO_MM_LANTIQ
183 bool "Lantiq Memory mapped GPIOs"
184 depends on LANTIQ && SOC_XWAY
186 This enables support for memory mapped GPIOs on the External Bus Unit
187 (EBU) found on Lantiq SoCs. The gpios are output only as they are
188 created by attaching a 16bit latch to the bus.
191 tristate "F71882FG and F71889F GPIO support"
194 This option enables support for GPIOs found on Fintek Super-I/O
195 chips F71882FG and F71889F.
197 To compile this driver as a module, choose M here: the module will
198 be called f7188x-gpio.
201 bool "MOXART GPIO support"
202 depends on ARCH_MOXART
205 Select this option to enable GPIO driver for
206 MOXA ART SoC devices.
210 depends on PPC_MPC52xx
213 bool "MPC512x/MPC8xxx GPIO support"
214 depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \
215 FSL_SOC_BOOKE || PPC_86xx
217 Say Y here if you're going to use hardware that connects to the
218 MPC512x/831x/834x/837x/8572/8610 GPIOs.
221 tristate "Qualcomm MSM GPIO v1"
222 depends on GPIOLIB && ARCH_MSM && (ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50)
224 Say yes here to support the GPIO interface on ARM v6 based
225 Qualcomm MSM chips. Most of the pins on the MSM can be
226 selected for GPIO, and are controlled by this driver.
229 tristate "Qualcomm MSM GPIO v2"
230 depends on GPIOLIB && OF && ARCH_QCOM
232 Say yes here to support the GPIO interface on ARM v7 based
233 Qualcomm MSM chips. Most of the pins on the MSM can be
234 selected for GPIO, and are controlled by this driver.
238 depends on PLAT_ORION
241 select GENERIC_IRQ_CHIP
247 select GENERIC_IRQ_CHIP
253 select GENERIC_IRQ_CHIP
256 tristate "Cavium OCTEON GPIO"
257 depends on GPIOLIB && CAVIUM_OCTEON_SOC
260 Say yes here to support the on-chip GPIO lines on the OCTEON
264 bool "TI OMAP GPIO support" if COMPILE_TEST && !ARCH_OMAP2PLUS
265 default y if ARCH_OMAP
267 select GENERIC_IRQ_CHIP
268 select GPIOLIB_IRQCHIP
270 Say yes here to enable GPIO support for TI OMAP SoCs.
273 bool "PrimeCell PL061 GPIO support"
276 select GPIOLIB_IRQCHIP
278 Say yes here to support the PrimeCell PL061 GPIO device
281 bool "PXA GPIO support"
282 depends on ARCH_PXA || ARCH_MMP
284 Say yes here to support the PXA GPIO device
287 tristate "Renesas R-Car GPIO"
288 depends on ARM && (ARCH_SHMOBILE || COMPILE_TEST)
290 Say yes here to support GPIO on Renesas R-Car SoCs.
294 depends on PLAT_SAMSUNG
296 Legacy GPIO support. Use only for platforms without support for
300 tristate "SMSC SCH311x SuperI/O GPIO"
302 Driver to enable the GPIOs found on SMSC SMSC SCH3112, SCH3114 and
303 SCH3116 "Super I/O" chipsets.
305 To compile this driver as a module, choose M here: the module will
306 be called gpio-sch311x.
308 config GPIO_SPEAR_SPICS
309 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
310 depends on PLAT_SPEAR
311 select GENERIC_IRQ_CHIP
313 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
316 bool "STA2x11/ConneXt GPIO support"
317 depends on MFD_STA2X11
318 select GENERIC_IRQ_CHIP
320 Say yes here to support the STA2x11/ConneXt GPIO device.
321 The GPIO module has 128 GPIO pins with alternate functions.
324 tristate "GPIO based on SYSCON"
325 depends on MFD_SYSCON && OF
327 Say yes here to support GPIO functionality though SYSCON driver.
330 tristate "TS-5500 DIO blocks and compatibles"
331 depends on TS5500 || COMPILE_TEST
333 This driver supports Digital I/O exposed by pin blocks found on some
334 Technologic Systems platforms. It includes, but is not limited to, 3
335 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
339 bool "Toumaz Xenif TZ1090 GPIO support"
340 depends on SOC_TZ1090
341 select GENERIC_IRQ_CHIP
344 Say yes here to support Toumaz Xenif TZ1090 GPIOs.
346 config GPIO_TZ1090_PDC
347 bool "Toumaz Xenif TZ1090 PDC GPIO support"
348 depends on SOC_TZ1090
351 Say yes here to support Toumaz Xenif TZ1090 PDC GPIOs.
355 depends on ARCH_MXC && SOC_VF610
356 select GPIOLIB_IRQCHIP
358 Say yes here to support Vybrid vf610 GPIOs.
361 bool "APM X-Gene GPIO controller support"
362 depends on ARM64 && OF_GPIO
364 This driver is to support the GPIO block within the APM X-Gene SoC
365 platform's generic flash controller. The GPIO pins are muxed with
366 the generic flash controller's address and data pins. Say yes
367 here to enable the GFC GPIO functionality.
370 tristate "Xilinx GPIO support"
371 depends on OF_GPIO && (PPC_OF || MICROBLAZE || ARCH_ZYNQ || ARCH_X86)
373 Say yes here to support the Xilinx FPGA GPIO device
376 tristate "Xilinx Zynq GPIO support"
378 select GPIOLIB_IRQCHIP
380 Say yes here to support Xilinx Zynq GPIO controller.
383 bool "Xtensa GPIO32 support"
385 depends on HAVE_XTENSA_GPIO32
388 Say yes here to support the Xtensa internal GPIO32 IMPWIRE (input)
389 and EXPSTATE (output) ports
392 tristate "NEC VR4100 series General-purpose I/O Uint support"
393 depends on CPU_VR41XX
395 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
398 tristate "Intel SCH/TunnelCreek/Centerton/Quark X1000 GPIO"
399 depends on PCI && X86
403 Say yes here to support GPIO interface on Intel Poulsbo SCH,
404 Intel Tunnel Creek processor, Intel Centerton processor or
405 Intel Quark X1000 SoC.
407 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
408 powered by the core power rail and are turned off during sleep
409 modes (S3 and higher). The remaining four GPIOs are powered by
410 the Intel SCH suspend power supply. These GPIOs remain
411 active during S3. The suspend powered GPIOs can be used to wake the
412 system from the Suspend-to-RAM state.
414 The Intel Tunnel Creek processor has 5 GPIOs powered by the
415 core power rail and 9 from suspend power supply.
417 The Intel Centerton processor has a total of 30 GPIO pins.
418 Twenty-one are powered by the core power rail and 9 from the
419 suspend power supply.
421 The Intel Quark X1000 SoC has 2 GPIOs powered by the core
422 power well and 6 from the suspend power well.
425 tristate "Intel ICH GPIO"
426 depends on PCI && X86
430 Say yes here to support the GPIO functionality of a number of Intel
431 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
432 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
433 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
438 tristate "Intel IOP GPIO"
439 depends on ARM && (ARCH_IOP32X || ARCH_IOP33X)
441 Say yes here to support the GPIO functionality of a number of Intel
447 tristate "VIA VX855/VX875 GPIO"
452 Support access to the VX855/VX875 GPIO lines through the gpio library.
454 This driver provides common support for accessing the device,
455 additional drivers must be enabled in order to use the
456 functionality of the device.
459 bool "GE FPGA based GPIO"
462 Support for common GPIO functionality provided on some GE Single Board
465 This driver provides basic support (configure as input or output, read
466 and write pin state) for GPIO implemented in a number of GE single
469 config GPIO_LYNXPOINT
470 tristate "Intel Lynxpoint GPIO support"
471 depends on ACPI && X86
472 select GPIOLIB_IRQCHIP
474 driver for GPIO functionality on Intel Lynxpoint PCH chipset
475 Requires ACPI device enumeration code to set up a platform device.
478 tristate "Aeroflex Gaisler GRGPIO support"
483 Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
484 VHDL IP core library.
488 select GENERIC_IRQ_CHIP
491 comment "I2C GPIO expanders:"
494 tristate "Wolfson Microelectronics Arizona class devices"
495 depends on MFD_ARIZONA
497 Support for GPIOs on Wolfson Arizona class devices.
499 config GPIO_CRYSTAL_COVE
500 tristate "GPIO support for Crystal Cove PMIC"
501 depends on INTEL_SOC_PMIC
502 select GPIOLIB_IRQCHIP
504 Support for GPIO pins on Crystal Cove PMIC.
506 Say Yes if you have a Intel SoC based tablet with Crystal Cove PMIC
509 This driver can also be built as a module. If so, the module will be
510 called gpio-crystalcove.
513 tristate "TI/National Semiconductor LP3943 GPIO expander"
514 depends on MFD_LP3943
516 GPIO driver for LP3943 MFD.
517 LP3943 can be used as a GPIO expander which provides up to 16 GPIOs.
518 Open drain outputs are required for this usage.
521 tristate "Maxim MAX7300 GPIO expander"
525 GPIO driver for Maxim MAX7300 I2C-based GPIO expander.
528 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
531 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
532 Port Expanders. Each IO port on these chips has a fixed role of
533 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
534 Input and Output (designed by 'P'). The combinations are listed
537 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
538 max7322 (4I4O), max7323 (4P4O)
540 16 bits: max7324 (8I8O), max7325 (8P8O),
541 max7326 (4I12O), max7327 (4P12O)
543 Board setup code must specify the model to use, and the start
544 number for these GPIOs.
546 config GPIO_MAX732X_IRQ
547 bool "Interrupt controller support for MAX732x"
548 depends on GPIO_MAX732X=y
550 Say yes here to enable the max732x to be used as an interrupt
551 controller. It requires the driver to be built in the kernel.
553 config GPIO_MC9S08DZ60
554 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
555 depends on I2C=y && MACH_MX35_3DS
557 Select this to enable the MC9S08DZ60 GPIO driver
560 tristate "PCA95[357]x, PCA9698, TCA64xx, and MAX7310 I/O ports"
563 Say yes here to provide access to several register-oriented
564 SMBus I/O expanders, made mostly by NXP or TI. Compatible
567 4 bits: pca9536, pca9537
569 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
570 pca9556, pca9557, pca9574, tca6408, xra1202
572 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
577 40 bits: pca9505, pca9698
579 config GPIO_PCA953X_IRQ
580 bool "Interrupt controller support for PCA953x"
581 depends on GPIO_PCA953X=y
582 select GPIOLIB_IRQCHIP
584 Say yes here to enable the pca953x to be used as an interrupt
585 controller. It requires the driver to be built in the kernel.
588 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
592 Say yes here to provide access to most "quasi-bidirectional" I2C
593 GPIO expanders used for additional digital outputs or inputs.
594 Most of these parts are from NXP, though TI is a second source for
595 some of them. Compatible models include:
597 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
598 pca9670, pca9672, pca9674, pca9674a,
601 16 bits: pcf8575, pcf8575c, pca8575,
602 pca9671, pca9673, pca9675
604 Your board setup code will need to declare the expanders in
605 use, and assign numbers to the GPIOs they expose. Those GPIOs
606 can then be used from drivers and other kernel code, just like
607 other GPIOs, but only accessible from task contexts.
609 This driver provides an in-kernel interface to those GPIOs using
610 platform-neutral GPIO calls.
613 bool "RICOH RC5T583 GPIO"
614 depends on MFD_RC5T583
616 Select this option to enable GPIO driver for the Ricoh RC5T583
618 This driver provides the support for driving/reading the gpio pins
619 of RC5T583 device through standard gpio library.
622 bool "Semtech SX150x I2C GPIO expander"
624 select GPIOLIB_IRQCHIP
627 Say yes here to provide support for Semtech SX150-series I2C
628 GPIO expanders. Compatible models include:
636 select GPIOLIB_IRQCHIP
638 This enables support for the GPIOs found on the STMPE I/O
642 bool "XWAY STP GPIOs"
645 This enables support for the Serial To Parallel (STP) unit found on
646 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
647 that can be up to 24 bit. This peripheral is aimed at driving leds.
648 Some of the gpios/leds can be auto updated by the soc with dsl and
653 depends on MFD_TC3589X
654 select GPIOLIB_IRQCHIP
656 This enables support for the GPIOs found on the TC3589X
660 tristate "TI TPS65912 GPIO"
661 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
663 This driver supports TPS65912 gpio chip
666 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
667 depends on TWL4030_CORE
669 Say yes here to access the GPIO signals of various multi-function
670 power management chips from Texas Instruments.
673 tristate "TWL6040 GPO"
674 depends on TWL6040_CORE
676 Say yes here to access the GPO signals of twl6040
677 audio chip from Texas Instruments.
680 tristate "WM831x GPIOs"
681 depends on MFD_WM831X
683 Say yes here to access the GPIO signals of WM831x power management
684 chips from Wolfson Microelectronics.
687 tristate "WM8350 GPIOs"
688 depends on MFD_WM8350
690 Say yes here to access the GPIO signals of WM8350 power management
691 chips from Wolfson Microelectronics.
694 tristate "WM8994 GPIOs"
695 depends on MFD_WM8994
697 Say yes here to access the GPIO signals of WM8994 audio hub
698 CODECs from Wolfson Microelectronics.
701 tristate "GPIO Support for ADP5520 PMIC"
702 depends on PMIC_ADP5520
704 This option enables support for on-chip GPIO found
705 on Analog Devices ADP5520 PMICs.
708 tristate "ADP5588 I2C GPIO expander"
711 This option enables support for 18 GPIOs found
712 on Analog Devices ADP5588 GPIO Expanders.
714 config GPIO_ADP5588_IRQ
715 bool "Interrupt controller support for ADP5588"
716 depends on GPIO_ADP5588=y
718 Say yes here to enable the adp5588 to be used as an interrupt
719 controller. It requires the driver to be built in the kernel.
722 tristate "Avionic Design N-bit GPIO expander"
723 depends on I2C && OF_GPIO
724 select GPIOLIB_IRQCHIP
726 This option enables support for N GPIOs found on Avionic Design
727 I2C GPIO expanders. The register space will be extended by powers
728 of two, so the controller will need to accommodate for that. For
729 example: if a controller provides 48 pins, 6 registers will be
730 enough to represent all pins, but the driver will assume a
731 register layout for 64 pins (8 registers).
733 comment "PCI GPIO expanders:"
736 tristate "AMD CS5535/CS5536 GPIO support"
737 depends on MFD_CS5535
739 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
740 can be used for quite a number of things. The CS5535/6 is found on
741 AMD Geode and Lemote Yeeloong devices.
746 tristate "BT8XX GPIO abuser"
747 depends on PCI && VIDEO_BT848=n
749 The BT8xx frame grabber chip has 24 GPIO pins that can be abused
750 as a cheap PCI GPIO card.
752 This chip can be found on Miro, Hauppauge and STB TV-cards.
754 The card needs to be physically altered for using it as a
755 GPIO card. For more information on how to build a GPIO card
756 from a BT8xx TV card, see the documentation file at
757 Documentation/bt8xxgpio.txt
762 tristate "AMD 8111 GPIO driver"
765 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
767 Note, that usually system firmware/ACPI handles GPIO pins on their
768 own and users might easily break their systems with uncarefull usage
773 config GPIO_INTEL_MID
774 bool "Intel Mid GPIO support"
775 depends on PCI && X86
776 select GPIOLIB_IRQCHIP
778 Say Y here to support Intel Mid GPIO.
781 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
782 depends on PCI && (X86_32 || COMPILE_TEST)
783 select GENERIC_IRQ_CHIP
785 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
786 which is an IOH(Input/Output Hub) for x86 embedded processor.
787 This driver can access PCH GPIO device.
789 This driver also can be used for LAPIS Semiconductor IOH(Input/
790 Output Hub), ML7223 and ML7831.
791 ML7223 IOH is for MP(Media Phone) use.
792 ML7831 IOH is for general purpose use.
793 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
794 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
797 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
799 select GENERIC_IRQ_CHIP
801 ML7213 is companion chip for Intel Atom E6xx series.
802 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
803 Hub) which is for IVI(In-Vehicle Infotainment) use.
804 This driver can access the IOH's GPIO device.
806 config GPIO_SODAVILLE
807 bool "Intel Sodaville GPIO support"
808 depends on X86 && PCI && OF
810 select GENERIC_IRQ_CHIP
812 Say Y here to support Intel Sodaville GPIO.
814 config GPIO_TIMBERDALE
815 bool "Support for timberdale GPIO IP"
816 depends on MFD_TIMBERDALE
818 Add support for the GPIO IP in the timberdale FPGA.
821 tristate "RDC R-321x GPIO support"
826 Support for the RDC R321x SoC GPIOs over southbridge
827 PCI configuration space.
829 comment "SPI GPIO expanders:"
832 tristate "Maxim MAX7301 GPIO expander"
833 depends on SPI_MASTER
836 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
839 tristate "Microchip MCP23xxx I/O expander"
840 depends on (SPI_MASTER && !I2C) || I2C
842 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
844 This provides a GPIO interface supporting inputs and outputs.
845 The I2C versions of the chips can be used as interrupt-controller.
848 tristate "Freescale MC33880 high-side/low-side switch"
849 depends on SPI_MASTER
851 SPI driver for Freescale MC33880 high-side/low-side switch.
852 This provides GPIO interface supporting inputs and outputs.
855 tristate "74x164 serial-in/parallel-out 8-bits shift register"
856 depends on SPI_MASTER && OF
858 Driver for 74x164 compatible serial-in/parallel-out 8-outputs
859 shift registers. This driver can be used to provide access
860 to more gpio outputs.
862 comment "AC97 GPIO expanders:"
865 tristate "Philips UCB1400 GPIO"
866 depends on UCB1400_CORE
868 This enables support for the Philips UCB1400 GPIO pins.
869 The UCB1400 is an AC97 audio codec.
871 comment "LPC GPIO expanders:"
874 tristate "Kontron ETX / COMexpress GPIO"
875 depends on MFD_KEMPLD
877 This enables support for the PLD GPIO interface on some Kontron ETX
878 and COMexpress (ETXexpress) modules.
880 This driver can also be built as a module. If so, the module will be
883 comment "MODULbus GPIO expanders:"
886 tristate "Janz VMOD-TTL Digital IO Module"
887 depends on MFD_JANZ_CMODIO
889 This enables support for the Janz VMOD-TTL Digital IO module.
890 This driver provides support for driving the pins in output
891 mode only. Input mode is not supported.
894 bool "TI PALMAS series PMICs GPIO"
895 depends on MFD_PALMAS
897 Select this option to enable GPIO driver for the TI PALMAS
902 depends on MFD_TPS6586X
904 Select this option to enable GPIO driver for the TPS6586X
909 depends on MFD_TPS65910
911 Select this option to enable GPIO driver for the TPS65910
915 bool "Intel MSIC mixed signal gpio support"
916 depends on MFD_INTEL_MSIC
918 Enable support for GPIO on intel MSIC controllers found in
922 bool "Broadcom Kona GPIO"
923 depends on OF_GPIO && (ARCH_BCM_MOBILE || COMPILE_TEST)
925 Turn on GPIO support for Broadcom "Kona" chips.
927 comment "USB GPIO expanders:"
929 config GPIO_VIPERBOARD
930 tristate "Viperboard GPIO a & b support"
931 depends on MFD_VIPERBOARD && USB
933 Say yes here to access the GPIO signals of Nano River
934 Technologies Viperboard. There are two GPIO chips on the
935 board: gpioa and gpiob.
936 See viperboard API specification and Nano
937 River Tech's viperboard.h for detailed meaning
938 of the module parameters.
941 tristate "Diolan DLN2 GPIO support"
943 select GPIOLIB_IRQCHIP
946 Select this option to enable GPIO driver for the Diolan DLN2
949 This driver can also be built as a module. If so, the module
950 will be called gpio-dln2.