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
116 Say yes here to support GPIO on CLPS711X SoCs.
118 config GPIO_GENERIC_PLATFORM
119 tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
122 Say yes here to support basic platform_device memory-mapped GPIO controllers.
125 tristate "IT8761E GPIO support"
126 depends on X86 # unconditional access to IO space.
128 Say yes here to support GPIO functionality of IT8761E super I/O chip.
131 tristate "Emma Mobile GPIO"
132 depends on ARM && OF_GPIO
134 Say yes here to support GPIO on Renesas Emma Mobile SoCs.
138 depends on ARCH_EP93XX
141 config GPIO_MM_LANTIQ
142 bool "Lantiq Memory mapped GPIOs"
143 depends on LANTIQ && SOC_XWAY
145 This enables support for memory mapped GPIOs on the External Bus Unit
146 (EBU) found on Lantiq SoCs. The gpios are output only as they are
147 created by attaching a 16bit latch to the bus.
150 tristate "F71882FG and F71889F GPIO support"
153 This option enables support for GPIOs found on Fintek Super-I/O
154 chips F71882FG and F71889F.
156 To compile this driver as a module, choose M here: the module will
157 be called f7188x-gpio.
161 depends on PPC_MPC52xx
164 bool "MPC512x/MPC8xxx GPIO support"
165 depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \
166 FSL_SOC_BOOKE || PPC_86xx
168 Say Y here if you're going to use hardware that connects to the
169 MPC512x/831x/834x/837x/8572/8610 GPIOs.
172 tristate "Qualcomm MSM GPIO v1"
173 depends on GPIOLIB && ARCH_MSM && (ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50)
175 Say yes here to support the GPIO interface on ARM v6 based
176 Qualcomm MSM chips. Most of the pins on the MSM can be
177 selected for GPIO, and are controlled by this driver.
180 tristate "Qualcomm MSM GPIO v2"
181 depends on GPIOLIB && OF && ARCH_MSM
183 Say yes here to support the GPIO interface on ARM v7 based
184 Qualcomm MSM chips. Most of the pins on the MSM can be
185 selected for GPIO, and are controlled by this driver.
189 depends on PLAT_ORION
192 select GENERIC_IRQ_CHIP
198 select GENERIC_IRQ_CHIP
204 select GENERIC_IRQ_CHIP
207 tristate "Cavium OCTEON GPIO"
208 depends on GPIOLIB && CAVIUM_OCTEON_SOC
211 Say yes here to support the on-chip GPIO lines on the OCTEON
215 bool "PrimeCell PL061 GPIO support"
217 select GENERIC_IRQ_CHIP
219 Say yes here to support the PrimeCell PL061 GPIO device
222 bool "PXA GPIO support"
223 depends on ARCH_PXA || ARCH_MMP
225 Say yes here to support the PXA GPIO device
228 tristate "Renesas R-Car GPIO"
231 Say yes here to support GPIO on Renesas R-Car SoCs.
235 depends on PLAT_SAMSUNG
237 Legacy GPIO support. Use only for platforms without support for
240 config GPIO_SPEAR_SPICS
241 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
242 depends on PLAT_SPEAR
243 select GENERIC_IRQ_CHIP
245 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
248 bool "STA2x11/ConneXt GPIO support"
249 depends on MFD_STA2X11
250 select GENERIC_IRQ_CHIP
252 Say yes here to support the STA2x11/ConneXt GPIO device.
253 The GPIO module has 128 GPIO pins with alternate functions.
256 tristate "TS-5500 DIO blocks and compatibles"
258 This driver supports Digital I/O exposed by pin blocks found on some
259 Technologic Systems platforms. It includes, but is not limited to, 3
260 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
264 bool "Toumaz Xenif TZ1090 GPIO support"
265 depends on SOC_TZ1090
266 select GENERIC_IRQ_CHIP
269 Say yes here to support Toumaz Xenif TZ1090 GPIOs.
271 config GPIO_TZ1090_PDC
272 bool "Toumaz Xenif TZ1090 PDC GPIO support"
273 depends on SOC_TZ1090
276 Say yes here to support Toumaz Xenif TZ1090 PDC GPIOs.
279 bool "Xilinx GPIO support"
280 depends on PPC_OF || MICROBLAZE || ARCH_ZYNQ
282 Say yes here to support the Xilinx FPGA GPIO device
285 tristate "NEC VR4100 series General-purpose I/O Uint support"
286 depends on CPU_VR41XX
288 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
291 tristate "Intel SCH/TunnelCreek/Centerton GPIO"
292 depends on PCI && X86
296 Say yes here to support GPIO interface on Intel Poulsbo SCH,
297 Intel Tunnel Creek processor or Intel Centerton processor.
298 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
299 powered by the core power rail and are turned off during sleep
300 modes (S3 and higher). The remaining four GPIOs are powered by
301 the Intel SCH suspend power supply. These GPIOs remain
302 active during S3. The suspend powered GPIOs can be used to wake the
303 system from the Suspend-to-RAM state.
304 The Intel Tunnel Creek processor has 5 GPIOs powered by the
305 core power rail and 9 from suspend power supply.
306 The Intel Centerton processor has a total of 30 GPIO pins.
307 Twenty-one are powered by the core power rail and 9 from the
308 suspend power supply.
311 tristate "Intel ICH GPIO"
312 depends on PCI && X86
316 Say yes here to support the GPIO functionality of a number of Intel
317 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
318 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
319 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
324 tristate "Intel IOP GPIO"
325 depends on ARM && (ARCH_IOP32X || ARCH_IOP33X)
327 Say yes here to support the GPIO functionality of a number of Intel
333 tristate "VIA VX855/VX875 GPIO"
338 Support access to the VX855/VX875 GPIO lines through the gpio library.
340 This driver provides common support for accessing the device,
341 additional drivers must be enabled in order to use the
342 functionality of the device.
345 bool "GE FPGA based GPIO"
348 Support for common GPIO functionality provided on some GE Single Board
351 This driver provides basic support (configure as input or output, read
352 and write pin state) for GPIO implemented in a number of GE single
355 config GPIO_LYNXPOINT
356 bool "Intel Lynxpoint GPIO support"
357 depends on ACPI && X86
360 driver for GPIO functionality on Intel Lynxpoint PCH chipset
361 Requires ACPI device enumeration code to set up a platform device.
364 tristate "Aeroflex Gaisler GRGPIO support"
369 Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
370 VHDL IP core library.
376 comment "I2C GPIO expanders:"
379 tristate "Wolfson Microelectronics Arizona class devices"
380 depends on MFD_ARIZONA
382 Support for GPIOs on Wolfson Arizona class devices.
385 tristate "Maxim MAX7300 GPIO expander"
389 GPIO driver for Maxim MAX7300 I2C-based GPIO expander.
392 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
395 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
396 Port Expanders. Each IO port on these chips has a fixed role of
397 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
398 Input and Output (designed by 'P'). The combinations are listed
401 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
402 max7322 (4I4O), max7323 (4P4O)
404 16 bits: max7324 (8I8O), max7325 (8P8O),
405 max7326 (4I12O), max7327 (4P12O)
407 Board setup code must specify the model to use, and the start
408 number for these GPIOs.
410 config GPIO_MAX732X_IRQ
411 bool "Interrupt controller support for MAX732x"
412 depends on GPIO_MAX732X=y
414 Say yes here to enable the max732x to be used as an interrupt
415 controller. It requires the driver to be built in the kernel.
417 config GPIO_MC9S08DZ60
418 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
419 depends on I2C=y && MACH_MX35_3DS
421 Select this to enable the MC9S08DZ60 GPIO driver
424 tristate "PCA953x, PCA955x, PCA957x, TCA64xx, and MAX7310 I/O ports"
427 Say yes here to provide access to several register-oriented
428 SMBus I/O expanders, made mostly by NXP or TI. Compatible
431 4 bits: pca9536, pca9537
433 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
434 pca9556, pca9557, pca9574, tca6408
436 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
439 config GPIO_PCA953X_IRQ
440 bool "Interrupt controller support for PCA953x"
441 depends on GPIO_PCA953X=y
443 Say yes here to enable the pca953x to be used as an interrupt
444 controller. It requires the driver to be built in the kernel.
447 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
451 Say yes here to provide access to most "quasi-bidirectional" I2C
452 GPIO expanders used for additional digital outputs or inputs.
453 Most of these parts are from NXP, though TI is a second source for
454 some of them. Compatible models include:
456 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
457 pca9670, pca9672, pca9674, pca9674a,
460 16 bits: pcf8575, pcf8575c, pca8575,
461 pca9671, pca9673, pca9675
463 Your board setup code will need to declare the expanders in
464 use, and assign numbers to the GPIOs they expose. Those GPIOs
465 can then be used from drivers and other kernel code, just like
466 other GPIOs, but only accessible from task contexts.
468 This driver provides an in-kernel interface to those GPIOs using
469 platform-neutral GPIO calls.
472 bool "RICOH RC5T583 GPIO"
473 depends on MFD_RC5T583
475 Select this option to enable GPIO driver for the Ricoh RC5T583
477 This driver provides the support for driving/reading the gpio pins
478 of RC5T583 device through standard gpio library.
481 bool "Semtech SX150x I2C GPIO expander"
485 Say yes here to provide support for Semtech SX150-series I2C
486 GPIO expanders. Compatible models include:
495 This enables support for the GPIOs found on the STMPE I/O
499 bool "XWAY STP GPIOs"
502 This enables support for the Serial To Parallel (STP) unit found on
503 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
504 that can be up to 24 bit. This peripheral is aimed at driving leds.
505 Some of the gpios/leds can be auto updated by the soc with dsl and
510 depends on MFD_TC3589X
512 This enables support for the GPIOs found on the TC3589X
516 tristate "TI TPS65912 GPIO"
517 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
519 This driver supports TPS65912 gpio chip
522 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
523 depends on TWL4030_CORE
525 Say yes here to access the GPIO signals of various multi-function
526 power management chips from Texas Instruments.
529 tristate "TWL6040 GPO"
530 depends on TWL6040_CORE
532 Say yes here to access the GPO signals of twl6040
533 audio chip from Texas Instruments.
536 tristate "WM831x GPIOs"
537 depends on MFD_WM831X
539 Say yes here to access the GPIO signals of WM831x power management
540 chips from Wolfson Microelectronics.
543 tristate "WM8350 GPIOs"
544 depends on MFD_WM8350
546 Say yes here to access the GPIO signals of WM8350 power management
547 chips from Wolfson Microelectronics.
550 tristate "WM8994 GPIOs"
551 depends on MFD_WM8994
553 Say yes here to access the GPIO signals of WM8994 audio hub
554 CODECs from Wolfson Microelectronics.
557 tristate "GPIO Support for ADP5520 PMIC"
558 depends on PMIC_ADP5520
560 This option enables support for on-chip GPIO found
561 on Analog Devices ADP5520 PMICs.
564 tristate "ADP5588 I2C GPIO expander"
567 This option enables support for 18 GPIOs found
568 on Analog Devices ADP5588 GPIO Expanders.
570 config GPIO_ADP5588_IRQ
571 bool "Interrupt controller support for ADP5588"
572 depends on GPIO_ADP5588=y
574 Say yes here to enable the adp5588 to be used as an interrupt
575 controller. It requires the driver to be built in the kernel.
578 tristate "Avionic Design N-bit GPIO expander"
579 depends on I2C && OF_GPIO
581 This option enables support for N GPIOs found on Avionic Design
582 I2C GPIO expanders. The register space will be extended by powers
583 of two, so the controller will need to accommodate for that. For
584 example: if a controller provides 48 pins, 6 registers will be
585 enough to represent all pins, but the driver will assume a
586 register layout for 64 pins (8 registers).
588 comment "PCI GPIO expanders:"
591 tristate "AMD CS5535/CS5536 GPIO support"
592 depends on PCI && X86 && MFD_CS5535
594 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
595 can be used for quite a number of things. The CS5535/6 is found on
596 AMD Geode and Lemote Yeeloong devices.
601 tristate "BT8XX GPIO abuser"
602 depends on PCI && VIDEO_BT848=n
604 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
605 as a cheap PCI GPIO card.
607 This chip can be found on Miro, Hauppauge and STB TV-cards.
609 The card needs to be physically altered for using it as a
610 GPIO card. For more information on how to build a GPIO card
611 from a BT8xx TV card, see the documentation file at
612 Documentation/bt8xxgpio.txt
617 tristate "AMD 8111 GPIO driver"
620 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
622 Note, that usually system firmware/ACPI handles GPIO pins on their
623 own and users might easily break their systems with uncarefull usage
628 config GPIO_INTEL_MID
629 bool "Intel Mid GPIO support"
630 depends on PCI && X86
633 Say Y here to support Intel Mid GPIO.
636 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
637 depends on PCI && X86
638 select GENERIC_IRQ_CHIP
640 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
641 which is an IOH(Input/Output Hub) for x86 embedded processor.
642 This driver can access PCH GPIO device.
644 This driver also can be used for LAPIS Semiconductor IOH(Input/
645 Output Hub), ML7223 and ML7831.
646 ML7223 IOH is for MP(Media Phone) use.
647 ML7831 IOH is for general purpose use.
648 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
649 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
652 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
654 select GENERIC_IRQ_CHIP
656 ML7213 is companion chip for Intel Atom E6xx series.
657 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
658 Hub) which is for IVI(In-Vehicle Infotainment) use.
659 This driver can access the IOH's GPIO device.
661 config GPIO_SODAVILLE
662 bool "Intel Sodaville GPIO support"
663 depends on X86 && PCI && OF
665 select GENERIC_IRQ_CHIP
667 Say Y here to support Intel Sodaville GPIO.
669 config GPIO_TIMBERDALE
670 bool "Support for timberdale GPIO IP"
671 depends on MFD_TIMBERDALE && HAS_IOMEM
673 Add support for the GPIO IP in the timberdale FPGA.
676 tristate "RDC R-321x GPIO support"
681 Support for the RDC R321x SoC GPIOs over southbridge
682 PCI configuration space.
684 comment "SPI GPIO expanders:"
687 tristate "Maxim MAX7301 GPIO expander"
688 depends on SPI_MASTER
691 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
694 tristate "Microchip MCP23xxx I/O expander"
695 depends on (SPI_MASTER && !I2C) || I2C
697 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
699 This provides a GPIO interface supporting inputs and outputs.
702 tristate "Freescale MC33880 high-side/low-side switch"
703 depends on SPI_MASTER
705 SPI driver for Freescale MC33880 high-side/low-side switch.
706 This provides GPIO interface supporting inputs and outputs.
709 tristate "74x164 serial-in/parallel-out 8-bits shift register"
710 depends on SPI_MASTER
712 Platform driver for 74x164 compatible serial-in/parallel-out
713 8-outputs shift registers. This driver can be used to provide access
714 to more gpio outputs.
716 comment "AC97 GPIO expanders:"
719 tristate "Philips UCB1400 GPIO"
720 depends on UCB1400_CORE
722 This enables support for the Philips UCB1400 GPIO pins.
723 The UCB1400 is an AC97 audio codec.
725 comment "LPC GPIO expanders:"
728 tristate "Kontron ETX / COMexpress GPIO"
729 depends on MFD_KEMPLD
731 This enables support for the PLD GPIO interface on some Kontron ETX
732 and COMexpress (ETXexpress) modules.
734 This driver can also be built as a module. If so, the module will be
737 comment "MODULbus GPIO expanders:"
740 tristate "Janz VMOD-TTL Digital IO Module"
741 depends on MFD_JANZ_CMODIO
743 This enables support for the Janz VMOD-TTL Digital IO module.
744 This driver provides support for driving the pins in output
745 mode only. Input mode is not supported.
748 bool "TI PALMAS series PMICs GPIO"
749 depends on MFD_PALMAS
751 Select this option to enable GPIO driver for the TI PALMAS
756 depends on MFD_TPS6586X
758 Select this option to enable GPIO driver for the TPS6586X
763 depends on MFD_TPS65910
765 Select this option to enable GPIO driver for the TPS65910
769 bool "Intel MSIC mixed signal gpio support"
770 depends on MFD_INTEL_MSIC
772 Enable support for GPIO on intel MSIC controllers found in
776 bool "Broadcom Kona GPIO"
779 Turn on GPIO support for Broadcom "Kona" chips.
781 comment "USB GPIO expanders:"
783 config GPIO_VIPERBOARD
784 tristate "Viperboard GPIO a & b support"
785 depends on MFD_VIPERBOARD && USB
787 Say yes here to access the GPIO signals of Nano River
788 Technologies Viperboard. There are two GPIO chips on the
789 board: gpioa and gpiob.
790 See viperboard API specification and Nano
791 River Tech's viperboard.h for detailed meaning
792 of the module parameters.