Select this config option from the architecture Kconfig, if it is possible to use gpiolib on the architecture, but let the user decide whether to actually build it or not. Select this instead of ARCH_REQUIRE_GPIOLIB, if your architecture does not depend on GPIOs being available, but rather let the user decide whether he needs it or not.
Platforms select gpiolib if they use this infrastructure for all their GPIOs, usually starting with ones integrated into SOC processors. Selecting this from the architecture code will cause the gpiolib code to always get built in.
This enables GPIO support through the generic GPIO library. You only need to enable this, if you also want to enable one or more of the GPIO drivers below. If unsure, say N.
Say Y here to add some extra checks and diagnostics to GPIO calls. These checks help ensure that GPIOs have been properly initialized before they are used, and that sleeping calls are not made from non-sleeping contexts. They can make bitbanged serial protocols slower. The diagnostics help catch the type of setup errors that are most common when setting up new platforms or boards.
Say Y here to add a sysfs interface for GPIOs. This is mostly useful to work around omissions in a system's kernel support. Those are common in custom and semicustom hardware assembled using standard kernels with a minimum of custom patches. In those cases, userspace code may import a given GPIO from the kernel, if no kernel driver requested it. Kernel drivers may also request that a particular GPIO be exported to userspace; this can be useful when debugging.
Provides core functionality for basic memory-mapped GPIO controllers.
Say yes here to support basic memory-mapped GPIO controllers.
Say yes here to support GPIO functionality of IT8761E super I/O chip.
Say yes here to support the PrimeCell PL061 GPIO device
Say yes here to support the Xilinx FPGA GPIO device
Say yes here to support the NEC VR4100 series General-purpose I/O Uint
Say yes here to support GPIO interface on Intel Poulsbo SCH or Intel Tunnel Creek processor. The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are powered by the core power rail and are turned off during sleep modes (S3 and higher). The remaining four GPIOs are powered by the Intel SCH suspend power supply. These GPIOs remain active during S3. The suspend powered GPIOs can be used to wake the system from the Suspend-to-RAM state. The Intel Tunnel Creek processor has 5 GPIOs powered by the core power rail and 9 from suspend power supply. This driver can also be built as a module. If so, the module will be called sch-gpio.
Support access to the VX855/VX875 GPIO lines through the gpio library. This driver provides common support for accessing the device, additional drivers must be enabled in order to use the functionality of the device.
GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
Say yes here to support the MAX7319, MAX7320-7327 series of I2C
Port Expanders. Each IO port on these chips has a fixed role of
Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
Input and Output (designed by 'P'). The combinations are listed
below:
8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
max7322 (4I4O), max7323 (4P4O)
16 bits: max7324 (8I8O), max7325 (8P8O),
max7326 (4I12O), max7327 (4P12O)
Board setup code must specify the model to use, and the start
number for these GPIOs.
Say yes here to enable the max732x to be used as an interrupt controller. It requires the driver to be built in the kernel.
Say yes here to provide access to several register-oriented SMBus I/O expanders, made mostly by NXP or TI. Compatible models include: 4 bits: pca9536, pca9537 8 bits: max7310, pca9534, pca9538, pca9554, pca9557, tca6408 16 bits: pca9535, pca9539, pca9555, tca6416 This driver can also be built as a module. If so, the module will be called pca953x.
Say yes here to enable the pca953x to be used as an interrupt controller. It requires the driver to be built in the kernel.
Say yes here to provide access to most "quasi-bidirectional" I2C GPIO expanders used for additional digital outputs or inputs. Most of these parts are from NXP, though TI is a second source for some of them. Compatible models include: 8 bits: pcf8574, pcf8574a, pca8574, pca8574a, pca9670, pca9672, pca9674, pca9674a, max7328, max7329 16 bits: pcf8575, pcf8575c, pca8575, pca9671, pca9673, pca9675 Your board setup code will need to declare the expanders in use, and assign numbers to the GPIOs they expose. Those GPIOs can then be used from drivers and other kernel code, just like other GPIOs, but only accessible from task contexts. This driver provides an in-kernel interface to those GPIOs using platform-neutral GPIO calls.
Say yes here to provide support for Semtech SX150-series I2C GPIO expanders. Compatible models include: 8 bits: sx1508q 16 bits: sx1509q
This enables support for the GPIOs found on the STMPE I/O Expanders.
This enables support for the GPIOs found on the TC3589X I/O Expander.
Say yes here to access the GPIO signals of various multi-function power management chips from Texas Instruments.
Say yes here to access the GPIO signals of WM831x power management chips from Wolfson Microelectronics.
Say yes here to access the GPIO signals of WM8350 power management chips from Wolfson Microelectronics.
Say yes here to access the GPIO signals of WM8994 audio hub CODECs from Wolfson Microelectronics.
This option enables support for on-chip GPIO found on Analog Devices ADP5520 PMICs. To compile this driver as a module, choose M here: the module will be called adp5520-gpio.
This option enables support for 18 GPIOs found on Analog Devices ADP5588 GPIO Expanders. To compile this driver as a module, choose M here: the module will be called adp5588-gpio.
Say yes here to enable the adp5588 to be used as an interrupt controller. It requires the driver to be built in the kernel.
The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that can be used for quite a number of things. The CS5535/6 is found on AMD Geode and Lemote Yeeloong devices. If unsure, say N.
The BT8xx frame grabber chip has 24 GPIO pins than can be abused as a cheap PCI GPIO card. This chip can be found on Miro, Hauppauge and STB TV-cards. The card needs to be physically altered for using it as a GPIO card. For more information on how to build a GPIO card from a BT8xx TV card, see the documentation file at Documentation/bt8xxgpio.txt If unsure, say N.
Say Y here to support Intel Langwell/Penwell GPIO.
This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded processor. This driver can access PCH GPIO device. This driver also can be used for OKI SEMICONDUCTOR IOH(Input/ Output Hub), ML7223. ML7223 IOH is for MP(Media Phone) use. ML7223 is companion chip for Intel Atom E6xx series. ML7223 is completely compatible for Intel EG20T PCH.
ML7213 is companion chip for Intel Atom E6xx series. This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output Hub) which is for IVI(In-Vehicle Infotainment) use. This driver can access the IOH's GPIO device.
Add support for the GPIO IP in the timberdale FPGA.
Support for the RDC R321x SoC GPIOs over southbridge PCI configuration space.
GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
SPI driver for Microchip MCP23S08/MPC23S17 I/O expanders. This provides a GPIO interface supporting inputs and outputs.
SPI driver for Freescale MC33880 high-side/low-side switch. This provides GPIO interface supporting inputs and outputs.
Platform driver for 74x164 compatible serial-in/parallel-out 8-outputs shift registers. This driver can be used to provide access to more gpio outputs.
This enables support for the Philips UCB1400 GPIO pins. The UCB1400 is an AC97 audio codec. To compile this driver as a module, choose M here: the module will be called ucb1400_gpio.
This enables support for the Janz VMOD-TTL Digital IO module. This driver provides support for driving the pins in output mode only. Input mode is not supported.
Select this to enable the AB8500 IC GPIO driver
Select this option to enable GPIO driver for the TPS65910 chip family.