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
206 config GPIO_SPEAR_SPICS
207 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
208 depends on PLAT_SPEAR
209 select GENERIC_IRQ_CHIP
211 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
214 bool "STA2x11/ConneXt GPIO support"
215 depends on MFD_STA2X11
216 select GENERIC_IRQ_CHIP
218 Say yes here to support the STA2x11/ConneXt GPIO device.
219 The GPIO module has 128 GPIO pins with alternate functions.
222 tristate "TS-5500 DIO blocks and compatibles"
224 This driver supports Digital I/O exposed by pin blocks found on some
225 Technologic Systems platforms. It includes, but is not limited to, 3
226 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
230 bool "VIA/Wondermedia SoC GPIO Support"
231 depends on ARCH_VT8500
233 Say yes here to support the VT8500/WM8505/WM8650 GPIO controller.
236 bool "Xilinx GPIO support"
237 depends on PPC_OF || MICROBLAZE
239 Say yes here to support the Xilinx FPGA GPIO device
242 tristate "NEC VR4100 series General-purpose I/O Uint support"
243 depends on CPU_VR41XX
245 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
248 tristate "Intel SCH/TunnelCreek/Centerton GPIO"
249 depends on PCI && X86
253 Say yes here to support GPIO interface on Intel Poulsbo SCH,
254 Intel Tunnel Creek processor or Intel Centerton processor.
255 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
256 powered by the core power rail and are turned off during sleep
257 modes (S3 and higher). The remaining four GPIOs are powered by
258 the Intel SCH suspend power supply. These GPIOs remain
259 active during S3. The suspend powered GPIOs can be used to wake the
260 system from the Suspend-to-RAM state.
261 The Intel Tunnel Creek processor has 5 GPIOs powered by the
262 core power rail and 9 from suspend power supply.
263 The Intel Centerton processor has a total of 30 GPIO pins.
264 Twenty-one are powered by the core power rail and 9 from the
265 suspend power supply.
268 tristate "Intel ICH GPIO"
269 depends on PCI && X86
273 Say yes here to support the GPIO functionality of a number of Intel
274 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
275 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
276 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
281 tristate "VIA VX855/VX875 GPIO"
282 depends on PCI && GENERIC_HARDIRQS
286 Support access to the VX855/VX875 GPIO lines through the gpio library.
288 This driver provides common support for accessing the device,
289 additional drivers must be enabled in order to use the
290 functionality of the device.
293 bool "GE FPGA based GPIO"
296 Support for common GPIO functionality provided on some GE Single Board
299 This driver provides basic support (configure as input or output, read
300 and write pin state) for GPIO implemented in a number of GE single
303 config GPIO_LYNXPOINT
304 bool "Intel Lynxpoint GPIO support"
308 driver for GPIO functionality on Intel Lynxpoint PCH chipset
309 Requires ACPI device enumeration code to set up a platform device.
311 comment "I2C GPIO expanders:"
314 tristate "Wolfson Microelectronics Arizona class devices"
315 depends on MFD_ARIZONA
317 Support for GPIOs on Wolfson Arizona class devices.
320 tristate "Maxim MAX7300 GPIO expander"
324 GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
327 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
330 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
331 Port Expanders. Each IO port on these chips has a fixed role of
332 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
333 Input and Output (designed by 'P'). The combinations are listed
336 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
337 max7322 (4I4O), max7323 (4P4O)
339 16 bits: max7324 (8I8O), max7325 (8P8O),
340 max7326 (4I12O), max7327 (4P12O)
342 Board setup code must specify the model to use, and the start
343 number for these GPIOs.
345 config GPIO_MAX732X_IRQ
346 bool "Interrupt controller support for MAX732x"
347 depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
349 Say yes here to enable the max732x to be used as an interrupt
350 controller. It requires the driver to be built in the kernel.
352 config GPIO_MC9S08DZ60
353 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
354 depends on I2C=y && MACH_MX35_3DS
356 Select this to enable the MC9S08DZ60 GPIO driver
359 tristate "PCA953x, PCA955x, PCA957x, TCA64xx, and MAX7310 I/O ports"
362 Say yes here to provide access to several register-oriented
363 SMBus I/O expanders, made mostly by NXP or TI. Compatible
366 4 bits: pca9536, pca9537
368 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
369 pca9556, pca9557, pca9574, tca6408
371 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
374 config GPIO_PCA953X_IRQ
375 bool "Interrupt controller support for PCA953x"
376 depends on GPIO_PCA953X=y
378 Say yes here to enable the pca953x to be used as an interrupt
379 controller. It requires the driver to be built in the kernel.
382 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
386 Say yes here to provide access to most "quasi-bidirectional" I2C
387 GPIO expanders used for additional digital outputs or inputs.
388 Most of these parts are from NXP, though TI is a second source for
389 some of them. Compatible models include:
391 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
392 pca9670, pca9672, pca9674, pca9674a,
395 16 bits: pcf8575, pcf8575c, pca8575,
396 pca9671, pca9673, pca9675
398 Your board setup code will need to declare the expanders in
399 use, and assign numbers to the GPIOs they expose. Those GPIOs
400 can then be used from drivers and other kernel code, just like
401 other GPIOs, but only accessible from task contexts.
403 This driver provides an in-kernel interface to those GPIOs using
404 platform-neutral GPIO calls.
407 bool "RICOH RC5T583 GPIO"
408 depends on MFD_RC5T583
410 Select this option to enable GPIO driver for the Ricoh RC5T583
412 This driver provides the support for driving/reading the gpio pins
413 of RC5T583 device through standard gpio library.
416 bool "Semtech SX150x I2C GPIO expander"
420 Say yes here to provide support for Semtech SX150-series I2C
421 GPIO expanders. Compatible models include:
430 This enables support for the GPIOs found on the STMPE I/O
434 bool "XWAY STP GPIOs"
437 This enables support for the Serial To Parallel (STP) unit found on
438 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
439 that can be up to 24 bit. This peripheral is aimed at driving leds.
440 Some of the gpios/leds can be auto updated by the soc with dsl and
445 depends on MFD_TC3589X
447 This enables support for the GPIOs found on the TC3589X
451 tristate "TI TPS65912 GPIO"
452 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
454 This driver supports TPS65912 gpio chip
457 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
458 depends on TWL4030_CORE
460 Say yes here to access the GPIO signals of various multi-function
461 power management chips from Texas Instruments.
464 tristate "TWL6040 GPO"
465 depends on TWL6040_CORE
467 Say yes here to access the GPO signals of twl6040
468 audio chip from Texas Instruments.
471 tristate "WM831x GPIOs"
472 depends on MFD_WM831X
474 Say yes here to access the GPIO signals of WM831x power management
475 chips from Wolfson Microelectronics.
478 tristate "WM8350 GPIOs"
479 depends on MFD_WM8350
481 Say yes here to access the GPIO signals of WM8350 power management
482 chips from Wolfson Microelectronics.
485 tristate "WM8994 GPIOs"
486 depends on MFD_WM8994
488 Say yes here to access the GPIO signals of WM8994 audio hub
489 CODECs from Wolfson Microelectronics.
492 tristate "GPIO Support for ADP5520 PMIC"
493 depends on PMIC_ADP5520
495 This option enables support for on-chip GPIO found
496 on Analog Devices ADP5520 PMICs.
499 tristate "ADP5588 I2C GPIO expander"
502 This option enables support for 18 GPIOs found
503 on Analog Devices ADP5588 GPIO Expanders.
505 config GPIO_ADP5588_IRQ
506 bool "Interrupt controller support for ADP5588"
507 depends on GPIO_ADP5588=y
509 Say yes here to enable the adp5588 to be used as an interrupt
510 controller. It requires the driver to be built in the kernel.
513 tristate "Avionic Design N-bit GPIO expander"
514 depends on I2C && OF_GPIO
516 This option enables support for N GPIOs found on Avionic Design
517 I2C GPIO expanders. The register space will be extended by powers
518 of two, so the controller will need to accommodate for that. For
519 example: if a controller provides 48 pins, 6 registers will be
520 enough to represent all pins, but the driver will assume a
521 register layout for 64 pins (8 registers).
523 comment "PCI GPIO expanders:"
526 tristate "AMD CS5535/CS5536 GPIO support"
527 depends on PCI && X86 && MFD_CS5535
529 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
530 can be used for quite a number of things. The CS5535/6 is found on
531 AMD Geode and Lemote Yeeloong devices.
536 tristate "BT8XX GPIO abuser"
537 depends on PCI && VIDEO_BT848=n
539 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
540 as a cheap PCI GPIO card.
542 This chip can be found on Miro, Hauppauge and STB TV-cards.
544 The card needs to be physically altered for using it as a
545 GPIO card. For more information on how to build a GPIO card
546 from a BT8xx TV card, see the documentation file at
547 Documentation/bt8xxgpio.txt
552 tristate "AMD 8111 GPIO driver"
555 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
557 Note, that usually system firmware/ACPI handles GPIO pins on their
558 own and users might easily break their systems with uncarefull usage
564 bool "Intel Langwell/Penwell GPIO support"
565 depends on PCI && X86
568 Say Y here to support Intel Langwell/Penwell GPIO.
571 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
572 depends on PCI && X86
573 select GENERIC_IRQ_CHIP
575 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
576 which is an IOH(Input/Output Hub) for x86 embedded processor.
577 This driver can access PCH GPIO device.
579 This driver also can be used for LAPIS Semiconductor IOH(Input/
580 Output Hub), ML7223 and ML7831.
581 ML7223 IOH is for MP(Media Phone) use.
582 ML7831 IOH is for general purpose use.
583 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
584 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
587 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
589 select GENERIC_IRQ_CHIP
591 ML7213 is companion chip for Intel Atom E6xx series.
592 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
593 Hub) which is for IVI(In-Vehicle Infotainment) use.
594 This driver can access the IOH's GPIO device.
596 config GPIO_SODAVILLE
597 bool "Intel Sodaville GPIO support"
598 depends on X86 && PCI && OF
600 select GENERIC_IRQ_CHIP
602 Say Y here to support Intel Sodaville GPIO.
604 config GPIO_TIMBERDALE
605 bool "Support for timberdale GPIO IP"
606 depends on MFD_TIMBERDALE && HAS_IOMEM
608 Add support for the GPIO IP in the timberdale FPGA.
611 tristate "RDC R-321x GPIO support"
612 depends on PCI && GENERIC_HARDIRQS
616 Support for the RDC R321x SoC GPIOs over southbridge
617 PCI configuration space.
619 comment "SPI GPIO expanders:"
622 tristate "Maxim MAX7301 GPIO expander"
623 depends on SPI_MASTER
626 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
629 tristate "Microchip MCP23xxx I/O expander"
630 depends on SPI_MASTER || I2C
632 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
634 This provides a GPIO interface supporting inputs and outputs.
637 tristate "Freescale MC33880 high-side/low-side switch"
638 depends on SPI_MASTER
640 SPI driver for Freescale MC33880 high-side/low-side switch.
641 This provides GPIO interface supporting inputs and outputs.
644 tristate "74x164 serial-in/parallel-out 8-bits shift register"
645 depends on SPI_MASTER
647 Platform driver for 74x164 compatible serial-in/parallel-out
648 8-outputs shift registers. This driver can be used to provide access
649 to more gpio outputs.
651 comment "AC97 GPIO expanders:"
654 bool "Philips UCB1400 GPIO"
655 depends on UCB1400_CORE
657 This enables support for the Philips UCB1400 GPIO pins.
658 The UCB1400 is an AC97 audio codec.
660 comment "MODULbus GPIO expanders:"
663 tristate "Janz VMOD-TTL Digital IO Module"
664 depends on MFD_JANZ_CMODIO
666 This enables support for the Janz VMOD-TTL Digital IO module.
667 This driver provides support for driving the pins in output
668 mode only. Input mode is not supported.
671 bool "TI PALMAS series PMICs GPIO"
672 depends on MFD_PALMAS
674 Select this option to enable GPIO driver for the TI PALMAS
679 depends on MFD_TPS6586X
681 Select this option to enable GPIO driver for the TPS6586X
686 depends on MFD_TPS65910
688 Select this option to enable GPIO driver for the TPS65910
692 bool "Intel MSIC mixed signal gpio support"
693 depends on MFD_INTEL_MSIC
695 Enable support for GPIO on intel MSIC controllers found in
698 comment "USB GPIO expanders:"
700 config GPIO_VIPERBOARD
701 tristate "Viperboard GPIO a & b support"
702 depends on MFD_VIPERBOARD && USB
704 Say yes here to access the GPIO signals of Nano River
705 Technologies Viperboard. There are two GPIO chips on the
706 board: gpioa and gpiob.
707 See viperboard API specification and Nano
708 River Tech's viperboard.h for detailed meaning
709 of the module parameters.