blob: ea83fe8f25d5bf11b2867849295b033689c23ea6 [file] [log] [blame]
Daniel Mentz94787a12013-05-29 21:12:04 -07001#
2# GPIO infrastructure and drivers
3#
4
5config ARCH_WANT_OPTIONAL_GPIOLIB
6 bool
7 help
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.
14
15config ARCH_REQUIRE_GPIOLIB
16 bool
17 select GPIOLIB
18 help
19 Platforms select gpiolib if they use this infrastructure
20 for all their GPIOs, usually starting with ones integrated
21 into SOC processors.
22 Selecting this from the architecture code will cause the gpiolib
23 code to always get built in.
24
25
26
27menuconfig GPIOLIB
28 bool "GPIO Support"
29 depends on ARCH_WANT_OPTIONAL_GPIOLIB || ARCH_REQUIRE_GPIOLIB
30 select GENERIC_GPIO
31 help
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.
35
36 If unsure, say N.
37
38if GPIOLIB
39
40config DEBUG_GPIO
41 bool "Debug GPIO calls"
42 depends on DEBUG_KERNEL
43 help
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.
50
51config GPIO_SYSFS
52 bool "/sys/class/gpio/... (sysfs interface)"
53 depends on SYSFS && EXPERIMENTAL
54 help
55 Say Y here to add a sysfs interface for GPIOs.
56
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.
62
63 Kernel drivers may also request that a particular GPIO be
64 exported to userspace; this can be useful when debugging.
65
66config GPIO_GENERIC
67 tristate
68
69# put drivers in the right section, in alphabetical order
70
71config GPIO_DA9052
72 tristate "Dialog DA9052 GPIO"
73 depends on PMIC_DA9052
74 help
75 Say yes here to enable the GPIO driver for the DA9052 chip.
76
77config GPIO_MAX730X
78 tristate
79
80comment "Memory mapped GPIO drivers:"
81
82config GPIO_GENERIC_PLATFORM
83 tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
84 select GPIO_GENERIC
85 help
86 Say yes here to support basic platform_device memory-mapped GPIO controllers.
87
88config GPIO_IT8761E
89 tristate "IT8761E GPIO support"
90 help
91 Say yes here to support GPIO functionality of IT8761E super I/O chip.
92
93config GPIO_EP93XX
94 def_bool y
95 depends on ARCH_EP93XX
96 select GPIO_GENERIC
97
98config GPIO_MPC5200
99 def_bool y
100 depends on PPC_MPC52xx
101
102config GPIO_MPC8XXX
103 bool "MPC512x/MPC8xxx GPIO support"
104 depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \
105 FSL_SOC_BOOKE || PPC_86xx
106 help
107 Say Y here if you're going to use hardware that connects to the
108 MPC512x/831x/834x/837x/8572/8610 GPIOs.
109
110config GPIO_MSM_V1
111 tristate "Qualcomm MSM GPIO v1"
112 depends on GPIOLIB && ARCH_MSM
113 help
114 Say yes here to support the GPIO interface on ARM v6 based
115 Qualcomm MSM chips. Most of the pins on the MSM can be
116 selected for GPIO, and are controlled by this driver.
117
118config GPIO_MSM_V2
119 tristate "Qualcomm MSM GPIO v2"
120 depends on GPIOLIB && ARCH_MSM
121 help
122 Say yes here to support the GPIO interface on ARM v7 based
123 Qualcomm MSM chips. Most of the pins on the MSM can be
124 selected for GPIO, and are controlled by this driver.
125
126config GPIO_MXC
127 def_bool y
128 depends on ARCH_MXC
129 select GPIO_GENERIC
130 select GENERIC_IRQ_CHIP
131
132config GPIO_MXS
133 def_bool y
134 depends on ARCH_MXS
135 select GPIO_GENERIC
136 select GENERIC_IRQ_CHIP
137
138config GPIO_PL061
139 bool "PrimeCell PL061 GPIO support"
140 depends on ARM_AMBA
141 help
142 Say yes here to support the PrimeCell PL061 GPIO device
143
144config GPIO_XILINX
145 bool "Xilinx GPIO support"
146 depends on PPC_OF || MICROBLAZE
147 help
148 Say yes here to support the Xilinx FPGA GPIO device
149
Daniel Mentz2a9125c2013-05-29 21:13:18 -0700150config GPIO_C2K
151 def_bool y
152 depends on ARCH_M86XXX
153 bool "Comcerto 2000 GPIO support"
154 help
155 Say yes here to support the Comcerto 2000 GPIO device
156
Daniel Mentz94787a12013-05-29 21:12:04 -0700157config GPIO_VR41XX
158 tristate "NEC VR4100 series General-purpose I/O Uint support"
159 depends on CPU_VR41XX
160 help
161 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
162
163config GPIO_SCH
164 tristate "Intel SCH/TunnelCreek GPIO"
165 depends on PCI && X86
166 select MFD_CORE
167 select LPC_SCH
168 help
169 Say yes here to support GPIO interface on Intel Poulsbo SCH
170 or Intel Tunnel Creek processor.
171 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
172 powered by the core power rail and are turned off during sleep
173 modes (S3 and higher). The remaining four GPIOs are powered by
174 the Intel SCH suspend power supply. These GPIOs remain
175 active during S3. The suspend powered GPIOs can be used to wake the
176 system from the Suspend-to-RAM state.
177 The Intel Tunnel Creek processor has 5 GPIOs powered by the
178 core power rail and 9 from suspend power supply.
179
180config GPIO_U300
181 bool "ST-Ericsson U300 COH 901 335/571 GPIO"
182 depends on GPIOLIB && ARCH_U300
183 help
184 Say yes here to support GPIO interface on ST-Ericsson U300.
185 The names of the two IP block variants supported are
186 COH 901 335 and COH 901 571/3. They contain 3, 5 or 7
187 ports of 8 GPIO pins each.
188
189config GPIO_VX855
190 tristate "VIA VX855/VX875 GPIO"
191 depends on PCI
192 select MFD_CORE
193 select MFD_VX855
194 help
195 Support access to the VX855/VX875 GPIO lines through the gpio library.
196
197 This driver provides common support for accessing the device,
198 additional drivers must be enabled in order to use the
199 functionality of the device.
200
201comment "I2C GPIO expanders:"
202
203config GPIO_MAX7300
204 tristate "Maxim MAX7300 GPIO expander"
205 depends on I2C
206 select GPIO_MAX730X
207 help
208 GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
209
210config GPIO_MAX732X
211 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
212 depends on I2C
213 help
214 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
215 Port Expanders. Each IO port on these chips has a fixed role of
216 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
217 Input and Output (designed by 'P'). The combinations are listed
218 below:
219
220 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
221 max7322 (4I4O), max7323 (4P4O)
222
223 16 bits: max7324 (8I8O), max7325 (8P8O),
224 max7326 (4I12O), max7327 (4P12O)
225
226 Board setup code must specify the model to use, and the start
227 number for these GPIOs.
228
229config GPIO_MAX732X_IRQ
230 bool "Interrupt controller support for MAX732x"
231 depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
232 help
233 Say yes here to enable the max732x to be used as an interrupt
234 controller. It requires the driver to be built in the kernel.
235
236config GPIO_PCA953X
237 tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports"
238 depends on I2C
239 help
240 Say yes here to provide access to several register-oriented
241 SMBus I/O expanders, made mostly by NXP or TI. Compatible
242 models include:
243
244 4 bits: pca9536, pca9537
245
246 8 bits: max7310, pca9534, pca9538, pca9554, pca9557,
247 tca6408
248
249 16 bits: pca9535, pca9539, pca9555, tca6416
250
251config GPIO_PCA953X_IRQ
252 bool "Interrupt controller support for PCA953x"
253 depends on GPIO_PCA953X=y
254 help
255 Say yes here to enable the pca953x to be used as an interrupt
256 controller. It requires the driver to be built in the kernel.
257
258config GPIO_PCF857X
259 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
260 depends on I2C
261 help
262 Say yes here to provide access to most "quasi-bidirectional" I2C
263 GPIO expanders used for additional digital outputs or inputs.
264 Most of these parts are from NXP, though TI is a second source for
265 some of them. Compatible models include:
266
267 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
268 pca9670, pca9672, pca9674, pca9674a,
269 max7328, max7329
270
271 16 bits: pcf8575, pcf8575c, pca8575,
272 pca9671, pca9673, pca9675
273
274 Your board setup code will need to declare the expanders in
275 use, and assign numbers to the GPIOs they expose. Those GPIOs
276 can then be used from drivers and other kernel code, just like
277 other GPIOs, but only accessible from task contexts.
278
279 This driver provides an in-kernel interface to those GPIOs using
280 platform-neutral GPIO calls.
281
282config GPIO_SX150X
283 bool "Semtech SX150x I2C GPIO expander"
284 depends on I2C=y
285 default n
286 help
287 Say yes here to provide support for Semtech SX150-series I2C
288 GPIO expanders. Compatible models include:
289
290 8 bits: sx1508q
291 16 bits: sx1509q
292
293config GPIO_STMPE
294 bool "STMPE GPIOs"
295 depends on MFD_STMPE
296 help
297 This enables support for the GPIOs found on the STMPE I/O
298 Expanders.
299
300config GPIO_TC3589X
301 bool "TC3589X GPIOs"
302 depends on MFD_TC3589X
303 help
304 This enables support for the GPIOs found on the TC3589X
305 I/O Expander.
306
307config GPIO_TPS65912
308 tristate "TI TPS65912 GPIO"
309 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
310 help
311 This driver supports TPS65912 gpio chip
312
313config GPIO_TWL4030
314 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
315 depends on TWL4030_CORE
316 help
317 Say yes here to access the GPIO signals of various multi-function
318 power management chips from Texas Instruments.
319
320config GPIO_WM831X
321 tristate "WM831x GPIOs"
322 depends on MFD_WM831X
323 help
324 Say yes here to access the GPIO signals of WM831x power management
325 chips from Wolfson Microelectronics.
326
327config GPIO_WM8350
328 tristate "WM8350 GPIOs"
329 depends on MFD_WM8350
330 help
331 Say yes here to access the GPIO signals of WM8350 power management
332 chips from Wolfson Microelectronics.
333
334config GPIO_WM8994
335 tristate "WM8994 GPIOs"
336 depends on MFD_WM8994
337 help
338 Say yes here to access the GPIO signals of WM8994 audio hub
339 CODECs from Wolfson Microelectronics.
340
341config GPIO_ADP5520
342 tristate "GPIO Support for ADP5520 PMIC"
343 depends on PMIC_ADP5520
344 help
345 This option enables support for on-chip GPIO found
346 on Analog Devices ADP5520 PMICs.
347
348config GPIO_ADP5588
349 tristate "ADP5588 I2C GPIO expander"
350 depends on I2C
351 help
352 This option enables support for 18 GPIOs found
353 on Analog Devices ADP5588 GPIO Expanders.
354
355config GPIO_ADP5588_IRQ
356 bool "Interrupt controller support for ADP5588"
357 depends on GPIO_ADP5588=y
358 help
359 Say yes here to enable the adp5588 to be used as an interrupt
360 controller. It requires the driver to be built in the kernel.
361
362comment "PCI GPIO expanders:"
363
364config GPIO_CS5535
365 tristate "AMD CS5535/CS5536 GPIO support"
366 depends on PCI && X86 && !CS5535_GPIO && MFD_CS5535
367 help
368 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
369 can be used for quite a number of things. The CS5535/6 is found on
370 AMD Geode and Lemote Yeeloong devices.
371
372 If unsure, say N.
373
374config GPIO_BT8XX
375 tristate "BT8XX GPIO abuser"
376 depends on PCI && VIDEO_BT848=n
377 help
378 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
379 as a cheap PCI GPIO card.
380
381 This chip can be found on Miro, Hauppauge and STB TV-cards.
382
383 The card needs to be physically altered for using it as a
384 GPIO card. For more information on how to build a GPIO card
385 from a BT8xx TV card, see the documentation file at
386 Documentation/bt8xxgpio.txt
387
388 If unsure, say N.
389
390config GPIO_LANGWELL
391 bool "Intel Langwell/Penwell GPIO support"
392 depends on PCI && X86
393 help
394 Say Y here to support Intel Langwell/Penwell GPIO.
395
396config GPIO_PCH
397 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
398 depends on PCI && X86
399 select GENERIC_IRQ_CHIP
400 help
401 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
402 which is an IOH(Input/Output Hub) for x86 embedded processor.
403 This driver can access PCH GPIO device.
404
405 This driver also can be used for LAPIS Semiconductor IOH(Input/
406 Output Hub), ML7223 and ML7831.
407 ML7223 IOH is for MP(Media Phone) use.
408 ML7831 IOH is for general purpose use.
409 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
410 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
411
412config GPIO_ML_IOH
413 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
414 depends on PCI
415 select GENERIC_IRQ_CHIP
416 help
417 ML7213 is companion chip for Intel Atom E6xx series.
418 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
419 Hub) which is for IVI(In-Vehicle Infotainment) use.
420 This driver can access the IOH's GPIO device.
421
422config GPIO_TIMBERDALE
423 bool "Support for timberdale GPIO IP"
424 depends on MFD_TIMBERDALE && HAS_IOMEM
425 ---help---
426 Add support for the GPIO IP in the timberdale FPGA.
427
428config GPIO_RDC321X
429 tristate "RDC R-321x GPIO support"
430 depends on PCI
431 select MFD_CORE
432 select MFD_RDC321X
433 help
434 Support for the RDC R321x SoC GPIOs over southbridge
435 PCI configuration space.
436
437comment "SPI GPIO expanders:"
438
439config GPIO_MAX7301
440 tristate "Maxim MAX7301 GPIO expander"
441 depends on SPI_MASTER
442 select GPIO_MAX730X
443 help
444 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
445
446config GPIO_MCP23S08
447 tristate "Microchip MCP23xxx I/O expander"
448 depends on SPI_MASTER || I2C
449 help
450 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
451 I/O expanders.
452 This provides a GPIO interface supporting inputs and outputs.
453
454config GPIO_MC33880
455 tristate "Freescale MC33880 high-side/low-side switch"
456 depends on SPI_MASTER
457 help
458 SPI driver for Freescale MC33880 high-side/low-side switch.
459 This provides GPIO interface supporting inputs and outputs.
460
461config GPIO_74X164
462 tristate "74x164 serial-in/parallel-out 8-bits shift register"
463 depends on SPI_MASTER
464 help
465 Platform driver for 74x164 compatible serial-in/parallel-out
466 8-outputs shift registers. This driver can be used to provide access
467 to more gpio outputs.
468
469comment "AC97 GPIO expanders:"
470
471config GPIO_UCB1400
472 bool "Philips UCB1400 GPIO"
473 depends on UCB1400_CORE
474 help
475 This enables support for the Philips UCB1400 GPIO pins.
476 The UCB1400 is an AC97 audio codec.
477
478comment "MODULbus GPIO expanders:"
479
480config GPIO_JANZ_TTL
481 tristate "Janz VMOD-TTL Digital IO Module"
482 depends on MFD_JANZ_CMODIO
483 help
484 This enables support for the Janz VMOD-TTL Digital IO module.
485 This driver provides support for driving the pins in output
486 mode only. Input mode is not supported.
487
488config GPIO_AB8500
489 bool "ST-Ericsson AB8500 Mixed Signal Circuit gpio functions"
490 depends on AB8500_CORE && BROKEN
491 help
492 Select this to enable the AB8500 IC GPIO driver
493
494config GPIO_TPS65910
495 bool "TPS65910 GPIO"
496 depends on MFD_TPS65910
497 help
498 Select this option to enable GPIO driver for the TPS65910
499 chip family.
500endif