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