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
43 This enables GPIO support through the generic GPIO library.
44 You only need to enable this, if you also want to enable
45 one or more of the GPIO drivers below.
60 bool "Debug GPIO calls"
61 depends on DEBUG_KERNEL
63 Say Y here to add some extra checks and diagnostics to GPIO calls.
64 These checks help ensure that GPIOs have been properly initialized
65 before they are used, and that sleeping calls are not made from
66 non-sleeping contexts. They can make bitbanged serial protocols
67 slower. The diagnostics help catch the type of setup errors
68 that are most common when setting up new platforms or boards.
71 bool "/sys/class/gpio/... (sysfs interface)"
74 Say Y here to add a sysfs interface for GPIOs.
76 This is mostly useful to work around omissions in a system's
77 kernel support. Those are common in custom and semicustom
78 hardware assembled using standard kernels with a minimum of
79 custom patches. In those cases, userspace code may import
80 a given GPIO from the kernel, if no kernel driver requested it.
82 Kernel drivers may also request that a particular GPIO be
83 exported to userspace; this can be useful when debugging.
88 # put drivers in the right section, in alphabetical order
91 tristate "Dialog DA9052 GPIO"
92 depends on PMIC_DA9052
94 Say yes here to enable the GPIO driver for the DA9052 chip.
97 tristate "Dialog Semiconductor DA9055 GPIO"
100 Say yes here to enable the GPIO driver for the DA9055 chip.
102 The Dialog DA9055 PMIC chip has 3 GPIO pins that can be
103 be controller by this driver.
105 If driver is built as a module it will be called gpio-da9055.
110 comment "Memory mapped GPIO drivers:"
114 depends on ARCH_CLPS711X
116 config GPIO_GENERIC_PLATFORM
117 tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
120 Say yes here to support basic platform_device memory-mapped GPIO controllers.
123 tristate "IT8761E GPIO support"
124 depends on X86 # unconditional access to IO space.
126 Say yes here to support GPIO functionality of IT8761E super I/O chip.
129 tristate "Emma Mobile GPIO"
132 Say yes here to support GPIO on Renesas Emma Mobile SoCs.
136 depends on ARCH_EP93XX
139 config GPIO_MM_LANTIQ
140 bool "Lantiq Memory mapped GPIOs"
141 depends on LANTIQ && SOC_XWAY
143 This enables support for memory mapped GPIOs on the External Bus Unit
144 (EBU) found on Lantiq SoCs. The gpios are output only as they are
145 created by attaching a 16bit latch to the bus.
149 depends on PPC_MPC52xx
152 bool "MPC512x/MPC8xxx GPIO support"
153 depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \
154 FSL_SOC_BOOKE || PPC_86xx
156 Say Y here if you're going to use hardware that connects to the
157 MPC512x/831x/834x/837x/8572/8610 GPIOs.
160 tristate "Qualcomm MSM GPIO v1"
161 depends on GPIOLIB && ARCH_MSM && (ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50)
163 Say yes here to support the GPIO interface on ARM v6 based
164 Qualcomm MSM chips. Most of the pins on the MSM can be
165 selected for GPIO, and are controlled by this driver.
168 tristate "Qualcomm MSM GPIO v2"
169 depends on GPIOLIB && ARCH_MSM
171 Say yes here to support the GPIO interface on ARM v7 based
172 Qualcomm MSM chips. Most of the pins on the MSM can be
173 selected for GPIO, and are controlled by this driver.
177 depends on PLAT_ORION
180 select GENERIC_IRQ_CHIP
186 select GENERIC_IRQ_CHIP
192 select GENERIC_IRQ_CHIP
195 bool "PrimeCell PL061 GPIO support"
196 depends on ARM && ARM_AMBA
197 select GENERIC_IRQ_CHIP
199 Say yes here to support the PrimeCell PL061 GPIO device
202 bool "PXA GPIO support"
203 depends on ARCH_PXA || ARCH_MMP
205 Say yes here to support the PXA GPIO device
207 config GPIO_SPEAR_SPICS
208 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
209 depends on PLAT_SPEAR
210 select GENERIC_IRQ_CHIP
212 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
215 bool "STA2x11/ConneXt GPIO support"
216 depends on MFD_STA2X11
217 select GENERIC_IRQ_CHIP
219 Say yes here to support the STA2x11/ConneXt GPIO device.
220 The GPIO module has 128 GPIO pins with alternate functions.
223 tristate "TS-5500 DIO blocks and compatibles"
225 This driver supports Digital I/O exposed by pin blocks found on some
226 Technologic Systems platforms. It includes, but is not limited to, 3
227 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
231 bool "VIA/Wondermedia SoC GPIO Support"
232 depends on ARCH_VT8500
234 Say yes here to support the VT8500/WM8505/WM8650 GPIO controller.
237 bool "Xilinx GPIO support"
238 depends on PPC_OF || MICROBLAZE
240 Say yes here to support the Xilinx FPGA GPIO device
243 tristate "NEC VR4100 series General-purpose I/O Uint support"
244 depends on CPU_VR41XX
246 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
249 tristate "Intel SCH/TunnelCreek/Centerton GPIO"
250 depends on PCI && X86
254 Say yes here to support GPIO interface on Intel Poulsbo SCH,
255 Intel Tunnel Creek processor or Intel Centerton processor.
256 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
257 powered by the core power rail and are turned off during sleep
258 modes (S3 and higher). The remaining four GPIOs are powered by
259 the Intel SCH suspend power supply. These GPIOs remain
260 active during S3. The suspend powered GPIOs can be used to wake the
261 system from the Suspend-to-RAM state.
262 The Intel Tunnel Creek processor has 5 GPIOs powered by the
263 core power rail and 9 from suspend power supply.
264 The Intel Centerton processor has a total of 30 GPIO pins.
265 Twenty-one are powered by the core power rail and 9 from the
266 suspend power supply.
269 tristate "Intel ICH GPIO"
270 depends on PCI && X86
274 Say yes here to support the GPIO functionality of a number of Intel
275 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
276 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
277 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
282 tristate "VIA VX855/VX875 GPIO"
283 depends on PCI && GENERIC_HARDIRQS
287 Support access to the VX855/VX875 GPIO lines through the gpio library.
289 This driver provides common support for accessing the device,
290 additional drivers must be enabled in order to use the
291 functionality of the device.
294 bool "GE FPGA based GPIO"
297 Support for common GPIO functionality provided on some GE Single Board
300 This driver provides basic support (configure as input or output, read
301 and write pin state) for GPIO implemented in a number of GE single
304 config GPIO_LYNXPOINT
305 bool "Intel Lynxpoint GPIO support"
306 depends on ACPI && X86
309 driver for GPIO functionality on Intel Lynxpoint PCH chipset
310 Requires ACPI device enumeration code to set up a platform device.
313 tristate "Aeroflex Gaisler GRGPIO support"
318 Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
319 VHDL IP core library.
321 comment "I2C GPIO expanders:"
324 tristate "Wolfson Microelectronics Arizona class devices"
325 depends on MFD_ARIZONA
327 Support for GPIOs on Wolfson Arizona class devices.
330 tristate "Maxim MAX7300 GPIO expander"
334 GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
337 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
340 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
341 Port Expanders. Each IO port on these chips has a fixed role of
342 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
343 Input and Output (designed by 'P'). The combinations are listed
346 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
347 max7322 (4I4O), max7323 (4P4O)
349 16 bits: max7324 (8I8O), max7325 (8P8O),
350 max7326 (4I12O), max7327 (4P12O)
352 Board setup code must specify the model to use, and the start
353 number for these GPIOs.
355 config GPIO_MAX732X_IRQ
356 bool "Interrupt controller support for MAX732x"
357 depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
359 Say yes here to enable the max732x to be used as an interrupt
360 controller. It requires the driver to be built in the kernel.
362 config GPIO_MC9S08DZ60
363 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
364 depends on I2C=y && MACH_MX35_3DS
366 Select this to enable the MC9S08DZ60 GPIO driver
369 tristate "PCA953x, PCA955x, PCA957x, TCA64xx, and MAX7310 I/O ports"
372 Say yes here to provide access to several register-oriented
373 SMBus I/O expanders, made mostly by NXP or TI. Compatible
376 4 bits: pca9536, pca9537
378 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
379 pca9556, pca9557, pca9574, tca6408
381 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
384 config GPIO_PCA953X_IRQ
385 bool "Interrupt controller support for PCA953x"
386 depends on GPIO_PCA953X=y
388 Say yes here to enable the pca953x to be used as an interrupt
389 controller. It requires the driver to be built in the kernel.
392 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
396 Say yes here to provide access to most "quasi-bidirectional" I2C
397 GPIO expanders used for additional digital outputs or inputs.
398 Most of these parts are from NXP, though TI is a second source for
399 some of them. Compatible models include:
401 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
402 pca9670, pca9672, pca9674, pca9674a,
405 16 bits: pcf8575, pcf8575c, pca8575,
406 pca9671, pca9673, pca9675
408 Your board setup code will need to declare the expanders in
409 use, and assign numbers to the GPIOs they expose. Those GPIOs
410 can then be used from drivers and other kernel code, just like
411 other GPIOs, but only accessible from task contexts.
413 This driver provides an in-kernel interface to those GPIOs using
414 platform-neutral GPIO calls.
417 bool "RICOH RC5T583 GPIO"
418 depends on MFD_RC5T583
420 Select this option to enable GPIO driver for the Ricoh RC5T583
422 This driver provides the support for driving/reading the gpio pins
423 of RC5T583 device through standard gpio library.
426 bool "Semtech SX150x I2C GPIO expander"
430 Say yes here to provide support for Semtech SX150-series I2C
431 GPIO expanders. Compatible models include:
440 This enables support for the GPIOs found on the STMPE I/O
444 bool "XWAY STP GPIOs"
447 This enables support for the Serial To Parallel (STP) unit found on
448 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
449 that can be up to 24 bit. This peripheral is aimed at driving leds.
450 Some of the gpios/leds can be auto updated by the soc with dsl and
455 depends on MFD_TC3589X
457 This enables support for the GPIOs found on the TC3589X
461 tristate "TI TPS65912 GPIO"
462 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
464 This driver supports TPS65912 gpio chip
467 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
468 depends on TWL4030_CORE
470 Say yes here to access the GPIO signals of various multi-function
471 power management chips from Texas Instruments.
474 tristate "TWL6040 GPO"
475 depends on TWL6040_CORE
477 Say yes here to access the GPO signals of twl6040
478 audio chip from Texas Instruments.
481 tristate "WM831x GPIOs"
482 depends on MFD_WM831X
484 Say yes here to access the GPIO signals of WM831x power management
485 chips from Wolfson Microelectronics.
488 tristate "WM8350 GPIOs"
489 depends on MFD_WM8350
491 Say yes here to access the GPIO signals of WM8350 power management
492 chips from Wolfson Microelectronics.
495 tristate "WM8994 GPIOs"
496 depends on MFD_WM8994
498 Say yes here to access the GPIO signals of WM8994 audio hub
499 CODECs from Wolfson Microelectronics.
502 tristate "GPIO Support for ADP5520 PMIC"
503 depends on PMIC_ADP5520
505 This option enables support for on-chip GPIO found
506 on Analog Devices ADP5520 PMICs.
509 tristate "ADP5588 I2C GPIO expander"
512 This option enables support for 18 GPIOs found
513 on Analog Devices ADP5588 GPIO Expanders.
515 config GPIO_ADP5588_IRQ
516 bool "Interrupt controller support for ADP5588"
517 depends on GPIO_ADP5588=y
519 Say yes here to enable the adp5588 to be used as an interrupt
520 controller. It requires the driver to be built in the kernel.
523 tristate "Avionic Design N-bit GPIO expander"
524 depends on I2C && OF_GPIO
526 This option enables support for N GPIOs found on Avionic Design
527 I2C GPIO expanders. The register space will be extended by powers
528 of two, so the controller will need to accommodate for that. For
529 example: if a controller provides 48 pins, 6 registers will be
530 enough to represent all pins, but the driver will assume a
531 register layout for 64 pins (8 registers).
533 comment "PCI GPIO expanders:"
536 tristate "AMD CS5535/CS5536 GPIO support"
537 depends on PCI && X86 && MFD_CS5535
539 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
540 can be used for quite a number of things. The CS5535/6 is found on
541 AMD Geode and Lemote Yeeloong devices.
546 tristate "BT8XX GPIO abuser"
547 depends on PCI && VIDEO_BT848=n
549 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
550 as a cheap PCI GPIO card.
552 This chip can be found on Miro, Hauppauge and STB TV-cards.
554 The card needs to be physically altered for using it as a
555 GPIO card. For more information on how to build a GPIO card
556 from a BT8xx TV card, see the documentation file at
557 Documentation/bt8xxgpio.txt
562 tristate "AMD 8111 GPIO driver"
565 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
567 Note, that usually system firmware/ACPI handles GPIO pins on their
568 own and users might easily break their systems with uncarefull usage
574 bool "Intel Langwell/Penwell GPIO support"
575 depends on PCI && X86
578 Say Y here to support Intel Langwell/Penwell GPIO.
581 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
582 depends on PCI && X86
583 select GENERIC_IRQ_CHIP
585 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
586 which is an IOH(Input/Output Hub) for x86 embedded processor.
587 This driver can access PCH GPIO device.
589 This driver also can be used for LAPIS Semiconductor IOH(Input/
590 Output Hub), ML7223 and ML7831.
591 ML7223 IOH is for MP(Media Phone) use.
592 ML7831 IOH is for general purpose use.
593 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
594 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
597 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
599 select GENERIC_IRQ_CHIP
601 ML7213 is companion chip for Intel Atom E6xx series.
602 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
603 Hub) which is for IVI(In-Vehicle Infotainment) use.
604 This driver can access the IOH's GPIO device.
606 config GPIO_SODAVILLE
607 bool "Intel Sodaville GPIO support"
608 depends on X86 && PCI && OF
610 select GENERIC_IRQ_CHIP
612 Say Y here to support Intel Sodaville GPIO.
614 config GPIO_TIMBERDALE
615 bool "Support for timberdale GPIO IP"
616 depends on MFD_TIMBERDALE && HAS_IOMEM
618 Add support for the GPIO IP in the timberdale FPGA.
621 tristate "RDC R-321x GPIO support"
622 depends on PCI && GENERIC_HARDIRQS
626 Support for the RDC R321x SoC GPIOs over southbridge
627 PCI configuration space.
629 comment "SPI GPIO expanders:"
632 tristate "Maxim MAX7301 GPIO expander"
633 depends on SPI_MASTER
636 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
639 tristate "Microchip MCP23xxx I/O expander"
640 depends on SPI_MASTER || I2C
642 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
644 This provides a GPIO interface supporting inputs and outputs.
647 tristate "Freescale MC33880 high-side/low-side switch"
648 depends on SPI_MASTER
650 SPI driver for Freescale MC33880 high-side/low-side switch.
651 This provides GPIO interface supporting inputs and outputs.
654 tristate "74x164 serial-in/parallel-out 8-bits shift register"
655 depends on SPI_MASTER
657 Platform driver for 74x164 compatible serial-in/parallel-out
658 8-outputs shift registers. This driver can be used to provide access
659 to more gpio outputs.
661 comment "AC97 GPIO expanders:"
664 bool "Philips UCB1400 GPIO"
665 depends on UCB1400_CORE
667 This enables support for the Philips UCB1400 GPIO pins.
668 The UCB1400 is an AC97 audio codec.
670 comment "MODULbus GPIO expanders:"
673 tristate "Janz VMOD-TTL Digital IO Module"
674 depends on MFD_JANZ_CMODIO
676 This enables support for the Janz VMOD-TTL Digital IO module.
677 This driver provides support for driving the pins in output
678 mode only. Input mode is not supported.
681 bool "TI PALMAS series PMICs GPIO"
682 depends on MFD_PALMAS
684 Select this option to enable GPIO driver for the TI PALMAS
689 depends on MFD_TPS6586X
691 Select this option to enable GPIO driver for the TPS6586X
696 depends on MFD_TPS65910
698 Select this option to enable GPIO driver for the TPS65910
702 bool "Intel MSIC mixed signal gpio support"
703 depends on MFD_INTEL_MSIC
705 Enable support for GPIO on intel MSIC controllers found in
708 comment "USB GPIO expanders:"
710 config GPIO_VIPERBOARD
711 tristate "Viperboard GPIO a & b support"
712 depends on MFD_VIPERBOARD && USB
714 Say yes here to access the GPIO signals of Nano River
715 Technologies Viperboard. There are two GPIO chips on the
716 board: gpioa and gpiob.
717 See viperboard API specification and Nano
718 River Tech's viperboard.h for detailed meaning
719 of the module parameters.