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