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.
40 depends on ARCH_WANT_OPTIONAL_GPIOLIB || ARCH_REQUIRE_GPIOLIB
42 This enables GPIO support through the generic GPIO library.
43 You only need to enable this, if you also want to enable
44 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"
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.
151 depends on PPC_MPC52xx
154 bool "MPC512x/MPC8xxx GPIO support"
155 depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \
156 FSL_SOC_BOOKE || PPC_86xx
158 Say Y here if you're going to use hardware that connects to the
159 MPC512x/831x/834x/837x/8572/8610 GPIOs.
162 tristate "Qualcomm MSM GPIO v1"
163 depends on GPIOLIB && ARCH_MSM && (ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50)
165 Say yes here to support the GPIO interface on ARM v6 based
166 Qualcomm MSM chips. Most of the pins on the MSM can be
167 selected for GPIO, and are controlled by this driver.
170 tristate "Qualcomm MSM GPIO v2"
171 depends on GPIOLIB && OF && ARCH_MSM
173 Say yes here to support the GPIO interface on ARM v7 based
174 Qualcomm MSM chips. Most of the pins on the MSM can be
175 selected for GPIO, and are controlled by this driver.
179 depends on PLAT_ORION
182 select GENERIC_IRQ_CHIP
188 select GENERIC_IRQ_CHIP
194 select GENERIC_IRQ_CHIP
197 bool "PrimeCell PL061 GPIO support"
198 depends on ARM && ARM_AMBA
199 select GENERIC_IRQ_CHIP
201 Say yes here to support the PrimeCell PL061 GPIO device
204 bool "PXA GPIO support"
205 depends on ARCH_PXA || ARCH_MMP
207 Say yes here to support the PXA GPIO device
210 tristate "Renesas R-Car GPIO"
213 Say yes here to support GPIO on Renesas R-Car SoCs.
217 depends on PLAT_SAMSUNG
219 Legacy GPIO support. Use only for platforms without support for
222 config GPIO_SPEAR_SPICS
223 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
224 depends on PLAT_SPEAR
225 select GENERIC_IRQ_CHIP
227 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
230 bool "STA2x11/ConneXt GPIO support"
231 depends on MFD_STA2X11
232 select GENERIC_IRQ_CHIP
234 Say yes here to support the STA2x11/ConneXt GPIO device.
235 The GPIO module has 128 GPIO pins with alternate functions.
238 tristate "TS-5500 DIO blocks and compatibles"
240 This driver supports Digital I/O exposed by pin blocks found on some
241 Technologic Systems platforms. It includes, but is not limited to, 3
242 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
246 bool "Xilinx GPIO support"
247 depends on PPC_OF || MICROBLAZE || ARCH_ZYNQ
249 Say yes here to support the Xilinx FPGA GPIO device
252 tristate "NEC VR4100 series General-purpose I/O Uint support"
253 depends on CPU_VR41XX
255 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
258 tristate "Intel SCH/TunnelCreek/Centerton GPIO"
259 depends on PCI && X86
263 Say yes here to support GPIO interface on Intel Poulsbo SCH,
264 Intel Tunnel Creek processor or Intel Centerton processor.
265 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
266 powered by the core power rail and are turned off during sleep
267 modes (S3 and higher). The remaining four GPIOs are powered by
268 the Intel SCH suspend power supply. These GPIOs remain
269 active during S3. The suspend powered GPIOs can be used to wake the
270 system from the Suspend-to-RAM state.
271 The Intel Tunnel Creek processor has 5 GPIOs powered by the
272 core power rail and 9 from suspend power supply.
273 The Intel Centerton processor has a total of 30 GPIO pins.
274 Twenty-one are powered by the core power rail and 9 from the
275 suspend power supply.
278 tristate "Intel ICH GPIO"
279 depends on PCI && X86
283 Say yes here to support the GPIO functionality of a number of Intel
284 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
285 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
286 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
291 tristate "VIA VX855/VX875 GPIO"
292 depends on PCI && GENERIC_HARDIRQS
296 Support access to the VX855/VX875 GPIO lines through the gpio library.
298 This driver provides common support for accessing the device,
299 additional drivers must be enabled in order to use the
300 functionality of the device.
303 bool "GE FPGA based GPIO"
306 Support for common GPIO functionality provided on some GE Single Board
309 This driver provides basic support (configure as input or output, read
310 and write pin state) for GPIO implemented in a number of GE single
313 config GPIO_LYNXPOINT
314 bool "Intel Lynxpoint GPIO support"
315 depends on ACPI && X86
318 driver for GPIO functionality on Intel Lynxpoint PCH chipset
319 Requires ACPI device enumeration code to set up a platform device.
322 tristate "Aeroflex Gaisler GRGPIO support"
327 Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
328 VHDL IP core library.
330 comment "I2C GPIO expanders:"
333 tristate "Wolfson Microelectronics Arizona class devices"
334 depends on MFD_ARIZONA
336 Support for GPIOs on Wolfson Arizona class devices.
339 tristate "Maxim MAX7300 GPIO expander"
343 GPIO driver for Maxim MAX7300 I2C-based GPIO expander.
346 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
349 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
350 Port Expanders. Each IO port on these chips has a fixed role of
351 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
352 Input and Output (designed by 'P'). The combinations are listed
355 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
356 max7322 (4I4O), max7323 (4P4O)
358 16 bits: max7324 (8I8O), max7325 (8P8O),
359 max7326 (4I12O), max7327 (4P12O)
361 Board setup code must specify the model to use, and the start
362 number for these GPIOs.
364 config GPIO_MAX732X_IRQ
365 bool "Interrupt controller support for MAX732x"
366 depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
368 Say yes here to enable the max732x to be used as an interrupt
369 controller. It requires the driver to be built in the kernel.
371 config GPIO_MC9S08DZ60
372 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
373 depends on I2C=y && MACH_MX35_3DS
375 Select this to enable the MC9S08DZ60 GPIO driver
378 tristate "PCA953x, PCA955x, PCA957x, TCA64xx, and MAX7310 I/O ports"
381 Say yes here to provide access to several register-oriented
382 SMBus I/O expanders, made mostly by NXP or TI. Compatible
385 4 bits: pca9536, pca9537
387 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
388 pca9556, pca9557, pca9574, tca6408
390 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
393 config GPIO_PCA953X_IRQ
394 bool "Interrupt controller support for PCA953x"
395 depends on GPIO_PCA953X=y
397 Say yes here to enable the pca953x to be used as an interrupt
398 controller. It requires the driver to be built in the kernel.
401 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
405 Say yes here to provide access to most "quasi-bidirectional" I2C
406 GPIO expanders used for additional digital outputs or inputs.
407 Most of these parts are from NXP, though TI is a second source for
408 some of them. Compatible models include:
410 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
411 pca9670, pca9672, pca9674, pca9674a,
414 16 bits: pcf8575, pcf8575c, pca8575,
415 pca9671, pca9673, pca9675
417 Your board setup code will need to declare the expanders in
418 use, and assign numbers to the GPIOs they expose. Those GPIOs
419 can then be used from drivers and other kernel code, just like
420 other GPIOs, but only accessible from task contexts.
422 This driver provides an in-kernel interface to those GPIOs using
423 platform-neutral GPIO calls.
426 bool "RICOH RC5T583 GPIO"
427 depends on MFD_RC5T583
429 Select this option to enable GPIO driver for the Ricoh RC5T583
431 This driver provides the support for driving/reading the gpio pins
432 of RC5T583 device through standard gpio library.
435 bool "Semtech SX150x I2C GPIO expander"
439 Say yes here to provide support for Semtech SX150-series I2C
440 GPIO expanders. Compatible models include:
449 This enables support for the GPIOs found on the STMPE I/O
453 bool "XWAY STP GPIOs"
456 This enables support for the Serial To Parallel (STP) unit found on
457 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
458 that can be up to 24 bit. This peripheral is aimed at driving leds.
459 Some of the gpios/leds can be auto updated by the soc with dsl and
464 depends on MFD_TC3589X
466 This enables support for the GPIOs found on the TC3589X
470 tristate "TI TPS65912 GPIO"
471 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
473 This driver supports TPS65912 gpio chip
476 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
477 depends on TWL4030_CORE
479 Say yes here to access the GPIO signals of various multi-function
480 power management chips from Texas Instruments.
483 tristate "TWL6040 GPO"
484 depends on TWL6040_CORE
486 Say yes here to access the GPO signals of twl6040
487 audio chip from Texas Instruments.
490 tristate "WM831x GPIOs"
491 depends on MFD_WM831X
493 Say yes here to access the GPIO signals of WM831x power management
494 chips from Wolfson Microelectronics.
497 tristate "WM8350 GPIOs"
498 depends on MFD_WM8350
500 Say yes here to access the GPIO signals of WM8350 power management
501 chips from Wolfson Microelectronics.
504 tristate "WM8994 GPIOs"
505 depends on MFD_WM8994
507 Say yes here to access the GPIO signals of WM8994 audio hub
508 CODECs from Wolfson Microelectronics.
511 tristate "GPIO Support for ADP5520 PMIC"
512 depends on PMIC_ADP5520
514 This option enables support for on-chip GPIO found
515 on Analog Devices ADP5520 PMICs.
518 tristate "ADP5588 I2C GPIO expander"
521 This option enables support for 18 GPIOs found
522 on Analog Devices ADP5588 GPIO Expanders.
524 config GPIO_ADP5588_IRQ
525 bool "Interrupt controller support for ADP5588"
526 depends on GPIO_ADP5588=y
528 Say yes here to enable the adp5588 to be used as an interrupt
529 controller. It requires the driver to be built in the kernel.
532 tristate "Avionic Design N-bit GPIO expander"
533 depends on I2C && OF_GPIO
535 This option enables support for N GPIOs found on Avionic Design
536 I2C GPIO expanders. The register space will be extended by powers
537 of two, so the controller will need to accommodate for that. For
538 example: if a controller provides 48 pins, 6 registers will be
539 enough to represent all pins, but the driver will assume a
540 register layout for 64 pins (8 registers).
542 comment "PCI GPIO expanders:"
545 tristate "AMD CS5535/CS5536 GPIO support"
546 depends on PCI && X86 && MFD_CS5535
548 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
549 can be used for quite a number of things. The CS5535/6 is found on
550 AMD Geode and Lemote Yeeloong devices.
555 tristate "BT8XX GPIO abuser"
556 depends on PCI && VIDEO_BT848=n
558 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
559 as a cheap PCI GPIO card.
561 This chip can be found on Miro, Hauppauge and STB TV-cards.
563 The card needs to be physically altered for using it as a
564 GPIO card. For more information on how to build a GPIO card
565 from a BT8xx TV card, see the documentation file at
566 Documentation/bt8xxgpio.txt
571 tristate "AMD 8111 GPIO driver"
574 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
576 Note, that usually system firmware/ACPI handles GPIO pins on their
577 own and users might easily break their systems with uncarefull usage
583 bool "Intel Langwell/Penwell GPIO support"
584 depends on PCI && X86
587 Say Y here to support Intel Langwell/Penwell GPIO.
590 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
591 depends on PCI && X86
592 select GENERIC_IRQ_CHIP
594 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
595 which is an IOH(Input/Output Hub) for x86 embedded processor.
596 This driver can access PCH GPIO device.
598 This driver also can be used for LAPIS Semiconductor IOH(Input/
599 Output Hub), ML7223 and ML7831.
600 ML7223 IOH is for MP(Media Phone) use.
601 ML7831 IOH is for general purpose use.
602 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
603 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
606 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
608 select GENERIC_IRQ_CHIP
610 ML7213 is companion chip for Intel Atom E6xx series.
611 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
612 Hub) which is for IVI(In-Vehicle Infotainment) use.
613 This driver can access the IOH's GPIO device.
615 config GPIO_SODAVILLE
616 bool "Intel Sodaville GPIO support"
617 depends on X86 && PCI && OF
619 select GENERIC_IRQ_CHIP
621 Say Y here to support Intel Sodaville GPIO.
623 config GPIO_TIMBERDALE
624 bool "Support for timberdale GPIO IP"
625 depends on MFD_TIMBERDALE && HAS_IOMEM
627 Add support for the GPIO IP in the timberdale FPGA.
630 tristate "RDC R-321x GPIO support"
631 depends on PCI && GENERIC_HARDIRQS
635 Support for the RDC R321x SoC GPIOs over southbridge
636 PCI configuration space.
638 comment "SPI GPIO expanders:"
641 tristate "Maxim MAX7301 GPIO expander"
642 depends on SPI_MASTER
645 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
648 tristate "Microchip MCP23xxx I/O expander"
649 depends on (SPI_MASTER && !I2C) || I2C
651 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
653 This provides a GPIO interface supporting inputs and outputs.
656 tristate "Freescale MC33880 high-side/low-side switch"
657 depends on SPI_MASTER
659 SPI driver for Freescale MC33880 high-side/low-side switch.
660 This provides GPIO interface supporting inputs and outputs.
663 tristate "74x164 serial-in/parallel-out 8-bits shift register"
664 depends on SPI_MASTER
666 Platform driver for 74x164 compatible serial-in/parallel-out
667 8-outputs shift registers. This driver can be used to provide access
668 to more gpio outputs.
670 comment "AC97 GPIO expanders:"
673 bool "Philips UCB1400 GPIO"
674 depends on UCB1400_CORE
676 This enables support for the Philips UCB1400 GPIO pins.
677 The UCB1400 is an AC97 audio codec.
679 comment "MODULbus GPIO expanders:"
682 tristate "Janz VMOD-TTL Digital IO Module"
683 depends on MFD_JANZ_CMODIO
685 This enables support for the Janz VMOD-TTL Digital IO module.
686 This driver provides support for driving the pins in output
687 mode only. Input mode is not supported.
690 bool "TI PALMAS series PMICs GPIO"
691 depends on MFD_PALMAS
693 Select this option to enable GPIO driver for the TI PALMAS
698 depends on MFD_TPS6586X
700 Select this option to enable GPIO driver for the TPS6586X
705 depends on MFD_TPS65910
707 Select this option to enable GPIO driver for the TPS65910
711 bool "Intel MSIC mixed signal gpio support"
712 depends on MFD_INTEL_MSIC
714 Enable support for GPIO on intel MSIC controllers found in
717 comment "USB GPIO expanders:"
719 config GPIO_VIPERBOARD
720 tristate "Viperboard GPIO a & b support"
721 depends on MFD_VIPERBOARD && USB
723 Say yes here to access the GPIO signals of Nano River
724 Technologies Viperboard. There are two GPIO chips on the
725 board: gpioa and gpiob.
726 See viperboard API specification and Nano
727 River Tech's viperboard.h for detailed meaning
728 of the module parameters.