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