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.
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 bool "PrimeCell PL061 GPIO support"
208 depends on ARM && ARM_AMBA
209 select GENERIC_IRQ_CHIP
211 Say yes here to support the PrimeCell PL061 GPIO device
214 bool "PXA GPIO support"
215 depends on ARCH_PXA || ARCH_MMP
217 Say yes here to support the PXA GPIO device
220 tristate "Renesas R-Car GPIO"
223 Say yes here to support GPIO on Renesas R-Car SoCs.
227 depends on PLAT_SAMSUNG
229 Legacy GPIO support. Use only for platforms without support for
232 config GPIO_SPEAR_SPICS
233 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
234 depends on PLAT_SPEAR
235 select GENERIC_IRQ_CHIP
237 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
240 bool "STA2x11/ConneXt GPIO support"
241 depends on MFD_STA2X11
242 select GENERIC_IRQ_CHIP
244 Say yes here to support the STA2x11/ConneXt GPIO device.
245 The GPIO module has 128 GPIO pins with alternate functions.
248 tristate "TS-5500 DIO blocks and compatibles"
250 This driver supports Digital I/O exposed by pin blocks found on some
251 Technologic Systems platforms. It includes, but is not limited to, 3
252 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
256 bool "Toumaz Xenif TZ1090 GPIO support"
257 depends on SOC_TZ1090
258 select GENERIC_IRQ_CHIP
261 Say yes here to support Toumaz Xenif TZ1090 GPIOs.
263 config GPIO_TZ1090_PDC
264 bool "Toumaz Xenif TZ1090 PDC GPIO support"
265 depends on SOC_TZ1090
268 Say yes here to support Toumaz Xenif TZ1090 PDC GPIOs.
271 bool "Xilinx GPIO support"
272 depends on PPC_OF || MICROBLAZE || ARCH_ZYNQ
274 Say yes here to support the Xilinx FPGA GPIO device
277 tristate "NEC VR4100 series General-purpose I/O Uint support"
278 depends on CPU_VR41XX
280 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
283 tristate "Intel SCH/TunnelCreek/Centerton GPIO"
284 depends on PCI && X86
288 Say yes here to support GPIO interface on Intel Poulsbo SCH,
289 Intel Tunnel Creek processor or Intel Centerton processor.
290 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
291 powered by the core power rail and are turned off during sleep
292 modes (S3 and higher). The remaining four GPIOs are powered by
293 the Intel SCH suspend power supply. These GPIOs remain
294 active during S3. The suspend powered GPIOs can be used to wake the
295 system from the Suspend-to-RAM state.
296 The Intel Tunnel Creek processor has 5 GPIOs powered by the
297 core power rail and 9 from suspend power supply.
298 The Intel Centerton processor has a total of 30 GPIO pins.
299 Twenty-one are powered by the core power rail and 9 from the
300 suspend power supply.
303 tristate "Intel ICH GPIO"
304 depends on PCI && X86
308 Say yes here to support the GPIO functionality of a number of Intel
309 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
310 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
311 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
316 tristate "VIA VX855/VX875 GPIO"
317 depends on PCI && GENERIC_HARDIRQS
321 Support access to the VX855/VX875 GPIO lines through the gpio library.
323 This driver provides common support for accessing the device,
324 additional drivers must be enabled in order to use the
325 functionality of the device.
328 bool "GE FPGA based GPIO"
331 Support for common GPIO functionality provided on some GE Single Board
334 This driver provides basic support (configure as input or output, read
335 and write pin state) for GPIO implemented in a number of GE single
338 config GPIO_LYNXPOINT
339 bool "Intel Lynxpoint GPIO support"
340 depends on ACPI && X86
343 driver for GPIO functionality on Intel Lynxpoint PCH chipset
344 Requires ACPI device enumeration code to set up a platform device.
347 tristate "Aeroflex Gaisler GRGPIO support"
352 Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
353 VHDL IP core library.
355 comment "I2C GPIO expanders:"
358 tristate "Wolfson Microelectronics Arizona class devices"
359 depends on MFD_ARIZONA
361 Support for GPIOs on Wolfson Arizona class devices.
364 tristate "Maxim MAX7300 GPIO expander"
368 GPIO driver for Maxim MAX7300 I2C-based GPIO expander.
371 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
374 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
375 Port Expanders. Each IO port on these chips has a fixed role of
376 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
377 Input and Output (designed by 'P'). The combinations are listed
380 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
381 max7322 (4I4O), max7323 (4P4O)
383 16 bits: max7324 (8I8O), max7325 (8P8O),
384 max7326 (4I12O), max7327 (4P12O)
386 Board setup code must specify the model to use, and the start
387 number for these GPIOs.
389 config GPIO_MAX732X_IRQ
390 bool "Interrupt controller support for MAX732x"
391 depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
393 Say yes here to enable the max732x to be used as an interrupt
394 controller. It requires the driver to be built in the kernel.
396 config GPIO_MC9S08DZ60
397 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
398 depends on I2C=y && MACH_MX35_3DS
400 Select this to enable the MC9S08DZ60 GPIO driver
403 tristate "PCA953x, PCA955x, PCA957x, TCA64xx, and MAX7310 I/O ports"
406 Say yes here to provide access to several register-oriented
407 SMBus I/O expanders, made mostly by NXP or TI. Compatible
410 4 bits: pca9536, pca9537
412 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
413 pca9556, pca9557, pca9574, tca6408
415 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
418 config GPIO_PCA953X_IRQ
419 bool "Interrupt controller support for PCA953x"
420 depends on GPIO_PCA953X=y
422 Say yes here to enable the pca953x to be used as an interrupt
423 controller. It requires the driver to be built in the kernel.
426 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
430 Say yes here to provide access to most "quasi-bidirectional" I2C
431 GPIO expanders used for additional digital outputs or inputs.
432 Most of these parts are from NXP, though TI is a second source for
433 some of them. Compatible models include:
435 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
436 pca9670, pca9672, pca9674, pca9674a,
439 16 bits: pcf8575, pcf8575c, pca8575,
440 pca9671, pca9673, pca9675
442 Your board setup code will need to declare the expanders in
443 use, and assign numbers to the GPIOs they expose. Those GPIOs
444 can then be used from drivers and other kernel code, just like
445 other GPIOs, but only accessible from task contexts.
447 This driver provides an in-kernel interface to those GPIOs using
448 platform-neutral GPIO calls.
451 bool "RICOH RC5T583 GPIO"
452 depends on MFD_RC5T583
454 Select this option to enable GPIO driver for the Ricoh RC5T583
456 This driver provides the support for driving/reading the gpio pins
457 of RC5T583 device through standard gpio library.
460 bool "Semtech SX150x I2C GPIO expander"
464 Say yes here to provide support for Semtech SX150-series I2C
465 GPIO expanders. Compatible models include:
474 This enables support for the GPIOs found on the STMPE I/O
478 bool "XWAY STP GPIOs"
481 This enables support for the Serial To Parallel (STP) unit found on
482 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
483 that can be up to 24 bit. This peripheral is aimed at driving leds.
484 Some of the gpios/leds can be auto updated by the soc with dsl and
489 depends on MFD_TC3589X
491 This enables support for the GPIOs found on the TC3589X
495 tristate "TI TPS65912 GPIO"
496 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
498 This driver supports TPS65912 gpio chip
501 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
502 depends on TWL4030_CORE
504 Say yes here to access the GPIO signals of various multi-function
505 power management chips from Texas Instruments.
508 tristate "TWL6040 GPO"
509 depends on TWL6040_CORE
511 Say yes here to access the GPO signals of twl6040
512 audio chip from Texas Instruments.
515 tristate "WM831x GPIOs"
516 depends on MFD_WM831X
518 Say yes here to access the GPIO signals of WM831x power management
519 chips from Wolfson Microelectronics.
522 tristate "WM8350 GPIOs"
523 depends on MFD_WM8350
525 Say yes here to access the GPIO signals of WM8350 power management
526 chips from Wolfson Microelectronics.
529 tristate "WM8994 GPIOs"
530 depends on MFD_WM8994
532 Say yes here to access the GPIO signals of WM8994 audio hub
533 CODECs from Wolfson Microelectronics.
536 tristate "GPIO Support for ADP5520 PMIC"
537 depends on PMIC_ADP5520
539 This option enables support for on-chip GPIO found
540 on Analog Devices ADP5520 PMICs.
543 tristate "ADP5588 I2C GPIO expander"
546 This option enables support for 18 GPIOs found
547 on Analog Devices ADP5588 GPIO Expanders.
549 config GPIO_ADP5588_IRQ
550 bool "Interrupt controller support for ADP5588"
551 depends on GPIO_ADP5588=y
553 Say yes here to enable the adp5588 to be used as an interrupt
554 controller. It requires the driver to be built in the kernel.
557 tristate "Avionic Design N-bit GPIO expander"
558 depends on I2C && OF_GPIO
560 This option enables support for N GPIOs found on Avionic Design
561 I2C GPIO expanders. The register space will be extended by powers
562 of two, so the controller will need to accommodate for that. For
563 example: if a controller provides 48 pins, 6 registers will be
564 enough to represent all pins, but the driver will assume a
565 register layout for 64 pins (8 registers).
567 comment "PCI GPIO expanders:"
570 tristate "AMD CS5535/CS5536 GPIO support"
571 depends on PCI && X86 && MFD_CS5535
573 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
574 can be used for quite a number of things. The CS5535/6 is found on
575 AMD Geode and Lemote Yeeloong devices.
580 tristate "BT8XX GPIO abuser"
581 depends on PCI && VIDEO_BT848=n
583 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
584 as a cheap PCI GPIO card.
586 This chip can be found on Miro, Hauppauge and STB TV-cards.
588 The card needs to be physically altered for using it as a
589 GPIO card. For more information on how to build a GPIO card
590 from a BT8xx TV card, see the documentation file at
591 Documentation/bt8xxgpio.txt
596 tristate "AMD 8111 GPIO driver"
599 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
601 Note, that usually system firmware/ACPI handles GPIO pins on their
602 own and users might easily break their systems with uncarefull usage
608 bool "Intel Langwell/Penwell GPIO support"
609 depends on PCI && X86
612 Say Y here to support Intel Langwell/Penwell GPIO.
615 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
616 depends on PCI && X86
617 select GENERIC_IRQ_CHIP
619 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
620 which is an IOH(Input/Output Hub) for x86 embedded processor.
621 This driver can access PCH GPIO device.
623 This driver also can be used for LAPIS Semiconductor IOH(Input/
624 Output Hub), ML7223 and ML7831.
625 ML7223 IOH is for MP(Media Phone) use.
626 ML7831 IOH is for general purpose use.
627 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
628 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
631 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
633 select GENERIC_IRQ_CHIP
635 ML7213 is companion chip for Intel Atom E6xx series.
636 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
637 Hub) which is for IVI(In-Vehicle Infotainment) use.
638 This driver can access the IOH's GPIO device.
640 config GPIO_SODAVILLE
641 bool "Intel Sodaville GPIO support"
642 depends on X86 && PCI && OF
644 select GENERIC_IRQ_CHIP
646 Say Y here to support Intel Sodaville GPIO.
648 config GPIO_TIMBERDALE
649 bool "Support for timberdale GPIO IP"
650 depends on MFD_TIMBERDALE && HAS_IOMEM
652 Add support for the GPIO IP in the timberdale FPGA.
655 tristate "RDC R-321x GPIO support"
656 depends on PCI && GENERIC_HARDIRQS
660 Support for the RDC R321x SoC GPIOs over southbridge
661 PCI configuration space.
663 comment "SPI GPIO expanders:"
666 tristate "Maxim MAX7301 GPIO expander"
667 depends on SPI_MASTER
670 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
673 tristate "Microchip MCP23xxx I/O expander"
674 depends on (SPI_MASTER && !I2C) || I2C
676 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
678 This provides a GPIO interface supporting inputs and outputs.
681 tristate "Freescale MC33880 high-side/low-side switch"
682 depends on SPI_MASTER
684 SPI driver for Freescale MC33880 high-side/low-side switch.
685 This provides GPIO interface supporting inputs and outputs.
688 tristate "74x164 serial-in/parallel-out 8-bits shift register"
689 depends on SPI_MASTER
691 Platform driver for 74x164 compatible serial-in/parallel-out
692 8-outputs shift registers. This driver can be used to provide access
693 to more gpio outputs.
695 comment "AC97 GPIO expanders:"
698 bool "Philips UCB1400 GPIO"
699 depends on UCB1400_CORE
701 This enables support for the Philips UCB1400 GPIO pins.
702 The UCB1400 is an AC97 audio codec.
704 comment "LPC GPIO expanders:"
707 tristate "Kontron ETX / COMexpress GPIO"
708 depends on MFD_KEMPLD
710 This enables support for the PLD GPIO interface on some Kontron ETX
711 and COMexpress (ETXexpress) modules.
713 This driver can also be built as a module. If so, the module will be
716 comment "MODULbus GPIO expanders:"
719 tristate "Janz VMOD-TTL Digital IO Module"
720 depends on MFD_JANZ_CMODIO
722 This enables support for the Janz VMOD-TTL Digital IO module.
723 This driver provides support for driving the pins in output
724 mode only. Input mode is not supported.
727 bool "TI PALMAS series PMICs GPIO"
728 depends on MFD_PALMAS
730 Select this option to enable GPIO driver for the TI PALMAS
735 depends on MFD_TPS6586X
737 Select this option to enable GPIO driver for the TPS6586X
742 depends on MFD_TPS65910
744 Select this option to enable GPIO driver for the TPS65910
748 bool "Intel MSIC mixed signal gpio support"
749 depends on MFD_INTEL_MSIC
751 Enable support for GPIO on intel MSIC controllers found in
754 comment "USB GPIO expanders:"
756 config GPIO_VIPERBOARD
757 tristate "Viperboard GPIO a & b support"
758 depends on MFD_VIPERBOARD && USB
760 Say yes here to access the GPIO signals of Nano River
761 Technologies Viperboard. There are two GPIO chips on the
762 board: gpioa and gpiob.
763 See viperboard API specification and Nano
764 River Tech's viperboard.h for detailed meaning
765 of the module parameters.