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)
289 select GPIOLIB_IRQCHIP
291 Say yes here to support GPIO on Renesas R-Car SoCs.
295 depends on PLAT_SAMSUNG
297 Legacy GPIO support. Use only for platforms without support for
301 tristate "SMSC SCH311x SuperI/O GPIO"
303 Driver to enable the GPIOs found on SMSC SMSC SCH3112, SCH3114 and
304 SCH3116 "Super I/O" chipsets.
306 To compile this driver as a module, choose M here: the module will
307 be called gpio-sch311x.
309 config GPIO_SPEAR_SPICS
310 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
311 depends on PLAT_SPEAR
312 select GENERIC_IRQ_CHIP
314 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
317 bool "STA2x11/ConneXt GPIO support"
318 depends on MFD_STA2X11
319 select GENERIC_IRQ_CHIP
321 Say yes here to support the STA2x11/ConneXt GPIO device.
322 The GPIO module has 128 GPIO pins with alternate functions.
325 tristate "GPIO based on SYSCON"
326 depends on MFD_SYSCON && OF
328 Say yes here to support GPIO functionality though SYSCON driver.
331 tristate "TS-5500 DIO blocks and compatibles"
332 depends on TS5500 || COMPILE_TEST
334 This driver supports Digital I/O exposed by pin blocks found on some
335 Technologic Systems platforms. It includes, but is not limited to, 3
336 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
340 bool "Toumaz Xenif TZ1090 GPIO support"
341 depends on SOC_TZ1090
342 select GENERIC_IRQ_CHIP
345 Say yes here to support Toumaz Xenif TZ1090 GPIOs.
347 config GPIO_TZ1090_PDC
348 bool "Toumaz Xenif TZ1090 PDC GPIO support"
349 depends on SOC_TZ1090
352 Say yes here to support Toumaz Xenif TZ1090 PDC GPIOs.
356 depends on ARCH_MXC && SOC_VF610
357 select GPIOLIB_IRQCHIP
359 Say yes here to support Vybrid vf610 GPIOs.
362 bool "APM X-Gene GPIO controller support"
363 depends on ARM64 && OF_GPIO
365 This driver is to support the GPIO block within the APM X-Gene SoC
366 platform's generic flash controller. The GPIO pins are muxed with
367 the generic flash controller's address and data pins. Say yes
368 here to enable the GFC GPIO functionality.
371 tristate "Xilinx GPIO support"
372 depends on OF_GPIO && (PPC_OF || MICROBLAZE || ARCH_ZYNQ || X86)
374 Say yes here to support the Xilinx FPGA GPIO device
377 tristate "Xilinx Zynq GPIO support"
379 select GPIOLIB_IRQCHIP
381 Say yes here to support Xilinx Zynq GPIO controller.
384 bool "Xtensa GPIO32 support"
386 depends on HAVE_XTENSA_GPIO32
389 Say yes here to support the Xtensa internal GPIO32 IMPWIRE (input)
390 and EXPSTATE (output) ports
393 tristate "NEC VR4100 series General-purpose I/O Uint support"
394 depends on CPU_VR41XX
396 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
399 tristate "Intel SCH/TunnelCreek/Centerton/Quark X1000 GPIO"
400 depends on PCI && X86
404 Say yes here to support GPIO interface on Intel Poulsbo SCH,
405 Intel Tunnel Creek processor, Intel Centerton processor or
406 Intel Quark X1000 SoC.
408 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
409 powered by the core power rail and are turned off during sleep
410 modes (S3 and higher). The remaining four GPIOs are powered by
411 the Intel SCH suspend power supply. These GPIOs remain
412 active during S3. The suspend powered GPIOs can be used to wake the
413 system from the Suspend-to-RAM state.
415 The Intel Tunnel Creek processor has 5 GPIOs powered by the
416 core power rail and 9 from suspend power supply.
418 The Intel Centerton processor has a total of 30 GPIO pins.
419 Twenty-one are powered by the core power rail and 9 from the
420 suspend power supply.
422 The Intel Quark X1000 SoC has 2 GPIOs powered by the core
423 power well and 6 from the suspend power well.
426 tristate "Intel ICH GPIO"
427 depends on PCI && X86
431 Say yes here to support the GPIO functionality of a number of Intel
432 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
433 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
434 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
439 tristate "Intel IOP GPIO"
440 depends on ARM && (ARCH_IOP32X || ARCH_IOP33X)
442 Say yes here to support the GPIO functionality of a number of Intel
448 tristate "VIA VX855/VX875 GPIO"
453 Support access to the VX855/VX875 GPIO lines through the gpio library.
455 This driver provides common support for accessing the device,
456 additional drivers must be enabled in order to use the
457 functionality of the device.
460 bool "GE FPGA based GPIO"
464 Support for common GPIO functionality provided on some GE Single Board
467 This driver provides basic support (configure as input or output, read
468 and write pin state) for GPIO implemented in a number of GE single
471 config GPIO_LYNXPOINT
472 tristate "Intel Lynxpoint GPIO support"
473 depends on ACPI && X86
474 select GPIOLIB_IRQCHIP
476 driver for GPIO functionality on Intel Lynxpoint PCH chipset
477 Requires ACPI device enumeration code to set up a platform device.
480 tristate "Aeroflex Gaisler GRGPIO support"
485 Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
486 VHDL IP core library.
490 select GENERIC_IRQ_CHIP
493 comment "I2C GPIO expanders:"
496 tristate "Wolfson Microelectronics Arizona class devices"
497 depends on MFD_ARIZONA
499 Support for GPIOs on Wolfson Arizona class devices.
501 config GPIO_CRYSTAL_COVE
502 tristate "GPIO support for Crystal Cove PMIC"
503 depends on INTEL_SOC_PMIC
504 select GPIOLIB_IRQCHIP
506 Support for GPIO pins on Crystal Cove PMIC.
508 Say Yes if you have a Intel SoC based tablet with Crystal Cove PMIC
511 This driver can also be built as a module. If so, the module will be
512 called gpio-crystalcove.
515 tristate "TI/National Semiconductor LP3943 GPIO expander"
516 depends on MFD_LP3943
518 GPIO driver for LP3943 MFD.
519 LP3943 can be used as a GPIO expander which provides up to 16 GPIOs.
520 Open drain outputs are required for this usage.
523 tristate "Maxim MAX7300 GPIO expander"
527 GPIO driver for Maxim MAX7300 I2C-based GPIO expander.
530 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
534 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
535 Port Expanders. Each IO port on these chips has a fixed role of
536 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
537 Input and Output (designed by 'P'). The combinations are listed
540 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
541 max7322 (4I4O), max7323 (4P4O)
543 16 bits: max7324 (8I8O), max7325 (8P8O),
544 max7326 (4I12O), max7327 (4P12O)
546 Board setup code must specify the model to use, and the start
547 number for these GPIOs.
549 config GPIO_MAX732X_IRQ
550 bool "Interrupt controller support for MAX732x"
551 depends on GPIO_MAX732X=y
553 Say yes here to enable the max732x to be used as an interrupt
554 controller. It requires the driver to be built in the kernel.
556 config GPIO_MC9S08DZ60
557 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
558 depends on I2C=y && MACH_MX35_3DS
560 Select this to enable the MC9S08DZ60 GPIO driver
563 tristate "PCA95[357]x, PCA9698, TCA64xx, and MAX7310 I/O ports"
566 Say yes here to provide access to several register-oriented
567 SMBus I/O expanders, made mostly by NXP or TI. Compatible
570 4 bits: pca9536, pca9537
572 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
573 pca9556, pca9557, pca9574, tca6408, xra1202
575 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
580 40 bits: pca9505, pca9698
582 config GPIO_PCA953X_IRQ
583 bool "Interrupt controller support for PCA953x"
584 depends on GPIO_PCA953X=y
585 select GPIOLIB_IRQCHIP
587 Say yes here to enable the pca953x to be used as an interrupt
588 controller. It requires the driver to be built in the kernel.
591 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
595 Say yes here to provide access to most "quasi-bidirectional" I2C
596 GPIO expanders used for additional digital outputs or inputs.
597 Most of these parts are from NXP, though TI is a second source for
598 some of them. Compatible models include:
600 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
601 pca9670, pca9672, pca9674, pca9674a,
604 16 bits: pcf8575, pcf8575c, pca8575,
605 pca9671, pca9673, pca9675
607 Your board setup code will need to declare the expanders in
608 use, and assign numbers to the GPIOs they expose. Those GPIOs
609 can then be used from drivers and other kernel code, just like
610 other GPIOs, but only accessible from task contexts.
612 This driver provides an in-kernel interface to those GPIOs using
613 platform-neutral GPIO calls.
616 bool "RICOH RC5T583 GPIO"
617 depends on MFD_RC5T583
619 Select this option to enable GPIO driver for the Ricoh RC5T583
621 This driver provides the support for driving/reading the gpio pins
622 of RC5T583 device through standard gpio library.
625 bool "Semtech SX150x I2C GPIO expander"
627 select GPIOLIB_IRQCHIP
630 Say yes here to provide support for Semtech SX150-series I2C
631 GPIO expanders. Compatible models include:
639 select GPIOLIB_IRQCHIP
641 This enables support for the GPIOs found on the STMPE I/O
645 bool "XWAY STP GPIOs"
648 This enables support for the Serial To Parallel (STP) unit found on
649 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
650 that can be up to 24 bit. This peripheral is aimed at driving leds.
651 Some of the gpios/leds can be auto updated by the soc with dsl and
656 depends on MFD_TC3589X
657 select GPIOLIB_IRQCHIP
659 This enables support for the GPIOs found on the TC3589X
663 tristate "TI TPS65912 GPIO"
664 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
666 This driver supports TPS65912 gpio chip
669 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
670 depends on TWL4030_CORE
672 Say yes here to access the GPIO signals of various multi-function
673 power management chips from Texas Instruments.
676 tristate "TWL6040 GPO"
677 depends on TWL6040_CORE
679 Say yes here to access the GPO signals of twl6040
680 audio chip from Texas Instruments.
683 tristate "WM831x GPIOs"
684 depends on MFD_WM831X
686 Say yes here to access the GPIO signals of WM831x power management
687 chips from Wolfson Microelectronics.
690 tristate "WM8350 GPIOs"
691 depends on MFD_WM8350
693 Say yes here to access the GPIO signals of WM8350 power management
694 chips from Wolfson Microelectronics.
697 tristate "WM8994 GPIOs"
698 depends on MFD_WM8994
700 Say yes here to access the GPIO signals of WM8994 audio hub
701 CODECs from Wolfson Microelectronics.
704 tristate "GPIO Support for ADP5520 PMIC"
705 depends on PMIC_ADP5520
707 This option enables support for on-chip GPIO found
708 on Analog Devices ADP5520 PMICs.
711 tristate "ADP5588 I2C GPIO expander"
714 This option enables support for 18 GPIOs found
715 on Analog Devices ADP5588 GPIO Expanders.
717 config GPIO_ADP5588_IRQ
718 bool "Interrupt controller support for ADP5588"
719 depends on GPIO_ADP5588=y
721 Say yes here to enable the adp5588 to be used as an interrupt
722 controller. It requires the driver to be built in the kernel.
725 tristate "Avionic Design N-bit GPIO expander"
726 depends on I2C && OF_GPIO
727 select GPIOLIB_IRQCHIP
729 This option enables support for N GPIOs found on Avionic Design
730 I2C GPIO expanders. The register space will be extended by powers
731 of two, so the controller will need to accommodate for that. For
732 example: if a controller provides 48 pins, 6 registers will be
733 enough to represent all pins, but the driver will assume a
734 register layout for 64 pins (8 registers).
736 comment "PCI GPIO expanders:"
739 tristate "AMD CS5535/CS5536 GPIO support"
740 depends on MFD_CS5535
742 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
743 can be used for quite a number of things. The CS5535/6 is found on
744 AMD Geode and Lemote Yeeloong devices.
749 tristate "BT8XX GPIO abuser"
750 depends on PCI && VIDEO_BT848=n
752 The BT8xx frame grabber chip has 24 GPIO pins that can be abused
753 as a cheap PCI GPIO card.
755 This chip can be found on Miro, Hauppauge and STB TV-cards.
757 The card needs to be physically altered for using it as a
758 GPIO card. For more information on how to build a GPIO card
759 from a BT8xx TV card, see the documentation file at
760 Documentation/bt8xxgpio.txt
765 tristate "AMD 8111 GPIO driver"
768 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
770 Note, that usually system firmware/ACPI handles GPIO pins on their
771 own and users might easily break their systems with uncarefull usage
776 config GPIO_INTEL_MID
777 bool "Intel Mid GPIO support"
778 depends on PCI && X86
779 select GPIOLIB_IRQCHIP
781 Say Y here to support Intel Mid GPIO.
784 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
785 depends on PCI && (X86_32 || COMPILE_TEST)
786 select GENERIC_IRQ_CHIP
788 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
789 which is an IOH(Input/Output Hub) for x86 embedded processor.
790 This driver can access PCH GPIO device.
792 This driver also can be used for LAPIS Semiconductor IOH(Input/
793 Output Hub), ML7223 and ML7831.
794 ML7223 IOH is for MP(Media Phone) use.
795 ML7831 IOH is for general purpose use.
796 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
797 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
800 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
802 select GENERIC_IRQ_CHIP
804 ML7213 is companion chip for Intel Atom E6xx series.
805 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
806 Hub) which is for IVI(In-Vehicle Infotainment) use.
807 This driver can access the IOH's GPIO device.
809 config GPIO_SODAVILLE
810 bool "Intel Sodaville GPIO support"
811 depends on X86 && PCI && OF
813 select GENERIC_IRQ_CHIP
815 Say Y here to support Intel Sodaville GPIO.
817 config GPIO_TIMBERDALE
818 bool "Support for timberdale GPIO IP"
819 depends on MFD_TIMBERDALE
821 Add support for the GPIO IP in the timberdale FPGA.
824 tristate "RDC R-321x GPIO support"
829 Support for the RDC R321x SoC GPIOs over southbridge
830 PCI configuration space.
832 comment "SPI GPIO expanders:"
835 tristate "Maxim MAX7301 GPIO expander"
836 depends on SPI_MASTER
839 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
842 tristate "Microchip MCP23xxx I/O expander"
843 depends on (SPI_MASTER && !I2C) || I2C
845 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
847 This provides a GPIO interface supporting inputs and outputs.
848 The I2C versions of the chips can be used as interrupt-controller.
851 tristate "Freescale MC33880 high-side/low-side switch"
852 depends on SPI_MASTER
854 SPI driver for Freescale MC33880 high-side/low-side switch.
855 This provides GPIO interface supporting inputs and outputs.
858 tristate "74x164 serial-in/parallel-out 8-bits shift register"
859 depends on SPI_MASTER && OF
861 Driver for 74x164 compatible serial-in/parallel-out 8-outputs
862 shift registers. This driver can be used to provide access
863 to more gpio outputs.
865 comment "AC97 GPIO expanders:"
868 tristate "Philips UCB1400 GPIO"
869 depends on UCB1400_CORE
871 This enables support for the Philips UCB1400 GPIO pins.
872 The UCB1400 is an AC97 audio codec.
874 comment "LPC GPIO expanders:"
877 tristate "Kontron ETX / COMexpress GPIO"
878 depends on MFD_KEMPLD
880 This enables support for the PLD GPIO interface on some Kontron ETX
881 and COMexpress (ETXexpress) modules.
883 This driver can also be built as a module. If so, the module will be
886 comment "MODULbus GPIO expanders:"
889 tristate "Janz VMOD-TTL Digital IO Module"
890 depends on MFD_JANZ_CMODIO
892 This enables support for the Janz VMOD-TTL Digital IO module.
893 This driver provides support for driving the pins in output
894 mode only. Input mode is not supported.
897 bool "TI PALMAS series PMICs GPIO"
898 depends on MFD_PALMAS
900 Select this option to enable GPIO driver for the TI PALMAS
905 depends on MFD_TPS6586X
907 Select this option to enable GPIO driver for the TPS6586X
912 depends on MFD_TPS65910
914 Select this option to enable GPIO driver for the TPS65910
918 bool "Intel MSIC mixed signal gpio support"
919 depends on MFD_INTEL_MSIC
921 Enable support for GPIO on intel MSIC controllers found in
925 bool "Broadcom Kona GPIO"
926 depends on OF_GPIO && (ARCH_BCM_MOBILE || COMPILE_TEST)
928 Turn on GPIO support for Broadcom "Kona" chips.
930 comment "USB GPIO expanders:"
932 config GPIO_VIPERBOARD
933 tristate "Viperboard GPIO a & b support"
934 depends on MFD_VIPERBOARD && USB
936 Say yes here to access the GPIO signals of Nano River
937 Technologies Viperboard. There are two GPIO chips on the
938 board: gpioa and gpiob.
939 See viperboard API specification and Nano
940 River Tech's viperboard.h for detailed meaning
941 of the module parameters.
944 tristate "Diolan DLN2 GPIO support"
946 select GPIOLIB_IRQCHIP
949 Select this option to enable GPIO driver for the Diolan DLN2
952 This driver can also be built as a module. If so, the module
953 will be called gpio-dln2.