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:"
113 depends on ARCH_CLPS711X
115 config GPIO_GENERIC_PLATFORM
116 tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
119 Say yes here to support basic platform_device memory-mapped GPIO controllers.
122 tristate "IT8761E GPIO support"
123 depends on X86 # unconditional access to IO space.
125 Say yes here to support GPIO functionality of IT8761E super I/O chip.
128 tristate "Emma Mobile GPIO"
131 Say yes here to support GPIO on Renesas Emma Mobile SoCs.
135 depends on ARCH_EP93XX
138 config GPIO_MM_LANTIQ
139 bool "Lantiq Memory mapped GPIOs"
140 depends on LANTIQ && SOC_XWAY
142 This enables support for memory mapped GPIOs on the External Bus Unit
143 (EBU) found on Lantiq SoCs. The gpios are output only as they are
144 created by attaching a 16bit latch to the bus.
148 depends on PPC_MPC52xx
151 bool "MPC512x/MPC8xxx GPIO support"
152 depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \
153 FSL_SOC_BOOKE || PPC_86xx
155 Say Y here if you're going to use hardware that connects to the
156 MPC512x/831x/834x/837x/8572/8610 GPIOs.
159 tristate "Qualcomm MSM GPIO v1"
160 depends on GPIOLIB && ARCH_MSM && (ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50)
162 Say yes here to support the GPIO interface on ARM v6 based
163 Qualcomm MSM chips. Most of the pins on the MSM can be
164 selected for GPIO, and are controlled by this driver.
167 tristate "Qualcomm MSM GPIO v2"
168 depends on GPIOLIB && ARCH_MSM
170 Say yes here to support the GPIO interface on ARM v7 based
171 Qualcomm MSM chips. Most of the pins on the MSM can be
172 selected for GPIO, and are controlled by this driver.
176 depends on PLAT_ORION
179 select GENERIC_IRQ_CHIP
185 select GENERIC_IRQ_CHIP
191 select GENERIC_IRQ_CHIP
194 bool "PrimeCell PL061 GPIO support"
195 depends on ARM && ARM_AMBA
196 select GENERIC_IRQ_CHIP
198 Say yes here to support the PrimeCell PL061 GPIO device
201 bool "PXA GPIO support"
202 depends on ARCH_PXA || ARCH_MMP
204 Say yes here to support the PXA GPIO device
207 tristate "Renesas R-Car GPIO"
210 Say yes here to support GPIO on Renesas R-Car SoCs.
213 bool "Richtek RT5025 GPIO support"
214 depends on MFD_RT5025
217 This is the gpio driver for RT5025 PMIC.
219 config GPIO_SPEAR_SPICS
220 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
221 depends on PLAT_SPEAR
222 select GENERIC_IRQ_CHIP
224 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
227 bool "STA2x11/ConneXt GPIO support"
228 depends on MFD_STA2X11
229 select GENERIC_IRQ_CHIP
231 Say yes here to support the STA2x11/ConneXt GPIO device.
232 The GPIO module has 128 GPIO pins with alternate functions.
235 tristate "TS-5500 DIO blocks and compatibles"
237 This driver supports Digital I/O exposed by pin blocks found on some
238 Technologic Systems platforms. It includes, but is not limited to, 3
239 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
243 bool "Xilinx GPIO support"
244 depends on PPC_OF || MICROBLAZE
246 Say yes here to support the Xilinx FPGA GPIO device
249 tristate "NEC VR4100 series General-purpose I/O Uint support"
250 depends on CPU_VR41XX
252 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
255 tristate "Intel SCH/TunnelCreek/Centerton GPIO"
256 depends on PCI && X86
260 Say yes here to support GPIO interface on Intel Poulsbo SCH,
261 Intel Tunnel Creek processor or Intel Centerton processor.
262 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
263 powered by the core power rail and are turned off during sleep
264 modes (S3 and higher). The remaining four GPIOs are powered by
265 the Intel SCH suspend power supply. These GPIOs remain
266 active during S3. The suspend powered GPIOs can be used to wake the
267 system from the Suspend-to-RAM state.
268 The Intel Tunnel Creek processor has 5 GPIOs powered by the
269 core power rail and 9 from suspend power supply.
270 The Intel Centerton processor has a total of 30 GPIO pins.
271 Twenty-one are powered by the core power rail and 9 from the
272 suspend power supply.
275 tristate "Intel ICH GPIO"
276 depends on PCI && X86
280 Say yes here to support the GPIO functionality of a number of Intel
281 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
282 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
283 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
288 tristate "VIA VX855/VX875 GPIO"
289 depends on PCI && GENERIC_HARDIRQS
293 Support access to the VX855/VX875 GPIO lines through the gpio library.
295 This driver provides common support for accessing the device,
296 additional drivers must be enabled in order to use the
297 functionality of the device.
300 bool "GE FPGA based GPIO"
303 Support for common GPIO functionality provided on some GE Single Board
306 This driver provides basic support (configure as input or output, read
307 and write pin state) for GPIO implemented in a number of GE single
310 config GPIO_LYNXPOINT
311 bool "Intel Lynxpoint GPIO support"
312 depends on ACPI && X86
315 driver for GPIO functionality on Intel Lynxpoint PCH chipset
316 Requires ACPI device enumeration code to set up a platform device.
319 tristate "Aeroflex Gaisler GRGPIO support"
324 Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
325 VHDL IP core library.
327 comment "I2C GPIO expanders:"
330 tristate "Wolfson Microelectronics Arizona class devices"
331 depends on MFD_ARIZONA
333 Support for GPIOs on Wolfson Arizona class devices.
336 tristate "Maxim MAX7300 GPIO expander"
340 GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
343 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
346 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
347 Port Expanders. Each IO port on these chips has a fixed role of
348 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
349 Input and Output (designed by 'P'). The combinations are listed
352 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
353 max7322 (4I4O), max7323 (4P4O)
355 16 bits: max7324 (8I8O), max7325 (8P8O),
356 max7326 (4I12O), max7327 (4P12O)
358 Board setup code must specify the model to use, and the start
359 number for these GPIOs.
361 config GPIO_MAX732X_IRQ
362 bool "Interrupt controller support for MAX732x"
363 depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
365 Say yes here to enable the max732x to be used as an interrupt
366 controller. It requires the driver to be built in the kernel.
368 config GPIO_MC9S08DZ60
369 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
370 depends on I2C=y && MACH_MX35_3DS
372 Select this to enable the MC9S08DZ60 GPIO driver
375 tristate "PCA953x, PCA955x, PCA957x, TCA64xx, and MAX7310 I/O ports"
378 Say yes here to provide access to several register-oriented
379 SMBus I/O expanders, made mostly by NXP or TI. Compatible
382 4 bits: pca9536, pca9537
384 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
385 pca9556, pca9557, pca9574, tca6408
387 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
390 config GPIO_PCA953X_IRQ
391 bool "Interrupt controller support for PCA953x"
392 depends on GPIO_PCA953X=y
394 Say yes here to enable the pca953x to be used as an interrupt
395 controller. It requires the driver to be built in the kernel.
398 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
402 Say yes here to provide access to most "quasi-bidirectional" I2C
403 GPIO expanders used for additional digital outputs or inputs.
404 Most of these parts are from NXP, though TI is a second source for
405 some of them. Compatible models include:
407 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
408 pca9670, pca9672, pca9674, pca9674a,
411 16 bits: pcf8575, pcf8575c, pca8575,
412 pca9671, pca9673, pca9675
414 Your board setup code will need to declare the expanders in
415 use, and assign numbers to the GPIOs they expose. Those GPIOs
416 can then be used from drivers and other kernel code, just like
417 other GPIOs, but only accessible from task contexts.
419 This driver provides an in-kernel interface to those GPIOs using
420 platform-neutral GPIO calls.
423 bool "RICOH RC5T583 GPIO"
424 depends on MFD_RC5T583
426 Select this option to enable GPIO driver for the Ricoh RC5T583
428 This driver provides the support for driving/reading the gpio pins
429 of RC5T583 device through standard gpio library.
432 bool "Semtech SX150x I2C GPIO expander"
436 Say yes here to provide support for Semtech SX150-series I2C
437 GPIO expanders. Compatible models include:
446 This enables support for the GPIOs found on the STMPE I/O
450 bool "XWAY STP GPIOs"
453 This enables support for the Serial To Parallel (STP) unit found on
454 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
455 that can be up to 24 bit. This peripheral is aimed at driving leds.
456 Some of the gpios/leds can be auto updated by the soc with dsl and
461 depends on MFD_TC3589X
463 This enables support for the GPIOs found on the TC3589X
467 tristate "TI TPS65912 GPIO"
468 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
470 This driver supports TPS65912 gpio chip
473 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
474 depends on TWL4030_CORE
476 Say yes here to access the GPIO signals of various multi-function
477 power management chips from Texas Instruments.
480 tristate "TWL6040 GPO"
481 depends on TWL6040_CORE
483 Say yes here to access the GPO signals of twl6040
484 audio chip from Texas Instruments.
487 tristate "WM831x GPIOs"
488 depends on MFD_WM831X
490 Say yes here to access the GPIO signals of WM831x power management
491 chips from Wolfson Microelectronics.
494 tristate "WM8350 GPIOs"
495 depends on MFD_WM8350
497 Say yes here to access the GPIO signals of WM8350 power management
498 chips from Wolfson Microelectronics.
501 tristate "WM8994 GPIOs"
502 depends on MFD_WM8994
504 Say yes here to access the GPIO signals of WM8994 audio hub
505 CODECs from Wolfson Microelectronics.
508 tristate "GPIO Support for ADP5520 PMIC"
509 depends on PMIC_ADP5520
511 This option enables support for on-chip GPIO found
512 on Analog Devices ADP5520 PMICs.
515 tristate "ADP5588 I2C GPIO expander"
518 This option enables support for 18 GPIOs found
519 on Analog Devices ADP5588 GPIO Expanders.
521 config GPIO_ADP5588_IRQ
522 bool "Interrupt controller support for ADP5588"
523 depends on GPIO_ADP5588=y
525 Say yes here to enable the adp5588 to be used as an interrupt
526 controller. It requires the driver to be built in the kernel.
529 tristate "Avionic Design N-bit GPIO expander"
530 depends on I2C && OF_GPIO
532 This option enables support for N GPIOs found on Avionic Design
533 I2C GPIO expanders. The register space will be extended by powers
534 of two, so the controller will need to accommodate for that. For
535 example: if a controller provides 48 pins, 6 registers will be
536 enough to represent all pins, but the driver will assume a
537 register layout for 64 pins (8 registers).
539 comment "PCI GPIO expanders:"
542 tristate "AMD CS5535/CS5536 GPIO support"
543 depends on PCI && X86 && MFD_CS5535
545 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
546 can be used for quite a number of things. The CS5535/6 is found on
547 AMD Geode and Lemote Yeeloong devices.
552 tristate "BT8XX GPIO abuser"
553 depends on PCI && VIDEO_BT848=n
555 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
556 as a cheap PCI GPIO card.
558 This chip can be found on Miro, Hauppauge and STB TV-cards.
560 The card needs to be physically altered for using it as a
561 GPIO card. For more information on how to build a GPIO card
562 from a BT8xx TV card, see the documentation file at
563 Documentation/bt8xxgpio.txt
568 tristate "AMD 8111 GPIO driver"
571 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
573 Note, that usually system firmware/ACPI handles GPIO pins on their
574 own and users might easily break their systems with uncarefull usage
580 bool "Intel Langwell/Penwell GPIO support"
581 depends on PCI && X86
584 Say Y here to support Intel Langwell/Penwell GPIO.
587 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
588 depends on PCI && X86
589 select GENERIC_IRQ_CHIP
591 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
592 which is an IOH(Input/Output Hub) for x86 embedded processor.
593 This driver can access PCH GPIO device.
595 This driver also can be used for LAPIS Semiconductor IOH(Input/
596 Output Hub), ML7223 and ML7831.
597 ML7223 IOH is for MP(Media Phone) use.
598 ML7831 IOH is for general purpose use.
599 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
600 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
603 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
605 select GENERIC_IRQ_CHIP
607 ML7213 is companion chip for Intel Atom E6xx series.
608 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
609 Hub) which is for IVI(In-Vehicle Infotainment) use.
610 This driver can access the IOH's GPIO device.
612 config GPIO_SODAVILLE
613 bool "Intel Sodaville GPIO support"
614 depends on X86 && PCI && OF
616 select GENERIC_IRQ_CHIP
618 Say Y here to support Intel Sodaville GPIO.
620 config GPIO_TIMBERDALE
621 bool "Support for timberdale GPIO IP"
622 depends on MFD_TIMBERDALE && HAS_IOMEM
624 Add support for the GPIO IP in the timberdale FPGA.
627 tristate "RDC R-321x GPIO support"
628 depends on PCI && GENERIC_HARDIRQS
632 Support for the RDC R321x SoC GPIOs over southbridge
633 PCI configuration space.
635 comment "SPI GPIO expanders:"
638 tristate "Maxim MAX7301 GPIO expander"
639 depends on SPI_MASTER
642 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
645 tristate "Microchip MCP23xxx I/O expander"
646 depends on (SPI_MASTER && !I2C) || I2C
648 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
650 This provides a GPIO interface supporting inputs and outputs.
653 tristate "Freescale MC33880 high-side/low-side switch"
654 depends on SPI_MASTER
656 SPI driver for Freescale MC33880 high-side/low-side switch.
657 This provides GPIO interface supporting inputs and outputs.
660 tristate "74x164 serial-in/parallel-out 8-bits shift register"
661 depends on SPI_MASTER
663 Platform driver for 74x164 compatible serial-in/parallel-out
664 8-outputs shift registers. This driver can be used to provide access
665 to more gpio outputs.
667 comment "AC97 GPIO expanders:"
670 bool "Philips UCB1400 GPIO"
671 depends on UCB1400_CORE
673 This enables support for the Philips UCB1400 GPIO pins.
674 The UCB1400 is an AC97 audio codec.
676 comment "MODULbus GPIO expanders:"
679 tristate "Janz VMOD-TTL Digital IO Module"
680 depends on MFD_JANZ_CMODIO
682 This enables support for the Janz VMOD-TTL Digital IO module.
683 This driver provides support for driving the pins in output
684 mode only. Input mode is not supported.
687 bool "TI PALMAS series PMICs GPIO"
688 depends on MFD_PALMAS
690 Select this option to enable GPIO driver for the TI PALMAS
695 depends on MFD_TPS6586X
697 Select this option to enable GPIO driver for the TPS6586X
702 depends on MFD_TPS65910
704 Select this option to enable GPIO driver for the TPS65910
708 bool "Intel MSIC mixed signal gpio support"
709 depends on MFD_INTEL_MSIC
711 Enable support for GPIO on intel MSIC controllers found in
714 comment "USB GPIO expanders:"
716 config GPIO_VIPERBOARD
717 tristate "Viperboard GPIO a & b support"
718 depends on MFD_VIPERBOARD && USB
720 Say yes here to access the GPIO signals of Nano River
721 Technologies Viperboard. There are two GPIO chips on the
722 board: gpioa and gpiob.
723 See viperboard API specification and Nano
724 River Tech's viperboard.h for detailed meaning
725 of the module parameters.