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.
59 bool "Debug GPIO calls"
60 depends on DEBUG_KERNEL
62 Say Y here to add some extra checks and diagnostics to GPIO calls.
63 These checks help ensure that GPIOs have been properly initialized
64 before they are used, and that sleeping calls are not made from
65 non-sleeping contexts. They can make bitbanged serial protocols
66 slower. The diagnostics help catch the type of setup errors
67 that are most common when setting up new platforms or boards.
70 bool "/sys/class/gpio/... (sysfs interface)"
73 Say Y here to add a sysfs interface for GPIOs.
75 This is mostly useful to work around omissions in a system's
76 kernel support. Those are common in custom and semicustom
77 hardware assembled using standard kernels with a minimum of
78 custom patches. In those cases, userspace code may import
79 a given GPIO from the kernel, if no kernel driver requested it.
81 Kernel drivers may also request that a particular GPIO be
82 exported to userspace; this can be useful when debugging.
87 # put drivers in the right section, in alphabetical order
90 tristate "Dialog DA9052 GPIO"
91 depends on PMIC_DA9052
93 Say yes here to enable the GPIO driver for the DA9052 chip.
96 tristate "Dialog Semiconductor DA9055 GPIO"
99 Say yes here to enable the GPIO driver for the DA9055 chip.
101 The Dialog DA9055 PMIC chip has 3 GPIO pins that can be
102 be controller by this driver.
104 If driver is built as a module it will be called gpio-da9055.
109 comment "Memory mapped GPIO drivers:"
112 tristate "CLPS711X GPIO support"
113 depends on ARCH_CLPS711X || COMPILE_TEST
116 Say yes here to support GPIO on CLPS711X SoCs.
119 bool "TI Davinci/Keystone GPIO support"
120 default y if ARCH_DAVINCI
121 depends on ARM && (ARCH_DAVINCI || ARCH_KEYSTONE)
123 Say yes here to enable GPIO support for TI Davinci/Keystone SoCs.
125 config GPIO_GENERIC_PLATFORM
126 tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
129 Say yes here to support basic platform_device memory-mapped GPIO controllers.
132 tristate "IT8761E GPIO support"
133 depends on X86 # unconditional access to IO space.
135 Say yes here to support GPIO functionality of IT8761E super I/O chip.
138 tristate "Emma Mobile GPIO"
139 depends on ARM && OF_GPIO
141 Say yes here to support GPIO on Renesas Emma Mobile SoCs.
145 depends on ARCH_EP93XX
148 config GPIO_MM_LANTIQ
149 bool "Lantiq Memory mapped GPIOs"
150 depends on LANTIQ && SOC_XWAY
152 This enables support for memory mapped GPIOs on the External Bus Unit
153 (EBU) found on Lantiq SoCs. The gpios are output only as they are
154 created by attaching a 16bit latch to the bus.
157 tristate "F71882FG and F71889F GPIO support"
160 This option enables support for GPIOs found on Fintek Super-I/O
161 chips F71882FG and F71889F.
163 To compile this driver as a module, choose M here: the module will
164 be called f7188x-gpio.
167 bool "MOXART GPIO support"
168 depends on ARCH_MOXART
170 Select this option to enable GPIO driver for
171 MOXA ART SoC devices.
175 depends on PPC_MPC52xx
178 bool "MPC512x/MPC8xxx GPIO support"
179 depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \
180 FSL_SOC_BOOKE || PPC_86xx
182 Say Y here if you're going to use hardware that connects to the
183 MPC512x/831x/834x/837x/8572/8610 GPIOs.
186 tristate "Qualcomm MSM GPIO v1"
187 depends on GPIOLIB && ARCH_MSM && (ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50)
189 Say yes here to support the GPIO interface on ARM v6 based
190 Qualcomm MSM chips. Most of the pins on the MSM can be
191 selected for GPIO, and are controlled by this driver.
194 tristate "Qualcomm MSM GPIO v2"
195 depends on GPIOLIB && OF && ARCH_MSM
197 Say yes here to support the GPIO interface on ARM v7 based
198 Qualcomm MSM chips. Most of the pins on the MSM can be
199 selected for GPIO, and are controlled by this driver.
203 depends on PLAT_ORION
206 select GENERIC_IRQ_CHIP
212 select GENERIC_IRQ_CHIP
218 select GENERIC_IRQ_CHIP
221 tristate "Cavium OCTEON GPIO"
222 depends on GPIOLIB && CAVIUM_OCTEON_SOC
225 Say yes here to support the on-chip GPIO lines on the OCTEON
229 bool "PrimeCell PL061 GPIO support"
231 select GENERIC_IRQ_CHIP
233 Say yes here to support the PrimeCell PL061 GPIO device
236 bool "PXA GPIO support"
237 depends on ARCH_PXA || ARCH_MMP
239 Say yes here to support the PXA GPIO device
242 tristate "Renesas R-Car GPIO"
245 Say yes here to support GPIO on Renesas R-Car SoCs.
249 depends on PLAT_SAMSUNG
251 Legacy GPIO support. Use only for platforms without support for
255 tristate "SMSC SCH311x SuperI/O GPIO"
257 Driver to enable the GPIOs found on SMSC SMSC SCH3112, SCH3114 and
258 SCH3116 "Super I/O" chipsets.
260 To compile this driver as a module, choose M here: the module will
261 be called gpio-sch311x.
263 config GPIO_SPEAR_SPICS
264 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
265 depends on PLAT_SPEAR
266 select GENERIC_IRQ_CHIP
268 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
271 bool "STA2x11/ConneXt GPIO support"
272 depends on MFD_STA2X11
273 select GENERIC_IRQ_CHIP
275 Say yes here to support the STA2x11/ConneXt GPIO device.
276 The GPIO module has 128 GPIO pins with alternate functions.
279 tristate "TS-5500 DIO blocks and compatibles"
281 This driver supports Digital I/O exposed by pin blocks found on some
282 Technologic Systems platforms. It includes, but is not limited to, 3
283 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
287 bool "Toumaz Xenif TZ1090 GPIO support"
288 depends on SOC_TZ1090
289 select GENERIC_IRQ_CHIP
292 Say yes here to support Toumaz Xenif TZ1090 GPIOs.
294 config GPIO_TZ1090_PDC
295 bool "Toumaz Xenif TZ1090 PDC GPIO support"
296 depends on SOC_TZ1090
299 Say yes here to support Toumaz Xenif TZ1090 PDC GPIOs.
302 bool "Xilinx GPIO support"
303 depends on PPC_OF || MICROBLAZE || ARCH_ZYNQ
305 Say yes here to support the Xilinx FPGA GPIO device
308 bool "Xtensa GPIO32 support"
310 depends on HAVE_XTENSA_GPIO32
313 Say yes here to support the Xtensa internal GPIO32 IMPWIRE (input)
314 and EXPSTATE (output) ports
317 tristate "NEC VR4100 series General-purpose I/O Uint support"
318 depends on CPU_VR41XX
320 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
323 tristate "Intel SCH/TunnelCreek/Centerton GPIO"
324 depends on PCI && X86
328 Say yes here to support GPIO interface on Intel Poulsbo SCH,
329 Intel Tunnel Creek processor or Intel Centerton processor.
330 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
331 powered by the core power rail and are turned off during sleep
332 modes (S3 and higher). The remaining four GPIOs are powered by
333 the Intel SCH suspend power supply. These GPIOs remain
334 active during S3. The suspend powered GPIOs can be used to wake the
335 system from the Suspend-to-RAM state.
336 The Intel Tunnel Creek processor has 5 GPIOs powered by the
337 core power rail and 9 from suspend power supply.
338 The Intel Centerton processor has a total of 30 GPIO pins.
339 Twenty-one are powered by the core power rail and 9 from the
340 suspend power supply.
343 tristate "Intel ICH GPIO"
344 depends on PCI && X86
348 Say yes here to support the GPIO functionality of a number of Intel
349 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
350 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
351 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
356 tristate "Intel IOP GPIO"
357 depends on ARM && (ARCH_IOP32X || ARCH_IOP33X)
359 Say yes here to support the GPIO functionality of a number of Intel
365 tristate "VIA VX855/VX875 GPIO"
370 Support access to the VX855/VX875 GPIO lines through the gpio library.
372 This driver provides common support for accessing the device,
373 additional drivers must be enabled in order to use the
374 functionality of the device.
377 bool "GE FPGA based GPIO"
380 Support for common GPIO functionality provided on some GE Single Board
383 This driver provides basic support (configure as input or output, read
384 and write pin state) for GPIO implemented in a number of GE single
387 config GPIO_LYNXPOINT
388 tristate "Intel Lynxpoint GPIO support"
389 depends on ACPI && X86
392 driver for GPIO functionality on Intel Lynxpoint PCH chipset
393 Requires ACPI device enumeration code to set up a platform device.
396 tristate "Aeroflex Gaisler GRGPIO support"
401 Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
402 VHDL IP core library.
408 comment "I2C GPIO expanders:"
411 tristate "Wolfson Microelectronics Arizona class devices"
412 depends on MFD_ARIZONA
414 Support for GPIOs on Wolfson Arizona class devices.
417 tristate "TI/National Semiconductor LP3943 GPIO expander"
418 depends on MFD_LP3943
420 GPIO driver for LP3943 MFD.
421 LP3943 can be used as a GPIO expander which provides up to 16 GPIOs.
422 Open drain outputs are required for this usage.
425 tristate "Maxim MAX7300 GPIO expander"
429 GPIO driver for Maxim MAX7300 I2C-based GPIO expander.
432 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
435 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
436 Port Expanders. Each IO port on these chips has a fixed role of
437 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
438 Input and Output (designed by 'P'). The combinations are listed
441 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
442 max7322 (4I4O), max7323 (4P4O)
444 16 bits: max7324 (8I8O), max7325 (8P8O),
445 max7326 (4I12O), max7327 (4P12O)
447 Board setup code must specify the model to use, and the start
448 number for these GPIOs.
450 config GPIO_MAX732X_IRQ
451 bool "Interrupt controller support for MAX732x"
452 depends on GPIO_MAX732X=y
454 Say yes here to enable the max732x to be used as an interrupt
455 controller. It requires the driver to be built in the kernel.
457 config GPIO_MC9S08DZ60
458 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
459 depends on I2C=y && MACH_MX35_3DS
461 Select this to enable the MC9S08DZ60 GPIO driver
464 tristate "PCA953x, PCA955x, PCA957x, TCA64xx, and MAX7310 I/O ports"
467 Say yes here to provide access to several register-oriented
468 SMBus I/O expanders, made mostly by NXP or TI. Compatible
471 4 bits: pca9536, pca9537
473 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
474 pca9556, pca9557, pca9574, tca6408
476 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
479 config GPIO_PCA953X_IRQ
480 bool "Interrupt controller support for PCA953x"
481 depends on GPIO_PCA953X=y
483 Say yes here to enable the pca953x to be used as an interrupt
484 controller. It requires the driver to be built in the kernel.
487 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
491 Say yes here to provide access to most "quasi-bidirectional" I2C
492 GPIO expanders used for additional digital outputs or inputs.
493 Most of these parts are from NXP, though TI is a second source for
494 some of them. Compatible models include:
496 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
497 pca9670, pca9672, pca9674, pca9674a,
500 16 bits: pcf8575, pcf8575c, pca8575,
501 pca9671, pca9673, pca9675
503 Your board setup code will need to declare the expanders in
504 use, and assign numbers to the GPIOs they expose. Those GPIOs
505 can then be used from drivers and other kernel code, just like
506 other GPIOs, but only accessible from task contexts.
508 This driver provides an in-kernel interface to those GPIOs using
509 platform-neutral GPIO calls.
512 bool "RICOH RC5T583 GPIO"
513 depends on MFD_RC5T583
515 Select this option to enable GPIO driver for the Ricoh RC5T583
517 This driver provides the support for driving/reading the gpio pins
518 of RC5T583 device through standard gpio library.
521 bool "Semtech SX150x I2C GPIO expander"
525 Say yes here to provide support for Semtech SX150-series I2C
526 GPIO expanders. Compatible models include:
535 This enables support for the GPIOs found on the STMPE I/O
539 bool "XWAY STP GPIOs"
542 This enables support for the Serial To Parallel (STP) unit found on
543 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
544 that can be up to 24 bit. This peripheral is aimed at driving leds.
545 Some of the gpios/leds can be auto updated by the soc with dsl and
550 depends on MFD_TC3589X
552 This enables support for the GPIOs found on the TC3589X
556 tristate "TI TPS65912 GPIO"
557 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
559 This driver supports TPS65912 gpio chip
562 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
563 depends on TWL4030_CORE
565 Say yes here to access the GPIO signals of various multi-function
566 power management chips from Texas Instruments.
569 tristate "TWL6040 GPO"
570 depends on TWL6040_CORE
572 Say yes here to access the GPO signals of twl6040
573 audio chip from Texas Instruments.
576 tristate "WM831x GPIOs"
577 depends on MFD_WM831X
579 Say yes here to access the GPIO signals of WM831x power management
580 chips from Wolfson Microelectronics.
583 tristate "WM8350 GPIOs"
584 depends on MFD_WM8350
586 Say yes here to access the GPIO signals of WM8350 power management
587 chips from Wolfson Microelectronics.
590 tristate "WM8994 GPIOs"
591 depends on MFD_WM8994
593 Say yes here to access the GPIO signals of WM8994 audio hub
594 CODECs from Wolfson Microelectronics.
597 tristate "GPIO Support for ADP5520 PMIC"
598 depends on PMIC_ADP5520
600 This option enables support for on-chip GPIO found
601 on Analog Devices ADP5520 PMICs.
604 tristate "ADP5588 I2C GPIO expander"
607 This option enables support for 18 GPIOs found
608 on Analog Devices ADP5588 GPIO Expanders.
610 config GPIO_ADP5588_IRQ
611 bool "Interrupt controller support for ADP5588"
612 depends on GPIO_ADP5588=y
614 Say yes here to enable the adp5588 to be used as an interrupt
615 controller. It requires the driver to be built in the kernel.
618 tristate "Avionic Design N-bit GPIO expander"
619 depends on I2C && OF_GPIO
621 This option enables support for N GPIOs found on Avionic Design
622 I2C GPIO expanders. The register space will be extended by powers
623 of two, so the controller will need to accommodate for that. For
624 example: if a controller provides 48 pins, 6 registers will be
625 enough to represent all pins, but the driver will assume a
626 register layout for 64 pins (8 registers).
628 comment "PCI GPIO expanders:"
631 tristate "AMD CS5535/CS5536 GPIO support"
632 depends on PCI && X86 && MFD_CS5535
634 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
635 can be used for quite a number of things. The CS5535/6 is found on
636 AMD Geode and Lemote Yeeloong devices.
641 tristate "BT8XX GPIO abuser"
642 depends on PCI && VIDEO_BT848=n
644 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
645 as a cheap PCI GPIO card.
647 This chip can be found on Miro, Hauppauge and STB TV-cards.
649 The card needs to be physically altered for using it as a
650 GPIO card. For more information on how to build a GPIO card
651 from a BT8xx TV card, see the documentation file at
652 Documentation/bt8xxgpio.txt
657 tristate "AMD 8111 GPIO driver"
660 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
662 Note, that usually system firmware/ACPI handles GPIO pins on their
663 own and users might easily break their systems with uncarefull usage
668 config GPIO_INTEL_MID
669 bool "Intel Mid GPIO support"
670 depends on PCI && X86
673 Say Y here to support Intel Mid GPIO.
676 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
677 depends on PCI && X86
678 select GENERIC_IRQ_CHIP
680 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
681 which is an IOH(Input/Output Hub) for x86 embedded processor.
682 This driver can access PCH GPIO device.
684 This driver also can be used for LAPIS Semiconductor IOH(Input/
685 Output Hub), ML7223 and ML7831.
686 ML7223 IOH is for MP(Media Phone) use.
687 ML7831 IOH is for general purpose use.
688 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
689 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
692 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
694 select GENERIC_IRQ_CHIP
696 ML7213 is companion chip for Intel Atom E6xx series.
697 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
698 Hub) which is for IVI(In-Vehicle Infotainment) use.
699 This driver can access the IOH's GPIO device.
701 config GPIO_SODAVILLE
702 bool "Intel Sodaville GPIO support"
703 depends on X86 && PCI && OF
705 select GENERIC_IRQ_CHIP
707 Say Y here to support Intel Sodaville GPIO.
709 config GPIO_TIMBERDALE
710 bool "Support for timberdale GPIO IP"
711 depends on MFD_TIMBERDALE && HAS_IOMEM
713 Add support for the GPIO IP in the timberdale FPGA.
716 tristate "RDC R-321x GPIO support"
721 Support for the RDC R321x SoC GPIOs over southbridge
722 PCI configuration space.
724 comment "SPI GPIO expanders:"
727 tristate "Maxim MAX7301 GPIO expander"
728 depends on SPI_MASTER
731 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
734 tristate "Microchip MCP23xxx I/O expander"
736 depends on (SPI_MASTER && !I2C) || I2C
738 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
740 This provides a GPIO interface supporting inputs and outputs.
741 The I2C versions of the chips can be used as interrupt-controller.
744 tristate "Freescale MC33880 high-side/low-side switch"
745 depends on SPI_MASTER
747 SPI driver for Freescale MC33880 high-side/low-side switch.
748 This provides GPIO interface supporting inputs and outputs.
751 tristate "74x164 serial-in/parallel-out 8-bits shift register"
752 depends on SPI_MASTER && OF
754 Driver for 74x164 compatible serial-in/parallel-out 8-outputs
755 shift registers. This driver can be used to provide access
756 to more gpio outputs.
758 comment "AC97 GPIO expanders:"
761 tristate "Philips UCB1400 GPIO"
762 depends on UCB1400_CORE
764 This enables support for the Philips UCB1400 GPIO pins.
765 The UCB1400 is an AC97 audio codec.
767 comment "LPC GPIO expanders:"
770 tristate "Kontron ETX / COMexpress GPIO"
771 depends on MFD_KEMPLD
773 This enables support for the PLD GPIO interface on some Kontron ETX
774 and COMexpress (ETXexpress) modules.
776 This driver can also be built as a module. If so, the module will be
779 comment "MODULbus GPIO expanders:"
782 tristate "Janz VMOD-TTL Digital IO Module"
783 depends on MFD_JANZ_CMODIO
785 This enables support for the Janz VMOD-TTL Digital IO module.
786 This driver provides support for driving the pins in output
787 mode only. Input mode is not supported.
790 bool "TI PALMAS series PMICs GPIO"
791 depends on MFD_PALMAS
793 Select this option to enable GPIO driver for the TI PALMAS
798 depends on MFD_TPS6586X
800 Select this option to enable GPIO driver for the TPS6586X
805 depends on MFD_TPS65910
807 Select this option to enable GPIO driver for the TPS65910
811 bool "Intel MSIC mixed signal gpio support"
812 depends on MFD_INTEL_MSIC
814 Enable support for GPIO on intel MSIC controllers found in
818 bool "Broadcom Kona GPIO"
821 Turn on GPIO support for Broadcom "Kona" chips.
823 comment "USB GPIO expanders:"
825 config GPIO_VIPERBOARD
826 tristate "Viperboard GPIO a & b support"
827 depends on MFD_VIPERBOARD && USB
829 Say yes here to access the GPIO signals of Nano River
830 Technologies Viperboard. There are two GPIO chips on the
831 board: gpioa and gpiob.
832 See viperboard API specification and Nano
833 River Tech's viperboard.h for detailed meaning
834 of the module parameters.