2 # GPIO infrastructure and drivers
5 config ARCH_WANT_OPTIONAL_GPIOLIB
8 Select this config option from the architecture Kconfig, if
9 it is possible to use gpiolib on the architecture, but let the
10 user decide whether to actually build it or not.
11 Select this instead of ARCH_REQUIRE_GPIOLIB, if your architecture does
12 not depend on GPIOs being available, but rather let the user
13 decide whether he needs it or not.
15 config ARCH_REQUIRE_GPIOLIB
19 Platforms select gpiolib if they use this infrastructure
20 for all their GPIOs, usually starting with ones integrated
22 Selecting this from the architecture code will cause the gpiolib
23 code to always get built in.
29 depends on ARCH_WANT_OPTIONAL_GPIOLIB || ARCH_REQUIRE_GPIOLIB
32 This enables GPIO support through the generic GPIO library.
33 You only need to enable this, if you also want to enable
34 one or more of the GPIO drivers below.
41 bool "Debug GPIO calls"
42 depends on DEBUG_KERNEL
44 Say Y here to add some extra checks and diagnostics to GPIO calls.
45 These checks help ensure that GPIOs have been properly initialized
46 before they are used, and that sleeping calls are not made from
47 non-sleeping contexts. They can make bitbanged serial protocols
48 slower. The diagnostics help catch the type of setup errors
49 that are most common when setting up new platforms or boards.
52 bool "/sys/class/gpio/... (sysfs interface)"
53 depends on SYSFS && EXPERIMENTAL
55 Say Y here to add a sysfs interface for GPIOs.
57 This is mostly useful to work around omissions in a system's
58 kernel support. Those are common in custom and semicustom
59 hardware assembled using standard kernels with a minimum of
60 custom patches. In those cases, userspace code may import
61 a given GPIO from the kernel, if no kernel driver requested it.
63 Kernel drivers may also request that a particular GPIO be
64 exported to userspace; this can be useful when debugging.
66 # put drivers in the right section, in alphabetical order
71 comment "Memory mapped GPIO drivers:"
73 config GPIO_BASIC_MMIO_CORE
76 Provides core functionality for basic memory-mapped GPIO controllers.
78 config GPIO_BASIC_MMIO
79 tristate "Basic memory-mapped GPIO controllers support"
80 select GPIO_BASIC_MMIO_CORE
82 Say yes here to support basic memory-mapped GPIO controllers.
85 tristate "IT8761E GPIO support"
87 Say yes here to support GPIO functionality of IT8761E super I/O chip.
91 depends on ARCH_EP93XX
95 depends on CPU_EXYNOS4210
97 config GPIO_PLAT_SAMSUNG
99 depends on SAMSUNG_GPIOLIB_4BIT
103 depends on CPU_S5PC100
107 depends on CPU_S5PV210
110 bool "PrimeCell PL061 GPIO support"
113 Say yes here to support the PrimeCell PL061 GPIO device
116 bool "Xilinx GPIO support"
117 depends on PPC_OF || MICROBLAZE
119 Say yes here to support the Xilinx FPGA GPIO device
122 tristate "NEC VR4100 series General-purpose I/O Uint support"
123 depends on CPU_VR41XX
125 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
128 tristate "Intel SCH/TunnelCreek GPIO"
129 depends on PCI && X86
133 Say yes here to support GPIO interface on Intel Poulsbo SCH
134 or Intel Tunnel Creek processor.
135 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
136 powered by the core power rail and are turned off during sleep
137 modes (S3 and higher). The remaining four GPIOs are powered by
138 the Intel SCH suspend power supply. These GPIOs remain
139 active during S3. The suspend powered GPIOs can be used to wake the
140 system from the Suspend-to-RAM state.
141 The Intel Tunnel Creek processor has 5 GPIOs powered by the
142 core power rail and 9 from suspend power supply.
144 This driver can also be built as a module. If so, the module
145 will be called sch-gpio.
148 tristate "VIA VX855/VX875 GPIO"
149 depends on MFD_SUPPORT && PCI
153 Support access to the VX855/VX875 GPIO lines through the gpio library.
155 This driver provides common support for accessing the device,
156 additional drivers must be enabled in order to use the
157 functionality of the device.
159 comment "I2C GPIO expanders:"
162 tristate "Maxim MAX7300 GPIO expander"
166 GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
169 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
172 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
173 Port Expanders. Each IO port on these chips has a fixed role of
174 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
175 Input and Output (designed by 'P'). The combinations are listed
178 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
179 max7322 (4I4O), max7323 (4P4O)
181 16 bits: max7324 (8I8O), max7325 (8P8O),
182 max7326 (4I12O), max7327 (4P12O)
184 Board setup code must specify the model to use, and the start
185 number for these GPIOs.
187 config GPIO_MAX732X_IRQ
188 bool "Interrupt controller support for MAX732x"
189 depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
191 Say yes here to enable the max732x to be used as an interrupt
192 controller. It requires the driver to be built in the kernel.
195 tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports"
198 Say yes here to provide access to several register-oriented
199 SMBus I/O expanders, made mostly by NXP or TI. Compatible
202 4 bits: pca9536, pca9537
204 8 bits: max7310, pca9534, pca9538, pca9554, pca9557,
207 16 bits: pca9535, pca9539, pca9555, tca6416
209 This driver can also be built as a module. If so, the module
210 will be called pca953x.
212 config GPIO_PCA953X_IRQ
213 bool "Interrupt controller support for PCA953x"
214 depends on GPIO_PCA953X=y
216 Say yes here to enable the pca953x to be used as an interrupt
217 controller. It requires the driver to be built in the kernel.
220 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
223 Say yes here to provide access to most "quasi-bidirectional" I2C
224 GPIO expanders used for additional digital outputs or inputs.
225 Most of these parts are from NXP, though TI is a second source for
226 some of them. Compatible models include:
228 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
229 pca9670, pca9672, pca9674, pca9674a,
232 16 bits: pcf8575, pcf8575c, pca8575,
233 pca9671, pca9673, pca9675
235 Your board setup code will need to declare the expanders in
236 use, and assign numbers to the GPIOs they expose. Those GPIOs
237 can then be used from drivers and other kernel code, just like
238 other GPIOs, but only accessible from task contexts.
240 This driver provides an in-kernel interface to those GPIOs using
241 platform-neutral GPIO calls.
244 bool "Semtech SX150x I2C GPIO expander"
248 Say yes here to provide support for Semtech SX150-series I2C
249 GPIO expanders. Compatible models include:
258 This enables support for the GPIOs found on the STMPE I/O
263 depends on MFD_TC3589X
265 This enables support for the GPIOs found on the TC3589X
269 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
270 depends on TWL4030_CORE
272 Say yes here to access the GPIO signals of various multi-function
273 power management chips from Texas Instruments.
276 tristate "WM831x GPIOs"
277 depends on MFD_WM831X
279 Say yes here to access the GPIO signals of WM831x power management
280 chips from Wolfson Microelectronics.
283 tristate "WM8350 GPIOs"
284 depends on MFD_WM8350
286 Say yes here to access the GPIO signals of WM8350 power management
287 chips from Wolfson Microelectronics.
290 tristate "WM8994 GPIOs"
291 depends on MFD_WM8994
293 Say yes here to access the GPIO signals of WM8994 audio hub
294 CODECs from Wolfson Microelectronics.
297 tristate "GPIO Support for ADP5520 PMIC"
298 depends on PMIC_ADP5520
300 This option enables support for on-chip GPIO found
301 on Analog Devices ADP5520 PMICs.
303 To compile this driver as a module, choose M here: the module will
304 be called adp5520-gpio.
307 tristate "ADP5588 I2C GPIO expander"
310 This option enables support for 18 GPIOs found
311 on Analog Devices ADP5588 GPIO Expanders.
312 To compile this driver as a module, choose M here: the module will be
315 config GPIO_ADP5588_IRQ
316 bool "Interrupt controller support for ADP5588"
317 depends on GPIO_ADP5588=y
319 Say yes here to enable the adp5588 to be used as an interrupt
320 controller. It requires the driver to be built in the kernel.
322 comment "PCI GPIO expanders:"
325 tristate "AMD CS5535/CS5536 GPIO support"
326 depends on PCI && X86 && !CS5535_GPIO && MFD_CS5535
328 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
329 can be used for quite a number of things. The CS5535/6 is found on
330 AMD Geode and Lemote Yeeloong devices.
335 tristate "BT8XX GPIO abuser"
336 depends on PCI && VIDEO_BT848=n
338 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
339 as a cheap PCI GPIO card.
341 This chip can be found on Miro, Hauppauge and STB TV-cards.
343 The card needs to be physically altered for using it as a
344 GPIO card. For more information on how to build a GPIO card
345 from a BT8xx TV card, see the documentation file at
346 Documentation/bt8xxgpio.txt
351 bool "Intel Langwell/Penwell GPIO support"
352 depends on PCI && X86
354 Say Y here to support Intel Langwell/Penwell GPIO.
357 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GPIO"
358 depends on PCI && X86
360 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
361 which is an IOH(Input/Output Hub) for x86 embedded processor.
362 This driver can access PCH GPIO device.
364 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
366 ML7223 IOH is for MP(Media Phone) use.
367 ML7223 is companion chip for Intel Atom E6xx series.
368 ML7223 is completely compatible for Intel EG20T PCH.
371 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
374 ML7213 is companion chip for Intel Atom E6xx series.
375 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
376 Hub) which is for IVI(In-Vehicle Infotainment) use.
377 This driver can access the IOH's GPIO device.
379 config GPIO_TIMBERDALE
380 bool "Support for timberdale GPIO IP"
381 depends on MFD_TIMBERDALE && HAS_IOMEM
383 Add support for the GPIO IP in the timberdale FPGA.
386 tristate "RDC R-321x GPIO support"
392 Support for the RDC R321x SoC GPIOs over southbridge
393 PCI configuration space.
395 comment "SPI GPIO expanders:"
398 tristate "Maxim MAX7301 GPIO expander"
399 depends on SPI_MASTER
402 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
405 tristate "Microchip MCP23Sxx I/O expander"
406 depends on SPI_MASTER
408 SPI driver for Microchip MCP23S08/MPC23S17 I/O expanders.
409 This provides a GPIO interface supporting inputs and outputs.
412 tristate "Freescale MC33880 high-side/low-side switch"
413 depends on SPI_MASTER
415 SPI driver for Freescale MC33880 high-side/low-side switch.
416 This provides GPIO interface supporting inputs and outputs.
419 tristate "74x164 serial-in/parallel-out 8-bits shift register"
420 depends on SPI_MASTER
422 Platform driver for 74x164 compatible serial-in/parallel-out
423 8-outputs shift registers. This driver can be used to provide access
424 to more gpio outputs.
426 comment "AC97 GPIO expanders:"
429 bool "Philips UCB1400 GPIO"
430 depends on UCB1400_CORE
432 This enables support for the Philips UCB1400 GPIO pins.
433 The UCB1400 is an AC97 audio codec.
435 To compile this driver as a module, choose M here: the
436 module will be called ucb1400_gpio.
438 comment "MODULbus GPIO expanders:"
441 tristate "Janz VMOD-TTL Digital IO Module"
442 depends on MFD_JANZ_CMODIO
444 This enables support for the Janz VMOD-TTL Digital IO module.
445 This driver provides support for driving the pins in output
446 mode only. Input mode is not supported.
449 bool "ST-Ericsson AB8500 Mixed Signal Circuit gpio functions"
450 depends on AB8500_CORE && BROKEN
452 Select this to enable the AB8500 IC GPIO driver
456 depends on MFD_TPS65910
458 Select this option to enable GPIO driver for the TPS65910