2 # GPIO infrastructure and drivers
5 config ARCH_WANT_OPTIONAL_GPIOLIB
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.
15 config ARCH_REQUIRE_GPIOLIB
19 Platforms select gpiolib if they use this infrastructure
20 for all their GPIOs, usually starting with ones integrated
22 Selecting this from the architecture code will cause the gpiolib
23 code to always get built in.
29 depends on ARCH_WANT_OPTIONAL_GPIOLIB || ARCH_REQUIRE_GPIOLIB
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.
41 bool "Debug GPIO calls"
42 depends on DEBUG_KERNEL
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.
52 bool "/sys/class/gpio/... (sysfs interface)"
53 depends on SYSFS && EXPERIMENTAL
55 Say Y here to add a sysfs interface for GPIOs.
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.
63 Kernel drivers may also request that a particular GPIO be
64 exported to userspace; this can be useful when debugging.
66 # put drivers in the right section, in alphabetical order
71 comment "Memory mapped GPIO drivers:"
73 config GPIO_BASIC_MMIO_CORE
76 Provides core functionality for basic memory-mapped GPIO controllers.
78 config GPIO_BASIC_MMIO
79 tristate "Basic memory-mapped GPIO controllers support"
80 select GPIO_BASIC_MMIO_CORE
82 Say yes here to support basic memory-mapped GPIO controllers.
85 tristate "IT8761E GPIO support"
87 Say yes here to support GPIO functionality of IT8761E super I/O chip.
90 bool "PrimeCell PL061 GPIO support"
93 Say yes here to support the PrimeCell PL061 GPIO device
96 bool "Xilinx GPIO support"
97 depends on PPC_OF || MICROBLAZE
99 Say yes here to support the Xilinx FPGA GPIO device
102 tristate "NEC VR4100 series General-purpose I/O Uint support"
103 depends on CPU_VR41XX
105 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
108 tristate "Intel SCH/TunnelCreek GPIO"
109 depends on PCI && X86
113 Say yes here to support GPIO interface on Intel Poulsbo SCH
114 or Intel Tunnel Creek processor.
115 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
116 powered by the core power rail and are turned off during sleep
117 modes (S3 and higher). The remaining four GPIOs are powered by
118 the Intel SCH suspend power supply. These GPIOs remain
119 active during S3. The suspend powered GPIOs can be used to wake the
120 system from the Suspend-to-RAM state.
121 The Intel Tunnel Creek processor has 5 GPIOs powered by the
122 core power rail and 9 from suspend power supply.
124 This driver can also be built as a module. If so, the module
125 will be called sch-gpio.
128 tristate "VIA VX855/VX875 GPIO"
129 depends on MFD_SUPPORT && PCI
133 Support access to the VX855/VX875 GPIO lines through the gpio library.
135 This driver provides common support for accessing the device,
136 additional drivers must be enabled in order to use the
137 functionality of the device.
139 comment "I2C GPIO expanders:"
142 tristate "Maxim MAX7300 GPIO expander"
146 GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
149 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
152 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
153 Port Expanders. Each IO port on these chips has a fixed role of
154 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
155 Input and Output (designed by 'P'). The combinations are listed
158 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
159 max7322 (4I4O), max7323 (4P4O)
161 16 bits: max7324 (8I8O), max7325 (8P8O),
162 max7326 (4I12O), max7327 (4P12O)
164 Board setup code must specify the model to use, and the start
165 number for these GPIOs.
167 config GPIO_MAX732X_IRQ
168 bool "Interrupt controller support for MAX732x"
169 depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
171 Say yes here to enable the max732x to be used as an interrupt
172 controller. It requires the driver to be built in the kernel.
175 tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports"
178 Say yes here to provide access to several register-oriented
179 SMBus I/O expanders, made mostly by NXP or TI. Compatible
182 4 bits: pca9536, pca9537
184 8 bits: max7310, pca9534, pca9538, pca9554, pca9557,
187 16 bits: pca9535, pca9539, pca9555, tca6416
189 This driver can also be built as a module. If so, the module
190 will be called pca953x.
192 config GPIO_PCA953X_IRQ
193 bool "Interrupt controller support for PCA953x"
194 depends on GPIO_PCA953X=y
196 Say yes here to enable the pca953x to be used as an interrupt
197 controller. It requires the driver to be built in the kernel.
200 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
203 Say yes here to provide access to most "quasi-bidirectional" I2C
204 GPIO expanders used for additional digital outputs or inputs.
205 Most of these parts are from NXP, though TI is a second source for
206 some of them. Compatible models include:
208 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
209 pca9670, pca9672, pca9674, pca9674a,
212 16 bits: pcf8575, pcf8575c, pca8575,
213 pca9671, pca9673, pca9675
215 Your board setup code will need to declare the expanders in
216 use, and assign numbers to the GPIOs they expose. Those GPIOs
217 can then be used from drivers and other kernel code, just like
218 other GPIOs, but only accessible from task contexts.
220 This driver provides an in-kernel interface to those GPIOs using
221 platform-neutral GPIO calls.
224 bool "Semtech SX150x I2C GPIO expander"
228 Say yes here to provide support for Semtech SX150-series I2C
229 GPIO expanders. Compatible models include:
238 This enables support for the GPIOs found on the STMPE I/O
243 depends on MFD_TC3589X
245 This enables support for the GPIOs found on the TC3589X
249 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
250 depends on TWL4030_CORE
252 Say yes here to access the GPIO signals of various multi-function
253 power management chips from Texas Instruments.
256 tristate "WM831x GPIOs"
257 depends on MFD_WM831X
259 Say yes here to access the GPIO signals of WM831x power management
260 chips from Wolfson Microelectronics.
263 tristate "WM8350 GPIOs"
264 depends on MFD_WM8350
266 Say yes here to access the GPIO signals of WM8350 power management
267 chips from Wolfson Microelectronics.
270 tristate "WM8994 GPIOs"
271 depends on MFD_WM8994
273 Say yes here to access the GPIO signals of WM8994 audio hub
274 CODECs from Wolfson Microelectronics.
277 tristate "GPIO Support for ADP5520 PMIC"
278 depends on PMIC_ADP5520
280 This option enables support for on-chip GPIO found
281 on Analog Devices ADP5520 PMICs.
283 To compile this driver as a module, choose M here: the module will
284 be called adp5520-gpio.
287 tristate "ADP5588 I2C GPIO expander"
290 This option enables support for 18 GPIOs found
291 on Analog Devices ADP5588 GPIO Expanders.
292 To compile this driver as a module, choose M here: the module will be
295 config GPIO_ADP5588_IRQ
296 bool "Interrupt controller support for ADP5588"
297 depends on GPIO_ADP5588=y
299 Say yes here to enable the adp5588 to be used as an interrupt
300 controller. It requires the driver to be built in the kernel.
302 comment "PCI GPIO expanders:"
305 tristate "AMD CS5535/CS5536 GPIO support"
306 depends on PCI && X86 && !CS5535_GPIO && MFD_CS5535
308 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
309 can be used for quite a number of things. The CS5535/6 is found on
310 AMD Geode and Lemote Yeeloong devices.
315 tristate "BT8XX GPIO abuser"
316 depends on PCI && VIDEO_BT848=n
318 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
319 as a cheap PCI GPIO card.
321 This chip can be found on Miro, Hauppauge and STB TV-cards.
323 The card needs to be physically altered for using it as a
324 GPIO card. For more information on how to build a GPIO card
325 from a BT8xx TV card, see the documentation file at
326 Documentation/bt8xxgpio.txt
331 bool "Intel Langwell/Penwell GPIO support"
332 depends on PCI && X86
334 Say Y here to support Intel Langwell/Penwell GPIO.
337 tristate "PCH GPIO of Intel Topcliff"
338 depends on PCI && X86
340 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
341 which is an IOH(Input/Output Hub) for x86 embedded processor.
342 This driver can access PCH GPIO device.
345 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
348 ML7213 is companion chip for Intel Atom E6xx series.
349 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
350 Hub) which is for IVI(In-Vehicle Infotainment) use.
351 This driver can access the IOH's GPIO device.
353 config GPIO_TIMBERDALE
354 bool "Support for timberdale GPIO IP"
355 depends on MFD_TIMBERDALE && HAS_IOMEM
357 Add support for the GPIO IP in the timberdale FPGA.
360 tristate "RDC R-321x GPIO support"
366 Support for the RDC R321x SoC GPIOs over southbridge
367 PCI configuration space.
369 comment "SPI GPIO expanders:"
372 tristate "Maxim MAX7301 GPIO expander"
373 depends on SPI_MASTER
376 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
379 tristate "Microchip MCP23Sxx I/O expander"
380 depends on SPI_MASTER
382 SPI driver for Microchip MCP23S08/MPC23S17 I/O expanders.
383 This provides a GPIO interface supporting inputs and outputs.
386 tristate "Freescale MC33880 high-side/low-side switch"
387 depends on SPI_MASTER
389 SPI driver for Freescale MC33880 high-side/low-side switch.
390 This provides GPIO interface supporting inputs and outputs.
393 tristate "74x164 serial-in/parallel-out 8-bits shift register"
394 depends on SPI_MASTER
396 Platform driver for 74x164 compatible serial-in/parallel-out
397 8-outputs shift registers. This driver can be used to provide access
398 to more gpio outputs.
400 comment "AC97 GPIO expanders:"
403 bool "Philips UCB1400 GPIO"
404 depends on UCB1400_CORE
406 This enables support for the Philips UCB1400 GPIO pins.
407 The UCB1400 is an AC97 audio codec.
409 To compile this driver as a module, choose M here: the
410 module will be called ucb1400_gpio.
412 comment "MODULbus GPIO expanders:"
415 tristate "Janz VMOD-TTL Digital IO Module"
416 depends on MFD_JANZ_CMODIO
418 This enables support for the Janz VMOD-TTL Digital IO module.
419 This driver provides support for driving the pins in output
420 mode only. Input mode is not supported.
423 bool "ST-Ericsson AB8500 Mixed Signal Circuit gpio functions"
424 depends on AB8500_CORE && BROKEN
426 Select this to enable the AB8500 IC GPIO driver