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.
90 bool "Samsung Exynos4 GPIO library support"
91 default y if CPU_EXYNOS4210
94 Say yes here to support Samsung Exynos4 series SoCs GPIO library
103 select GPIO_BASIC_MMIO_CORE
105 config GPIO_PLAT_SAMSUNG
106 bool "Samsung SoCs GPIO library support"
107 default y if SAMSUNG_GPIOLIB_4BIT
110 Say yes here to support Samsung SoCs GPIO library
113 bool "Samsung S5PC100 GPIO library support"
114 default y if CPU_S5PC100
117 Say yes here to support Samsung S5PC100 SoCs GPIO library
120 bool "Samsung S5PV210/S5PC110 GPIO library support"
121 default y if CPU_S5PV210
124 Say yes here to support Samsung S5PV210/S5PC110 SoCs GPIO library
127 bool "PrimeCell PL061 GPIO support"
130 Say yes here to support the PrimeCell PL061 GPIO device
133 bool "Xilinx GPIO support"
134 depends on PPC_OF || MICROBLAZE
136 Say yes here to support the Xilinx FPGA GPIO device
139 tristate "NEC VR4100 series General-purpose I/O Uint support"
140 depends on CPU_VR41XX
142 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
145 tristate "Intel SCH/TunnelCreek GPIO"
146 depends on PCI && X86
150 Say yes here to support GPIO interface on Intel Poulsbo SCH
151 or Intel Tunnel Creek processor.
152 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
153 powered by the core power rail and are turned off during sleep
154 modes (S3 and higher). The remaining four GPIOs are powered by
155 the Intel SCH suspend power supply. These GPIOs remain
156 active during S3. The suspend powered GPIOs can be used to wake the
157 system from the Suspend-to-RAM state.
158 The Intel Tunnel Creek processor has 5 GPIOs powered by the
159 core power rail and 9 from suspend power supply.
161 This driver can also be built as a module. If so, the module
162 will be called sch-gpio.
165 tristate "VIA VX855/VX875 GPIO"
166 depends on MFD_SUPPORT && PCI
170 Support access to the VX855/VX875 GPIO lines through the gpio library.
172 This driver provides common support for accessing the device,
173 additional drivers must be enabled in order to use the
174 functionality of the device.
176 comment "I2C GPIO expanders:"
179 tristate "Maxim MAX7300 GPIO expander"
183 GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
186 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
189 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
190 Port Expanders. Each IO port on these chips has a fixed role of
191 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
192 Input and Output (designed by 'P'). The combinations are listed
195 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
196 max7322 (4I4O), max7323 (4P4O)
198 16 bits: max7324 (8I8O), max7325 (8P8O),
199 max7326 (4I12O), max7327 (4P12O)
201 Board setup code must specify the model to use, and the start
202 number for these GPIOs.
204 config GPIO_MAX732X_IRQ
205 bool "Interrupt controller support for MAX732x"
206 depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
208 Say yes here to enable the max732x to be used as an interrupt
209 controller. It requires the driver to be built in the kernel.
212 tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports"
215 Say yes here to provide access to several register-oriented
216 SMBus I/O expanders, made mostly by NXP or TI. Compatible
219 4 bits: pca9536, pca9537
221 8 bits: max7310, pca9534, pca9538, pca9554, pca9557,
224 16 bits: pca9535, pca9539, pca9555, tca6416
226 This driver can also be built as a module. If so, the module
227 will be called pca953x.
229 config GPIO_PCA953X_IRQ
230 bool "Interrupt controller support for PCA953x"
231 depends on GPIO_PCA953X=y
233 Say yes here to enable the pca953x to be used as an interrupt
234 controller. It requires the driver to be built in the kernel.
237 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
240 Say yes here to provide access to most "quasi-bidirectional" I2C
241 GPIO expanders used for additional digital outputs or inputs.
242 Most of these parts are from NXP, though TI is a second source for
243 some of them. Compatible models include:
245 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
246 pca9670, pca9672, pca9674, pca9674a,
249 16 bits: pcf8575, pcf8575c, pca8575,
250 pca9671, pca9673, pca9675
252 Your board setup code will need to declare the expanders in
253 use, and assign numbers to the GPIOs they expose. Those GPIOs
254 can then be used from drivers and other kernel code, just like
255 other GPIOs, but only accessible from task contexts.
257 This driver provides an in-kernel interface to those GPIOs using
258 platform-neutral GPIO calls.
261 bool "Semtech SX150x I2C GPIO expander"
265 Say yes here to provide support for Semtech SX150-series I2C
266 GPIO expanders. Compatible models include:
275 This enables support for the GPIOs found on the STMPE I/O
280 depends on MFD_TC3589X
282 This enables support for the GPIOs found on the TC3589X
286 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
287 depends on TWL4030_CORE
289 Say yes here to access the GPIO signals of various multi-function
290 power management chips from Texas Instruments.
293 tristate "WM831x GPIOs"
294 depends on MFD_WM831X
296 Say yes here to access the GPIO signals of WM831x power management
297 chips from Wolfson Microelectronics.
300 tristate "WM8350 GPIOs"
301 depends on MFD_WM8350
303 Say yes here to access the GPIO signals of WM8350 power management
304 chips from Wolfson Microelectronics.
307 tristate "WM8994 GPIOs"
308 depends on MFD_WM8994
310 Say yes here to access the GPIO signals of WM8994 audio hub
311 CODECs from Wolfson Microelectronics.
314 tristate "GPIO Support for ADP5520 PMIC"
315 depends on PMIC_ADP5520
317 This option enables support for on-chip GPIO found
318 on Analog Devices ADP5520 PMICs.
320 To compile this driver as a module, choose M here: the module will
321 be called adp5520-gpio.
324 tristate "ADP5588 I2C GPIO expander"
327 This option enables support for 18 GPIOs found
328 on Analog Devices ADP5588 GPIO Expanders.
329 To compile this driver as a module, choose M here: the module will be
332 config GPIO_ADP5588_IRQ
333 bool "Interrupt controller support for ADP5588"
334 depends on GPIO_ADP5588=y
336 Say yes here to enable the adp5588 to be used as an interrupt
337 controller. It requires the driver to be built in the kernel.
339 comment "PCI GPIO expanders:"
342 tristate "AMD CS5535/CS5536 GPIO support"
343 depends on PCI && X86 && !CS5535_GPIO && MFD_CS5535
345 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
346 can be used for quite a number of things. The CS5535/6 is found on
347 AMD Geode and Lemote Yeeloong devices.
352 tristate "BT8XX GPIO abuser"
353 depends on PCI && VIDEO_BT848=n
355 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
356 as a cheap PCI GPIO card.
358 This chip can be found on Miro, Hauppauge and STB TV-cards.
360 The card needs to be physically altered for using it as a
361 GPIO card. For more information on how to build a GPIO card
362 from a BT8xx TV card, see the documentation file at
363 Documentation/bt8xxgpio.txt
368 bool "Intel Langwell/Penwell GPIO support"
369 depends on PCI && X86
371 Say Y here to support Intel Langwell/Penwell GPIO.
374 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GPIO"
375 depends on PCI && X86
377 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
378 which is an IOH(Input/Output Hub) for x86 embedded processor.
379 This driver can access PCH GPIO device.
381 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
383 ML7223 IOH is for MP(Media Phone) use.
384 ML7223 is companion chip for Intel Atom E6xx series.
385 ML7223 is completely compatible for Intel EG20T PCH.
388 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
391 ML7213 is companion chip for Intel Atom E6xx series.
392 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
393 Hub) which is for IVI(In-Vehicle Infotainment) use.
394 This driver can access the IOH's GPIO device.
396 config GPIO_TIMBERDALE
397 bool "Support for timberdale GPIO IP"
398 depends on MFD_TIMBERDALE && HAS_IOMEM
400 Add support for the GPIO IP in the timberdale FPGA.
403 tristate "RDC R-321x GPIO support"
409 Support for the RDC R321x SoC GPIOs over southbridge
410 PCI configuration space.
412 comment "SPI GPIO expanders:"
415 tristate "Maxim MAX7301 GPIO expander"
416 depends on SPI_MASTER
419 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
422 tristate "Microchip MCP23Sxx I/O expander"
423 depends on SPI_MASTER
425 SPI driver for Microchip MCP23S08/MPC23S17 I/O expanders.
426 This provides a GPIO interface supporting inputs and outputs.
429 tristate "Freescale MC33880 high-side/low-side switch"
430 depends on SPI_MASTER
432 SPI driver for Freescale MC33880 high-side/low-side switch.
433 This provides GPIO interface supporting inputs and outputs.
436 tristate "74x164 serial-in/parallel-out 8-bits shift register"
437 depends on SPI_MASTER
439 Platform driver for 74x164 compatible serial-in/parallel-out
440 8-outputs shift registers. This driver can be used to provide access
441 to more gpio outputs.
443 comment "AC97 GPIO expanders:"
446 bool "Philips UCB1400 GPIO"
447 depends on UCB1400_CORE
449 This enables support for the Philips UCB1400 GPIO pins.
450 The UCB1400 is an AC97 audio codec.
452 To compile this driver as a module, choose M here: the
453 module will be called ucb1400_gpio.
455 comment "MODULbus GPIO expanders:"
458 tristate "Janz VMOD-TTL Digital IO Module"
459 depends on MFD_JANZ_CMODIO
461 This enables support for the Janz VMOD-TTL Digital IO module.
462 This driver provides support for driving the pins in output
463 mode only. Input mode is not supported.
466 bool "ST-Ericsson AB8500 Mixed Signal Circuit gpio functions"
467 depends on AB8500_CORE && BROKEN
469 Select this to enable the AB8500 IC GPIO driver
473 depends on MFD_TPS65910
475 Select this option to enable GPIO driver for the TPS65910