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