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 CPU_EXYNOS4210
93 config GPIO_PLAT_SAMSUNG
95 depends on SAMSUNG_GPIOLIB_4BIT
99 depends on CPU_S5PC100
103 depends on CPU_S5PV210
106 bool "PrimeCell PL061 GPIO support"
109 Say yes here to support the PrimeCell PL061 GPIO device
112 bool "Xilinx GPIO support"
113 depends on PPC_OF || MICROBLAZE
115 Say yes here to support the Xilinx FPGA GPIO device
118 tristate "NEC VR4100 series General-purpose I/O Uint support"
119 depends on CPU_VR41XX
121 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
124 tristate "Intel SCH/TunnelCreek GPIO"
125 depends on PCI && X86
129 Say yes here to support GPIO interface on Intel Poulsbo SCH
130 or Intel Tunnel Creek processor.
131 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
132 powered by the core power rail and are turned off during sleep
133 modes (S3 and higher). The remaining four GPIOs are powered by
134 the Intel SCH suspend power supply. These GPIOs remain
135 active during S3. The suspend powered GPIOs can be used to wake the
136 system from the Suspend-to-RAM state.
137 The Intel Tunnel Creek processor has 5 GPIOs powered by the
138 core power rail and 9 from suspend power supply.
140 This driver can also be built as a module. If so, the module
141 will be called sch-gpio.
144 tristate "VIA VX855/VX875 GPIO"
145 depends on MFD_SUPPORT && PCI
149 Support access to the VX855/VX875 GPIO lines through the gpio library.
151 This driver provides common support for accessing the device,
152 additional drivers must be enabled in order to use the
153 functionality of the device.
155 comment "I2C GPIO expanders:"
158 tristate "Maxim MAX7300 GPIO expander"
162 GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
165 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
168 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
169 Port Expanders. Each IO port on these chips has a fixed role of
170 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
171 Input and Output (designed by 'P'). The combinations are listed
174 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
175 max7322 (4I4O), max7323 (4P4O)
177 16 bits: max7324 (8I8O), max7325 (8P8O),
178 max7326 (4I12O), max7327 (4P12O)
180 Board setup code must specify the model to use, and the start
181 number for these GPIOs.
183 config GPIO_MAX732X_IRQ
184 bool "Interrupt controller support for MAX732x"
185 depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
187 Say yes here to enable the max732x to be used as an interrupt
188 controller. It requires the driver to be built in the kernel.
191 tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports"
194 Say yes here to provide access to several register-oriented
195 SMBus I/O expanders, made mostly by NXP or TI. Compatible
198 4 bits: pca9536, pca9537
200 8 bits: max7310, pca9534, pca9538, pca9554, pca9557,
203 16 bits: pca9535, pca9539, pca9555, tca6416
205 This driver can also be built as a module. If so, the module
206 will be called pca953x.
208 config GPIO_PCA953X_IRQ
209 bool "Interrupt controller support for PCA953x"
210 depends on GPIO_PCA953X=y
212 Say yes here to enable the pca953x to be used as an interrupt
213 controller. It requires the driver to be built in the kernel.
216 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
219 Say yes here to provide access to most "quasi-bidirectional" I2C
220 GPIO expanders used for additional digital outputs or inputs.
221 Most of these parts are from NXP, though TI is a second source for
222 some of them. Compatible models include:
224 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
225 pca9670, pca9672, pca9674, pca9674a,
228 16 bits: pcf8575, pcf8575c, pca8575,
229 pca9671, pca9673, pca9675
231 Your board setup code will need to declare the expanders in
232 use, and assign numbers to the GPIOs they expose. Those GPIOs
233 can then be used from drivers and other kernel code, just like
234 other GPIOs, but only accessible from task contexts.
236 This driver provides an in-kernel interface to those GPIOs using
237 platform-neutral GPIO calls.
240 bool "Semtech SX150x I2C GPIO expander"
244 Say yes here to provide support for Semtech SX150-series I2C
245 GPIO expanders. Compatible models include:
254 This enables support for the GPIOs found on the STMPE I/O
259 depends on MFD_TC3589X
261 This enables support for the GPIOs found on the TC3589X
265 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
266 depends on TWL4030_CORE
268 Say yes here to access the GPIO signals of various multi-function
269 power management chips from Texas Instruments.
272 tristate "WM831x GPIOs"
273 depends on MFD_WM831X
275 Say yes here to access the GPIO signals of WM831x power management
276 chips from Wolfson Microelectronics.
279 tristate "WM8350 GPIOs"
280 depends on MFD_WM8350
282 Say yes here to access the GPIO signals of WM8350 power management
283 chips from Wolfson Microelectronics.
286 tristate "WM8994 GPIOs"
287 depends on MFD_WM8994
289 Say yes here to access the GPIO signals of WM8994 audio hub
290 CODECs from Wolfson Microelectronics.
293 tristate "GPIO Support for ADP5520 PMIC"
294 depends on PMIC_ADP5520
296 This option enables support for on-chip GPIO found
297 on Analog Devices ADP5520 PMICs.
299 To compile this driver as a module, choose M here: the module will
300 be called adp5520-gpio.
303 tristate "ADP5588 I2C GPIO expander"
306 This option enables support for 18 GPIOs found
307 on Analog Devices ADP5588 GPIO Expanders.
308 To compile this driver as a module, choose M here: the module will be
311 config GPIO_ADP5588_IRQ
312 bool "Interrupt controller support for ADP5588"
313 depends on GPIO_ADP5588=y
315 Say yes here to enable the adp5588 to be used as an interrupt
316 controller. It requires the driver to be built in the kernel.
318 comment "PCI GPIO expanders:"
321 tristate "AMD CS5535/CS5536 GPIO support"
322 depends on PCI && X86 && !CS5535_GPIO && MFD_CS5535
324 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
325 can be used for quite a number of things. The CS5535/6 is found on
326 AMD Geode and Lemote Yeeloong devices.
331 tristate "BT8XX GPIO abuser"
332 depends on PCI && VIDEO_BT848=n
334 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
335 as a cheap PCI GPIO card.
337 This chip can be found on Miro, Hauppauge and STB TV-cards.
339 The card needs to be physically altered for using it as a
340 GPIO card. For more information on how to build a GPIO card
341 from a BT8xx TV card, see the documentation file at
342 Documentation/bt8xxgpio.txt
347 bool "Intel Langwell/Penwell GPIO support"
348 depends on PCI && X86
350 Say Y here to support Intel Langwell/Penwell GPIO.
353 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GPIO"
354 depends on PCI && X86
356 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
357 which is an IOH(Input/Output Hub) for x86 embedded processor.
358 This driver can access PCH GPIO device.
360 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
362 ML7223 IOH is for MP(Media Phone) use.
363 ML7223 is companion chip for Intel Atom E6xx series.
364 ML7223 is completely compatible for Intel EG20T PCH.
367 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
370 ML7213 is companion chip for Intel Atom E6xx series.
371 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
372 Hub) which is for IVI(In-Vehicle Infotainment) use.
373 This driver can access the IOH's GPIO device.
375 config GPIO_TIMBERDALE
376 bool "Support for timberdale GPIO IP"
377 depends on MFD_TIMBERDALE && HAS_IOMEM
379 Add support for the GPIO IP in the timberdale FPGA.
382 tristate "RDC R-321x GPIO support"
388 Support for the RDC R321x SoC GPIOs over southbridge
389 PCI configuration space.
391 comment "SPI GPIO expanders:"
394 tristate "Maxim MAX7301 GPIO expander"
395 depends on SPI_MASTER
398 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
401 tristate "Microchip MCP23Sxx I/O expander"
402 depends on SPI_MASTER
404 SPI driver for Microchip MCP23S08/MPC23S17 I/O expanders.
405 This provides a GPIO interface supporting inputs and outputs.
408 tristate "Freescale MC33880 high-side/low-side switch"
409 depends on SPI_MASTER
411 SPI driver for Freescale MC33880 high-side/low-side switch.
412 This provides GPIO interface supporting inputs and outputs.
415 tristate "74x164 serial-in/parallel-out 8-bits shift register"
416 depends on SPI_MASTER
418 Platform driver for 74x164 compatible serial-in/parallel-out
419 8-outputs shift registers. This driver can be used to provide access
420 to more gpio outputs.
422 comment "AC97 GPIO expanders:"
425 bool "Philips UCB1400 GPIO"
426 depends on UCB1400_CORE
428 This enables support for the Philips UCB1400 GPIO pins.
429 The UCB1400 is an AC97 audio codec.
431 To compile this driver as a module, choose M here: the
432 module will be called ucb1400_gpio.
434 comment "MODULbus GPIO expanders:"
437 tristate "Janz VMOD-TTL Digital IO Module"
438 depends on MFD_JANZ_CMODIO
440 This enables support for the Janz VMOD-TTL Digital IO module.
441 This driver provides support for driving the pins in output
442 mode only. Input mode is not supported.
445 bool "ST-Ericsson AB8500 Mixed Signal Circuit gpio functions"
446 depends on AB8500_CORE && BROKEN
448 Select this to enable the AB8500 IC GPIO driver
452 depends on MFD_TPS65910
454 Select this option to enable GPIO driver for the TPS65910