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