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.
89 config GPIO_PLAT_SAMSUNG
90 bool "Samsung SoCs GPIO library support"
91 default y if SAMSUNG_GPIOLIB_4BIT
93 Say yes here to support Samsung SoCs GPIO library
96 bool "PrimeCell PL061 GPIO support"
99 Say yes here to support the PrimeCell PL061 GPIO device
102 bool "Xilinx GPIO support"
103 depends on PPC_OF || MICROBLAZE
105 Say yes here to support the Xilinx FPGA GPIO device
108 tristate "NEC VR4100 series General-purpose I/O Uint support"
109 depends on CPU_VR41XX
111 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
114 tristate "Intel SCH/TunnelCreek GPIO"
115 depends on PCI && X86
119 Say yes here to support GPIO interface on Intel Poulsbo SCH
120 or Intel Tunnel Creek processor.
121 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
122 powered by the core power rail and are turned off during sleep
123 modes (S3 and higher). The remaining four GPIOs are powered by
124 the Intel SCH suspend power supply. These GPIOs remain
125 active during S3. The suspend powered GPIOs can be used to wake the
126 system from the Suspend-to-RAM state.
127 The Intel Tunnel Creek processor has 5 GPIOs powered by the
128 core power rail and 9 from suspend power supply.
130 This driver can also be built as a module. If so, the module
131 will be called sch-gpio.
134 tristate "VIA VX855/VX875 GPIO"
135 depends on MFD_SUPPORT && PCI
139 Support access to the VX855/VX875 GPIO lines through the gpio library.
141 This driver provides common support for accessing the device,
142 additional drivers must be enabled in order to use the
143 functionality of the device.
145 comment "I2C GPIO expanders:"
148 tristate "Maxim MAX7300 GPIO expander"
152 GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
155 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
158 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
159 Port Expanders. Each IO port on these chips has a fixed role of
160 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
161 Input and Output (designed by 'P'). The combinations are listed
164 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
165 max7322 (4I4O), max7323 (4P4O)
167 16 bits: max7324 (8I8O), max7325 (8P8O),
168 max7326 (4I12O), max7327 (4P12O)
170 Board setup code must specify the model to use, and the start
171 number for these GPIOs.
173 config GPIO_MAX732X_IRQ
174 bool "Interrupt controller support for MAX732x"
175 depends on GPIO_MAX732X=y && GENERIC_HARDIRQS
177 Say yes here to enable the max732x to be used as an interrupt
178 controller. It requires the driver to be built in the kernel.
181 tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports"
184 Say yes here to provide access to several register-oriented
185 SMBus I/O expanders, made mostly by NXP or TI. Compatible
188 4 bits: pca9536, pca9537
190 8 bits: max7310, pca9534, pca9538, pca9554, pca9557,
193 16 bits: pca9535, pca9539, pca9555, tca6416
195 This driver can also be built as a module. If so, the module
196 will be called pca953x.
198 config GPIO_PCA953X_IRQ
199 bool "Interrupt controller support for PCA953x"
200 depends on GPIO_PCA953X=y
202 Say yes here to enable the pca953x to be used as an interrupt
203 controller. It requires the driver to be built in the kernel.
206 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
209 Say yes here to provide access to most "quasi-bidirectional" I2C
210 GPIO expanders used for additional digital outputs or inputs.
211 Most of these parts are from NXP, though TI is a second source for
212 some of them. Compatible models include:
214 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
215 pca9670, pca9672, pca9674, pca9674a,
218 16 bits: pcf8575, pcf8575c, pca8575,
219 pca9671, pca9673, pca9675
221 Your board setup code will need to declare the expanders in
222 use, and assign numbers to the GPIOs they expose. Those GPIOs
223 can then be used from drivers and other kernel code, just like
224 other GPIOs, but only accessible from task contexts.
226 This driver provides an in-kernel interface to those GPIOs using
227 platform-neutral GPIO calls.
230 bool "Semtech SX150x I2C GPIO expander"
234 Say yes here to provide support for Semtech SX150-series I2C
235 GPIO expanders. Compatible models include:
244 This enables support for the GPIOs found on the STMPE I/O
249 depends on MFD_TC3589X
251 This enables support for the GPIOs found on the TC3589X
255 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
256 depends on TWL4030_CORE
258 Say yes here to access the GPIO signals of various multi-function
259 power management chips from Texas Instruments.
262 tristate "WM831x GPIOs"
263 depends on MFD_WM831X
265 Say yes here to access the GPIO signals of WM831x power management
266 chips from Wolfson Microelectronics.
269 tristate "WM8350 GPIOs"
270 depends on MFD_WM8350
272 Say yes here to access the GPIO signals of WM8350 power management
273 chips from Wolfson Microelectronics.
276 tristate "WM8994 GPIOs"
277 depends on MFD_WM8994
279 Say yes here to access the GPIO signals of WM8994 audio hub
280 CODECs from Wolfson Microelectronics.
283 tristate "GPIO Support for ADP5520 PMIC"
284 depends on PMIC_ADP5520
286 This option enables support for on-chip GPIO found
287 on Analog Devices ADP5520 PMICs.
289 To compile this driver as a module, choose M here: the module will
290 be called adp5520-gpio.
293 tristate "ADP5588 I2C GPIO expander"
296 This option enables support for 18 GPIOs found
297 on Analog Devices ADP5588 GPIO Expanders.
298 To compile this driver as a module, choose M here: the module will be
301 config GPIO_ADP5588_IRQ
302 bool "Interrupt controller support for ADP5588"
303 depends on GPIO_ADP5588=y
305 Say yes here to enable the adp5588 to be used as an interrupt
306 controller. It requires the driver to be built in the kernel.
308 comment "PCI GPIO expanders:"
311 tristate "AMD CS5535/CS5536 GPIO support"
312 depends on PCI && X86 && !CS5535_GPIO && MFD_CS5535
314 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
315 can be used for quite a number of things. The CS5535/6 is found on
316 AMD Geode and Lemote Yeeloong devices.
321 tristate "BT8XX GPIO abuser"
322 depends on PCI && VIDEO_BT848=n
324 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
325 as a cheap PCI GPIO card.
327 This chip can be found on Miro, Hauppauge and STB TV-cards.
329 The card needs to be physically altered for using it as a
330 GPIO card. For more information on how to build a GPIO card
331 from a BT8xx TV card, see the documentation file at
332 Documentation/bt8xxgpio.txt
337 bool "Intel Langwell/Penwell GPIO support"
338 depends on PCI && X86
340 Say Y here to support Intel Langwell/Penwell GPIO.
343 tristate "PCH GPIO of Intel Topcliff"
344 depends on PCI && X86
346 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff
347 which is an IOH(Input/Output Hub) for x86 embedded processor.
348 This driver can access PCH GPIO device.
351 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support"
354 ML7213 is companion chip for Intel Atom E6xx series.
355 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output
356 Hub) which is for IVI(In-Vehicle Infotainment) use.
357 This driver can access the IOH's GPIO device.
359 config GPIO_TIMBERDALE
360 bool "Support for timberdale GPIO IP"
361 depends on MFD_TIMBERDALE && HAS_IOMEM
363 Add support for the GPIO IP in the timberdale FPGA.
366 tristate "RDC R-321x GPIO support"
372 Support for the RDC R321x SoC GPIOs over southbridge
373 PCI configuration space.
375 comment "SPI GPIO expanders:"
378 tristate "Maxim MAX7301 GPIO expander"
379 depends on SPI_MASTER
382 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
385 tristate "Microchip MCP23Sxx I/O expander"
386 depends on SPI_MASTER
388 SPI driver for Microchip MCP23S08/MPC23S17 I/O expanders.
389 This provides a GPIO interface supporting inputs and outputs.
392 tristate "Freescale MC33880 high-side/low-side switch"
393 depends on SPI_MASTER
395 SPI driver for Freescale MC33880 high-side/low-side switch.
396 This provides GPIO interface supporting inputs and outputs.
399 tristate "74x164 serial-in/parallel-out 8-bits shift register"
400 depends on SPI_MASTER
402 Platform driver for 74x164 compatible serial-in/parallel-out
403 8-outputs shift registers. This driver can be used to provide access
404 to more gpio outputs.
406 comment "AC97 GPIO expanders:"
409 bool "Philips UCB1400 GPIO"
410 depends on UCB1400_CORE
412 This enables support for the Philips UCB1400 GPIO pins.
413 The UCB1400 is an AC97 audio codec.
415 To compile this driver as a module, choose M here: the
416 module will be called ucb1400_gpio.
418 comment "MODULbus GPIO expanders:"
421 tristate "Janz VMOD-TTL Digital IO Module"
422 depends on MFD_JANZ_CMODIO
424 This enables support for the Janz VMOD-TTL Digital IO module.
425 This driver provides support for driving the pins in output
426 mode only. Input mode is not supported.
429 bool "ST-Ericsson AB8500 Mixed Signal Circuit gpio functions"
430 depends on AB8500_CORE && BROKEN
432 Select this to enable the AB8500 IC GPIO driver