2 # GPIO infrastructure and expanders
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 expansion card 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 expanders in the right section, in alphabetical order
71 comment "Memory mapped GPIO expanders:"
74 tristate "IT8761E GPIO support"
77 Say yes here to support GPIO functionality of IT8761E super I/O chip.
80 bool "PrimeCell PL061 GPIO support"
83 Say yes here to support the PrimeCell PL061 GPIO device
86 bool "Xilinx GPIO support"
87 depends on PPC_OF || MICROBLAZE
89 Say yes here to support the Xilinx FPGA GPIO device
92 tristate "NEC VR4100 series General-purpose I/O Uint support"
95 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
98 tristate "Intel SCH GPIO"
102 Say yes here to support GPIO interface on Intel Poulsbo SCH.
103 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are
104 powered by the core power rail and are turned off during sleep
105 modes (S3 and higher). The remaining four GPIOs are powered by
106 the Intel SCH suspend power supply. These GPIOs remain
107 active during S3. The suspend powered GPIOs can be used to wake the
108 system from the Suspend-to-RAM state.
110 This driver can also be built as a module. If so, the module
111 will be called sch-gpio.
113 comment "I2C GPIO expanders:"
116 tristate "Maxim MAX7300 GPIO expander"
120 GPIO driver for Maxim MAX7301 I2C-based GPIO expander.
123 tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
126 Say yes here to support the MAX7319, MAX7320-7327 series of I2C
127 Port Expanders. Each IO port on these chips has a fixed role of
128 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
129 Input and Output (designed by 'P'). The combinations are listed
132 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
133 max7322 (4I4O), max7323 (4P4O)
135 16 bits: max7324 (8I8O), max7325 (8P8O),
136 max7326 (4I12O), max7327 (4P12O)
138 Board setup code must specify the model to use, and the start
139 number for these GPIOs.
142 tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports"
145 Say yes here to provide access to several register-oriented
146 SMBus I/O expanders, made mostly by NXP or TI. Compatible
149 4 bits: pca9536, pca9537
151 8 bits: max7310, pca9534, pca9538, pca9554, pca9557,
154 16 bits: pca9535, pca9539, pca9555, tca6416
156 This driver can also be built as a module. If so, the module
157 will be called pca953x.
159 config GPIO_PCA953X_IRQ
160 bool "Interrupt controller support for PCA953x"
161 depends on GPIO_PCA953X=y
163 Say yes here to enable the pca953x to be used as an interrupt
164 controller. It requires the driver to be built in the kernel.
167 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
170 Say yes here to provide access to most "quasi-bidirectional" I2C
171 GPIO expanders used for additional digital outputs or inputs.
172 Most of these parts are from NXP, though TI is a second source for
173 some of them. Compatible models include:
175 8 bits: pcf8574, pcf8574a, pca8574, pca8574a,
176 pca9670, pca9672, pca9674, pca9674a,
179 16 bits: pcf8575, pcf8575c, pca8575,
180 pca9671, pca9673, pca9675
182 Your board setup code will need to declare the expanders in
183 use, and assign numbers to the GPIOs they expose. Those GPIOs
184 can then be used from drivers and other kernel code, just like
185 other GPIOs, but only accessible from task contexts.
187 This driver provides an in-kernel interface to those GPIOs using
188 platform-neutral GPIO calls.
191 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
192 depends on TWL4030_CORE
194 Say yes here to access the GPIO signals of various multi-function
195 power management chips from Texas Instruments.
198 tristate "WM831x GPIOs"
199 depends on MFD_WM831X
201 Say yes here to access the GPIO signals of WM831x power management
202 chips from Wolfson Microelectronics.
205 tristate "WM8350 GPIOs"
206 depends on MFD_WM8350
208 Say yes here to access the GPIO signals of WM8350 power management
209 chips from Wolfson Microelectronics.
212 tristate "WM8994 GPIOs"
213 depends on MFD_WM8994
215 Say yes here to access the GPIO signals of WM8994 audio hub
216 CODECs from Wolfson Microelectronics.
219 tristate "GPIO Support for ADP5520 PMIC"
220 depends on PMIC_ADP5520
222 This option enables support for on-chip GPIO found
223 on Analog Devices ADP5520 PMICs.
225 To compile this driver as a module, choose M here: the module will
226 be called adp5520-gpio.
229 tristate "ADP5588 I2C GPIO expander"
232 This option enables support for 18 GPIOs found
233 on Analog Devices ADP5588 GPIO Expanders.
234 To compile this driver as a module, choose M here: the module will be
237 comment "PCI GPIO expanders:"
240 tristate "AMD CS5535/CS5536 GPIO support"
241 depends on PCI && !CS5535_GPIO
243 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
244 can be used for quite a number of things. The CS5535/6 is found on
245 AMD Geode and Lemote Yeeloong devices.
250 tristate "BT8XX GPIO abuser"
251 depends on PCI && VIDEO_BT848=n
253 The BT8xx frame grabber chip has 24 GPIO pins than can be abused
254 as a cheap PCI GPIO card.
256 This chip can be found on Miro, Hauppauge and STB TV-cards.
258 The card needs to be physically altered for using it as a
259 GPIO card. For more information on how to build a GPIO card
260 from a BT8xx TV card, see the documentation file at
261 Documentation/bt8xxgpio.txt
266 bool "Intel Moorestown Platform Langwell GPIO support"
269 Say Y here to support Intel Moorestown platform GPIO.
271 config GPIO_TIMBERDALE
272 bool "Support for timberdale GPIO IP"
273 depends on MFD_TIMBERDALE && GPIOLIB && HAS_IOMEM
275 Add support for the GPIO IP in the timberdale FPGA.
277 comment "SPI GPIO expanders:"
280 tristate "Maxim MAX7301 GPIO expander"
281 depends on SPI_MASTER
284 GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
287 tristate "Microchip MCP23S08 I/O expander"
288 depends on SPI_MASTER
290 SPI driver for Microchip MCP23S08 I/O expander. This provides
291 a GPIO interface supporting inputs and outputs.
294 tristate "Freescale MC33880 high-side/low-side switch"
295 depends on SPI_MASTER
297 SPI driver for Freescale MC33880 high-side/low-side switch.
298 This provides GPIO interface supporting inputs and outputs.
300 comment "AC97 GPIO expanders:"
303 bool "Philips UCB1400 GPIO"
304 depends on UCB1400_CORE
306 This enables support for the Philips UCB1400 GPIO pins.
307 The UCB1400 is an AC97 audio codec.
309 To compile this driver as a module, choose M here: the
310 module will be called ucb1400_gpio.