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