1
2
3
4
5config ARCH_HAVE_CUSTOM_GPIO_H
6 bool
7 help
8 Selecting this config option from the architecture Kconfig allows
9 the architecture to provide a custom asm/gpio.h implementation
10 overriding the default implementations. New uses of this are
11 strongly discouraged.
12
13config ARCH_WANT_OPTIONAL_GPIOLIB
14 bool
15 help
16 Select this config option from the architecture Kconfig, if
17 it is possible to use gpiolib on the architecture, but let the
18 user decide whether to actually build it or not.
19 Select this instead of ARCH_REQUIRE_GPIOLIB, if your architecture does
20 not depend on GPIOs being available, but rather let the user
21 decide whether he needs it or not.
22
23config ARCH_REQUIRE_GPIOLIB
24 bool
25 select GPIOLIB
26 help
27 Platforms select gpiolib if they use this infrastructure
28 for all their GPIOs, usually starting with ones integrated
29 into SOC processors.
30 Selecting this from the architecture code will cause the gpiolib
31 code to always get built in.
32
33config GPIO_DEVRES
34 def_bool y
35 depends on HAS_IOMEM
36
37
38menuconfig GPIOLIB
39 bool "GPIO Support"
40 depends on ARCH_WANT_OPTIONAL_GPIOLIB || ARCH_REQUIRE_GPIOLIB
41 help
42 This enables GPIO support through the generic GPIO library.
43 You only need to enable this, if you also want to enable
44 one or more of the GPIO drivers below.
45
46 If unsure, say N.
47
48if GPIOLIB
49
50config OF_GPIO
51 def_bool y
52 depends on OF
53
54config GPIO_ACPI
55 def_bool y
56 depends on ACPI
57
58config DEBUG_GPIO
59 bool "Debug GPIO calls"
60 depends on DEBUG_KERNEL
61 help
62 Say Y here to add some extra checks and diagnostics to GPIO calls.
63 These checks help ensure that GPIOs have been properly initialized
64 before they are used, and that sleeping calls are not made from
65 non-sleeping contexts. They can make bitbanged serial protocols
66 slower. The diagnostics help catch the type of setup errors
67 that are most common when setting up new platforms or boards.
68
69config GPIO_SYSFS
70 bool "/sys/class/gpio/... (sysfs interface)"
71 depends on SYSFS
72 help
73 Say Y here to add a sysfs interface for GPIOs.
74
75 This is mostly useful to work around omissions in a system's
76 kernel support. Those are common in custom and semicustom
77 hardware assembled using standard kernels with a minimum of
78 custom patches. In those cases, userspace code may import
79 a given GPIO from the kernel, if no kernel driver requested it.
80
81 Kernel drivers may also request that a particular GPIO be
82 exported to userspace; this can be useful when debugging.
83
84config GPIO_GENERIC
85 tristate
86
87
88
89config GPIO_DA9052
90 tristate "Dialog DA9052 GPIO"
91 depends on PMIC_DA9052
92 help
93 Say yes here to enable the GPIO driver for the DA9052 chip.
94
95config GPIO_DA9055
96 tristate "Dialog Semiconductor DA9055 GPIO"
97 depends on MFD_DA9055
98 help
99 Say yes here to enable the GPIO driver for the DA9055 chip.
100
101 The Dialog DA9055 PMIC chip has 3 GPIO pins that can be
102 be controller by this driver.
103
104 If driver is built as a module it will be called gpio-da9055.
105
106config GPIO_MAX730X
107 tristate
108
109comment "Memory mapped GPIO drivers:"
110
111config GPIO_CLPS711X
112 def_bool y
113 depends on ARCH_CLPS711X
114
115config GPIO_GENERIC_PLATFORM
116 tristate "Generic memory-mapped GPIO controller support (MMIO platform device)"
117 select GPIO_GENERIC
118 help
119 Say yes here to support basic platform_device memory-mapped GPIO controllers.
120
121config GPIO_IT8761E
122 tristate "IT8761E GPIO support"
123 depends on X86
124 help
125 Say yes here to support GPIO functionality of IT8761E super I/O chip.
126
127config GPIO_EM
128 tristate "Emma Mobile GPIO"
129 depends on ARM
130 help
131 Say yes here to support GPIO on Renesas Emma Mobile SoCs.
132
133config GPIO_EP93XX
134 def_bool y
135 depends on ARCH_EP93XX
136 select GPIO_GENERIC
137
138config GPIO_MM_LANTIQ
139 bool "Lantiq Memory mapped GPIOs"
140 depends on LANTIQ && SOC_XWAY
141 help
142 This enables support for memory mapped GPIOs on the External Bus Unit
143 (EBU) found on Lantiq SoCs. The gpios are output only as they are
144 created by attaching a 16bit latch to the bus.
145
146config GPIO_MPC5200
147 def_bool y
148 depends on PPC_MPC52xx
149
150config GPIO_MPC8XXX
151 bool "MPC512x/MPC8xxx GPIO support"
152 depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \
153 FSL_SOC_BOOKE || PPC_86xx
154 help
155 Say Y here if you're going to use hardware that connects to the
156 MPC512x/831x/834x/837x/8572/8610 GPIOs.
157
158config GPIO_MSM_V1
159 tristate "Qualcomm MSM GPIO v1"
160 depends on GPIOLIB && ARCH_MSM && (ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50)
161 help
162 Say yes here to support the GPIO interface on ARM v6 based
163 Qualcomm MSM chips. Most of the pins on the MSM can be
164 selected for GPIO, and are controlled by this driver.
165
166config GPIO_MSM_V2
167 tristate "Qualcomm MSM GPIO v2"
168 depends on GPIOLIB && ARCH_MSM
169 help
170 Say yes here to support the GPIO interface on ARM v7 based
171 Qualcomm MSM chips. Most of the pins on the MSM can be
172 selected for GPIO, and are controlled by this driver.
173
174config GPIO_MVEBU
175 def_bool y
176 depends on PLAT_ORION
177 depends on OF
178 select GPIO_GENERIC
179 select GENERIC_IRQ_CHIP
180
181config GPIO_MXC
182 def_bool y
183 depends on ARCH_MXC
184 select GPIO_GENERIC
185 select GENERIC_IRQ_CHIP
186
187config GPIO_MXS
188 def_bool y
189 depends on ARCH_MXS
190 select GPIO_GENERIC
191 select GENERIC_IRQ_CHIP
192
193config GPIO_PL061
194 bool "PrimeCell PL061 GPIO support"
195 depends on ARM && ARM_AMBA
196 select GENERIC_IRQ_CHIP
197 help
198 Say yes here to support the PrimeCell PL061 GPIO device
199
200config GPIO_PXA
201 bool "PXA GPIO support"
202 depends on ARCH_PXA || ARCH_MMP
203 help
204 Say yes here to support the PXA GPIO device
205
206config GPIO_RCAR
207 tristate "Renesas R-Car GPIO"
208 depends on ARM
209 help
210 Say yes here to support GPIO on Renesas R-Car SoCs.
211
212config GPIO_SPEAR_SPICS
213 bool "ST SPEAr13xx SPI Chip Select as GPIO support"
214 depends on PLAT_SPEAR
215 select GENERIC_IRQ_CHIP
216 help
217 Say yes here to support ST SPEAr SPI Chip Select as GPIO device
218
219config GPIO_STA2X11
220 bool "STA2x11/ConneXt GPIO support"
221 depends on MFD_STA2X11
222 select GENERIC_IRQ_CHIP
223 help
224 Say yes here to support the STA2x11/ConneXt GPIO device.
225 The GPIO module has 128 GPIO pins with alternate functions.
226
227config GPIO_TS5500
228 tristate "TS-5500 DIO blocks and compatibles"
229 help
230 This driver supports Digital I/O exposed by pin blocks found on some
231 Technologic Systems platforms. It includes, but is not limited to, 3
232 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600
233 LCD port.
234
235config GPIO_XILINX
236 bool "Xilinx GPIO support"
237 depends on PPC_OF || MICROBLAZE
238 help
239 Say yes here to support the Xilinx FPGA GPIO device
240
241config GPIO_VR41XX
242 tristate "NEC VR4100 series General-purpose I/O Uint support"
243 depends on CPU_VR41XX
244 help
245 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
246
247config GPIO_SCH
248 tristate "Intel SCH/TunnelCreek/Centerton GPIO"
249 depends on PCI && X86
250 select MFD_CORE
251 select LPC_SCH
252 help
253 Say yes here to support GPIO interface on Intel Poulsbo SCH,
254 Intel Tunnel Creek processor or Intel Centerton processor.
255 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
256 powered by the core power rail and are turned off during sleep
257 modes (S3 and higher). The remaining four GPIOs are powered by
258 the Intel SCH suspend power supply. These GPIOs remain
259 active during S3. The suspend powered GPIOs can be used to wake the
260 system from the Suspend-to-RAM state.
261 The Intel Tunnel Creek processor has 5 GPIOs powered by the
262 core power rail and 9 from suspend power supply.
263 The Intel Centerton processor has a total of 30 GPIO pins.
264 Twenty-one are powered by the core power rail and 9 from the
265 suspend power supply.
266
267config GPIO_ICH
268 tristate "Intel ICH GPIO"
269 depends on PCI && X86
270 select MFD_CORE
271 select LPC_ICH
272 help
273 Say yes here to support the GPIO functionality of a number of Intel
274 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8
275 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg
276 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake).
277
278 If unsure, say N.
279
280config GPIO_VX855
281 tristate "VIA VX855/VX875 GPIO"
282 depends on PCI && GENERIC_HARDIRQS
283 select MFD_CORE
284 select MFD_VX855
285 help
286 Support access to the VX855/VX875 GPIO lines through the gpio library.
287
288 This driver provides common support for accessing the device,
289 additional drivers must be enabled in order to use the
290 functionality of the device.
291
292config GPIO_GE_FPGA
293 bool "GE FPGA based GPIO"
294 depends on GE_FPGA
295 help
296 Support for common GPIO functionality provided on some GE Single Board
297 Computers.
298
299 This driver provides basic support (configure as input or output, read
300 and write pin state) for GPIO implemented in a number of GE single
301 board computers.
302
303config GPIO_LYNXPOINT
304 bool "Intel Lynxpoint GPIO support"
305 depends on ACPI && X86
306 select IRQ_DOMAIN
307 help
308 driver for GPIO functionality on Intel Lynxpoint PCH chipset
309 Requires ACPI device enumeration code to set up a platform device.
310
311config GPIO_GRGPIO
312 tristate "Aeroflex Gaisler GRGPIO support"
313 depends on OF
314 select GPIO_GENERIC
315 select IRQ_DOMAIN
316 help
317 Select this to support Aeroflex Gaisler GRGPIO cores from the GRLIB
318 VHDL IP core library.
319
320comment "I2C GPIO expanders:"
321
322config GPIO_ARIZONA
323 tristate "Wolfson Microelectronics Arizona class devices"
324 depends on MFD_ARIZONA
325 help
326 Support for GPIOs on Wolfson Arizona class devices.
327
328config GPIO_MAX7300
329 tristate "Maxim MAX7300 GPIO expander"
330 depends on I2C
331 select GPIO_MAX730X
332 help
333 GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
334
335config GPIO_MAX732X
336 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
337 depends on I2C
338 help
339 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
340 Port Expanders. Each IO port on these chips has a fixed role of
341 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
342 Input and Output (designed by 'P'). The combinations are listed
343 below:
344
345 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
346 max7322 (4I4O), max7323 (4P4O)
347
348 16 bits: max7324 (8I8O), max7325 (8P8O),
349 max7326 (4I12O), max7327 (4P12O)
350
351 Board setup code must specify the model to use, and the start
352 number for these GPIOs.
353
354config GPIO_MAX732X_IRQ
355 bool "Interrupt controller support for MAX732x"
356 depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
357 help
358 Say yes here to enable the max732x to be used as an interrupt
359 controller. It requires the driver to be built in the kernel.
360
361config GPIO_MC9S08DZ60
362 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions"
363 depends on I2C=y && MACH_MX35_3DS
364 help
365 Select this to enable the MC9S08DZ60 GPIO driver
366
367config GPIO_PCA953X
368 tristate "PCA953x, PCA955x, PCA957x, TCA64xx, and MAX7310 I/O ports"
369 depends on I2C
370 help
371 Say yes here to provide access to several register-oriented
372 SMBus I/O expanders, made mostly by NXP or TI. Compatible
373 models include:
374
375 4 bits: pca9536, pca9537
376
377 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554,
378 pca9556, pca9557, pca9574, tca6408
379
380 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575,
381 tca6416
382
383config GPIO_PCA953X_IRQ
384 bool "Interrupt controller support for PCA953x"
385 depends on GPIO_PCA953X=y
386 help
387 Say yes here to enable the pca953x to be used as an interrupt
388 controller. It requires the driver to be built in the kernel.
389
390config GPIO_PCF857X
391 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
392 depends on I2C
393 select IRQ_DOMAIN
394 help
395 Say yes here to provide access to most "quasi-bidirectional" I2C
396 GPIO expanders used for additional digital outputs or inputs.
397 Most of these parts are from NXP, though TI is a second source for
398 some of them. Compatible models include:
399
400 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
401 pca9670, pca9672, pca9674, pca9674a,
402 max7328, max7329
403
404 16 bits: pcf8575, pcf8575c, pca8575,
405 pca9671, pca9673, pca9675
406
407 Your board setup code will need to declare the expanders in
408 use, and assign numbers to the GPIOs they expose. Those GPIOs
409 can then be used from drivers and other kernel code, just like
410 other GPIOs, but only accessible from task contexts.
411
412 This driver provides an in-kernel interface to those GPIOs using
413 platform-neutral GPIO calls.
414
415config GPIO_RC5T583
416 bool "RICOH RC5T583 GPIO"
417 depends on MFD_RC5T583
418 help
419 Select this option to enable GPIO driver for the Ricoh RC5T583
420 chip family.
421 This driver provides the support for driving/reading the gpio pins
422 of RC5T583 device through standard gpio library.
423
424config GPIO_SX150X
425 bool "Semtech SX150x I2C GPIO expander"
426 depends on I2C=y
427 default n
428 help
429 Say yes here to provide support for Semtech SX150-series I2C
430 GPIO expanders. Compatible models include:
431
432 8 bits: sx1508q
433 16 bits: sx1509q
434
435config GPIO_STMPE
436 bool "STMPE GPIOs"
437 depends on MFD_STMPE
438 help
439 This enables support for the GPIOs found on the STMPE I/O
440 Expanders.
441
442config GPIO_STP_XWAY
443 bool "XWAY STP GPIOs"
444 depends on SOC_XWAY
445 help
446 This enables support for the Serial To Parallel (STP) unit found on
447 XWAY SoC. The STP allows the SoC to drive a shift registers cascade,
448 that can be up to 24 bit. This peripheral is aimed at driving leds.
449 Some of the gpios/leds can be auto updated by the soc with dsl and
450 phy status.
451
452config GPIO_TC3589X
453 bool "TC3589X GPIOs"
454 depends on MFD_TC3589X
455 help
456 This enables support for the GPIOs found on the TC3589X
457 I/O Expander.
458
459config GPIO_TPS65912
460 tristate "TI TPS65912 GPIO"
461 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI)
462 help
463 This driver supports TPS65912 gpio chip
464
465config GPIO_TWL4030
466 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
467 depends on TWL4030_CORE
468 help
469 Say yes here to access the GPIO signals of various multi-function
470 power management chips from Texas Instruments.
471
472config GPIO_TWL6040
473 tristate "TWL6040 GPO"
474 depends on TWL6040_CORE
475 help
476 Say yes here to access the GPO signals of twl6040
477 audio chip from Texas Instruments.
478
479config GPIO_WM831X
480 tristate "WM831x GPIOs"
481 depends on MFD_WM831X
482 help
483 Say yes here to access the GPIO signals of WM831x power management
484 chips from Wolfson Microelectronics.
485
486config GPIO_WM8350
487 tristate "WM8350 GPIOs"
488 depends on MFD_WM8350
489 help
490 Say yes here to access the GPIO signals of WM8350 power management
491 chips from Wolfson Microelectronics.
492
493config GPIO_WM8994
494 tristate "WM8994 GPIOs"
495 depends on MFD_WM8994
496 help
497 Say yes here to access the GPIO signals of WM8994 audio hub
498 CODECs from Wolfson Microelectronics.
499
500config GPIO_ADP5520
501 tristate "GPIO Support for ADP5520 PMIC"
502 depends on PMIC_ADP5520
503 help
504 This option enables support for on-chip GPIO found
505 on Analog Devices ADP5520 PMICs.
506
507config GPIO_ADP5588
508 tristate "ADP5588 I2C GPIO expander"
509 depends on I2C
510 help
511 This option enables support for 18 GPIOs found
512 on Analog Devices ADP5588 GPIO Expanders.
513
514config GPIO_ADP5588_IRQ
515 bool "Interrupt controller support for ADP5588"
516 depends on GPIO_ADP5588=y
517 help
518 Say yes here to enable the adp5588 to be used as an interrupt
519 controller. It requires the driver to be built in the kernel.
520
521config GPIO_ADNP
522 tristate "Avionic Design N-bit GPIO expander"
523 depends on I2C && OF_GPIO
524 help
525 This option enables support for N GPIOs found on Avionic Design
526 I2C GPIO expanders. The register space will be extended by powers
527 of two, so the controller will need to accommodate for that. For
528 example: if a controller provides 48 pins, 6 registers will be
529 enough to represent all pins, but the driver will assume a
530 register layout for 64 pins (8 registers).
531
532comment "PCI GPIO expanders:"
533
534config GPIO_CS5535
535 tristate "AMD CS5535/CS5536 GPIO support"
536 depends on PCI && X86 && MFD_CS5535
537 help
538 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
539 can be used for quite a number of things. The CS5535/6 is found on
540 AMD Geode and Lemote Yeeloong devices.
541
542 If unsure, say N.
543
544config GPIO_BT8XX
545 tristate "BT8XX GPIO abuser"
546 depends on PCI && VIDEO_BT848=n
547 help
548 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
549 as a cheap PCI GPIO card.
550
551 This chip can be found on Miro, Hauppauge and STB TV-cards.
552
553 The card needs to be physically altered for using it as a
554 GPIO card. For more information on how to build a GPIO card
555 from a BT8xx TV card, see the documentation file at
556 Documentation/bt8xxgpio.txt
557
558 If unsure, say N.
559
560config GPIO_AMD8111
561 tristate "AMD 8111 GPIO driver"
562 depends on PCI
563 help
564 The AMD 8111 south bridge contains 32 GPIO pins which can be used.
565
566 Note, that usually system firmware/ACPI handles GPIO pins on their
567 own and users might easily break their systems with uncarefull usage
568 of this driver!
569
570 If unsure, say N
571
572config GPIO_LANGWELL
573 bool "Intel Langwell/Penwell GPIO support"
574 depends on PCI && X86
575 select IRQ_DOMAIN
576 help
577 Say Y here to support Intel Langwell/Penwell GPIO.
578
579config GPIO_PCH
580 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO"
581 depends on PCI && X86
582 select GENERIC_IRQ_CHIP
583 help
584 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
585 which is an IOH(Input/Output Hub) for x86 embedded processor.
586 This driver can access PCH GPIO device.
587
588 This driver also can be used for LAPIS Semiconductor IOH(Input/
589 Output Hub), ML7223 and ML7831.
590 ML7223 IOH is for MP(Media Phone) use.
591 ML7831 IOH is for general purpose use.
592 ML7223/ML7831 is companion chip for Intel Atom E6xx series.
593 ML7223/ML7831 is completely compatible for Intel EG20T PCH.
594
595config GPIO_ML_IOH
596 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
597 depends on PCI
598 select GENERIC_IRQ_CHIP
599 help
600 ML7213 is companion chip for Intel Atom E6xx series.
601 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
602 Hub) which is for IVI(In-Vehicle Infotainment) use.
603 This driver can access the IOH's GPIO device.
604
605config GPIO_SODAVILLE
606 bool "Intel Sodaville GPIO support"
607 depends on X86 && PCI && OF
608 select GPIO_GENERIC
609 select GENERIC_IRQ_CHIP
610 help
611 Say Y here to support Intel Sodaville GPIO.
612
613config GPIO_TIMBERDALE
614 bool "Support for timberdale GPIO IP"
615 depends on MFD_TIMBERDALE && HAS_IOMEM
616 ---help---
617 Add support for the GPIO IP in the timberdale FPGA.
618
619config GPIO_RDC321X
620 tristate "RDC R-321x GPIO support"
621 depends on PCI && GENERIC_HARDIRQS
622 select MFD_CORE
623 select MFD_RDC321X
624 help
625 Support for the RDC R321x SoC GPIOs over southbridge
626 PCI configuration space.
627
628comment "SPI GPIO expanders:"
629
630config GPIO_MAX7301
631 tristate "Maxim MAX7301 GPIO expander"
632 depends on SPI_MASTER
633 select GPIO_MAX730X
634 help
635 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
636
637config GPIO_MCP23S08
638 tristate "Microchip MCP23xxx I/O expander"
639 depends on (SPI_MASTER && !I2C) || I2C
640 help
641 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017
642 I/O expanders.
643 This provides a GPIO interface supporting inputs and outputs.
644
645config GPIO_MC33880
646 tristate "Freescale MC33880 high-side/low-side switch"
647 depends on SPI_MASTER
648 help
649 SPI driver for Freescale MC33880 high-side/low-side switch.
650 This provides GPIO interface supporting inputs and outputs.
651
652config GPIO_74X164
653 tristate "74x164 serial-in/parallel-out 8-bits shift register"
654 depends on SPI_MASTER
655 help
656 Platform driver for 74x164 compatible serial-in/parallel-out
657 8-outputs shift registers. This driver can be used to provide access
658 to more gpio outputs.
659
660comment "AC97 GPIO expanders:"
661
662config GPIO_UCB1400
663 bool "Philips UCB1400 GPIO"
664 depends on UCB1400_CORE
665 help
666 This enables support for the Philips UCB1400 GPIO pins.
667 The UCB1400 is an AC97 audio codec.
668
669comment "MODULbus GPIO expanders:"
670
671config GPIO_JANZ_TTL
672 tristate "Janz VMOD-TTL Digital IO Module"
673 depends on MFD_JANZ_CMODIO
674 help
675 This enables support for the Janz VMOD-TTL Digital IO module.
676 This driver provides support for driving the pins in output
677 mode only. Input mode is not supported.
678
679config GPIO_PALMAS
680 bool "TI PALMAS series PMICs GPIO"
681 depends on MFD_PALMAS
682 help
683 Select this option to enable GPIO driver for the TI PALMAS
684 series chip family.
685
686config GPIO_TPS6586X
687 bool "TPS6586X GPIO"
688 depends on MFD_TPS6586X
689 help
690 Select this option to enable GPIO driver for the TPS6586X
691 chip family.
692
693config GPIO_TPS65910
694 bool "TPS65910 GPIO"
695 depends on MFD_TPS65910
696 help
697 Select this option to enable GPIO driver for the TPS65910
698 chip family.
699
700config GPIO_MSIC
701 bool "Intel MSIC mixed signal gpio support"
702 depends on MFD_INTEL_MSIC
703 help
704 Enable support for GPIO on intel MSIC controllers found in
705 intel MID devices
706
707comment "USB GPIO expanders:"
708
709config GPIO_VIPERBOARD
710 tristate "Viperboard GPIO a & b support"
711 depends on MFD_VIPERBOARD && USB
712 help
713 Say yes here to access the GPIO signals of Nano River
714 Technologies Viperboard. There are two GPIO chips on the
715 board: gpioa and gpiob.
716 See viperboard API specification and Nano
717 River Tech's viperboard.h for detailed meaning
718 of the module parameters.
719
720endif
721
