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