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