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