1# 2# GPIO infrastructure and drivers 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 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 66config GPIO_GENERIC 67 tristate 68 69# put drivers in the right section, in alphabetical order 70 71config GPIO_DA9052 72 tristate "Dialog DA9052 GPIO" 73 depends on PMIC_DA9052 && BROKEN 74 help 75 Say yes here to enable the GPIO driver for the DA9052 chip. 76 77config GPIO_MAX730X 78 tristate 79 80comment "Memory mapped GPIO drivers:" 81 82config GPIO_GENERIC_PLATFORM 83 tristate "Generic memory-mapped GPIO controller support (MMIO platform device)" 84 select GPIO_GENERIC 85 help 86 Say yes here to support basic platform_device memory-mapped GPIO controllers. 87 88config GPIO_IT8761E 89 tristate "IT8761E GPIO support" 90 depends on X86 # unconditional access to IO space. 91 help 92 Say yes here to support GPIO functionality of IT8761E super I/O chip. 93 94config GPIO_EP93XX 95 def_bool y 96 depends on ARCH_EP93XX 97 select GPIO_GENERIC 98 99config GPIO_MPC5200 100 def_bool y 101 depends on PPC_MPC52xx 102 103config GPIO_MPC8XXX 104 bool "MPC512x/MPC8xxx GPIO support" 105 depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \ 106 FSL_SOC_BOOKE || PPC_86xx 107 help 108 Say Y here if you're going to use hardware that connects to the 109 MPC512x/831x/834x/837x/8572/8610 GPIOs. 110 111config GPIO_MSM_V1 112 tristate "Qualcomm MSM GPIO v1" 113 depends on GPIOLIB && ARCH_MSM 114 help 115 Say yes here to support the GPIO interface on ARM v6 based 116 Qualcomm MSM chips. Most of the pins on the MSM can be 117 selected for GPIO, and are controlled by this driver. 118 119config GPIO_MSM_V2 120 tristate "Qualcomm MSM GPIO v2" 121 depends on GPIOLIB && ARCH_MSM 122 help 123 Say yes here to support the GPIO interface on ARM v7 based 124 Qualcomm MSM chips. Most of the pins on the MSM can be 125 selected for GPIO, and are controlled by this driver. 126 127config GPIO_MXC 128 def_bool y 129 depends on ARCH_MXC 130 select GPIO_GENERIC 131 select GENERIC_IRQ_CHIP 132 133config GPIO_MXS 134 def_bool y 135 depends on ARCH_MXS 136 select GPIO_GENERIC 137 select GENERIC_IRQ_CHIP 138 139config GPIO_PL061 140 bool "PrimeCell PL061 GPIO support" 141 depends on ARM_AMBA 142 select GENERIC_IRQ_CHIP 143 help 144 Say yes here to support the PrimeCell PL061 GPIO device 145 146config GPIO_PXA 147 bool "PXA GPIO support" 148 depends on ARCH_PXA || ARCH_MMP 149 help 150 Say yes here to support the PXA GPIO device 151 152config GPIO_XILINX 153 bool "Xilinx GPIO support" 154 depends on PPC_OF || MICROBLAZE 155 help 156 Say yes here to support the Xilinx FPGA GPIO device 157 158config GPIO_VR41XX 159 tristate "NEC VR4100 series General-purpose I/O Uint support" 160 depends on CPU_VR41XX 161 help 162 Say yes here to support the NEC VR4100 series General-purpose I/O Uint 163 164config GPIO_SCH 165 tristate "Intel SCH/TunnelCreek GPIO" 166 depends on PCI && X86 167 select MFD_CORE 168 select LPC_SCH 169 help 170 Say yes here to support GPIO interface on Intel Poulsbo SCH 171 or Intel Tunnel Creek processor. 172 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are 173 powered by the core power rail and are turned off during sleep 174 modes (S3 and higher). The remaining four GPIOs are powered by 175 the Intel SCH suspend power supply. These GPIOs remain 176 active during S3. The suspend powered GPIOs can be used to wake the 177 system from the Suspend-to-RAM state. 178 The Intel Tunnel Creek processor has 5 GPIOs powered by the 179 core power rail and 9 from suspend power supply. 180 181config GPIO_VX855 182 tristate "VIA VX855/VX875 GPIO" 183 depends on PCI 184 select MFD_CORE 185 select MFD_VX855 186 help 187 Support access to the VX855/VX875 GPIO lines through the gpio library. 188 189 This driver provides common support for accessing the device, 190 additional drivers must be enabled in order to use the 191 functionality of the device. 192 193config GPIO_GE_FPGA 194 bool "GE FPGA based GPIO" 195 depends on GE_FPGA 196 help 197 Support for common GPIO functionality provided on some GE Single Board 198 Computers. 199 200 This driver provides basic support (configure as input or output, read 201 and write pin state) for GPIO implemented in a number of GE single 202 board computers. 203 204comment "I2C GPIO expanders:" 205 206config GPIO_MAX7300 207 tristate "Maxim MAX7300 GPIO expander" 208 depends on I2C 209 select GPIO_MAX730X 210 help 211 GPIO driver for Maxim MAX7301 I2C-based GPIO expander. 212 213config GPIO_MAX732X 214 tristate "MAX7319, MAX7320-7327 I2C Port Expanders" 215 depends on I2C 216 help 217 Say yes here to support the MAX7319, MAX7320-7327 series of I2C 218 Port Expanders. Each IO port on these chips has a fixed role of 219 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain 220 Input and Output (designed by 'P'). The combinations are listed 221 below: 222 223 8 bits: max7319 (8I), max7320 (8O), max7321 (8P), 224 max7322 (4I4O), max7323 (4P4O) 225 226 16 bits: max7324 (8I8O), max7325 (8P8O), 227 max7326 (4I12O), max7327 (4P12O) 228 229 Board setup code must specify the model to use, and the start 230 number for these GPIOs. 231 232config GPIO_MAX732X_IRQ 233 bool "Interrupt controller support for MAX732x" 234 depends on GPIO_MAX732X=y && GENERIC_HARDIRQS 235 help 236 Say yes here to enable the max732x to be used as an interrupt 237 controller. It requires the driver to be built in the kernel. 238 239config GPIO_MC9S08DZ60 240 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions" 241 depends on I2C && MACH_MX35_3DS 242 help 243 Select this to enable the MC9S08DZ60 GPIO driver 244 245config GPIO_PCA953X 246 tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports" 247 depends on I2C 248 help 249 Say yes here to provide access to several register-oriented 250 SMBus I/O expanders, made mostly by NXP or TI. Compatible 251 models include: 252 253 4 bits: pca9536, pca9537 254 255 8 bits: max7310, pca9534, pca9538, pca9554, pca9557, 256 tca6408 257 258 16 bits: pca9535, pca9539, pca9555, tca6416 259 260config GPIO_PCA953X_IRQ 261 bool "Interrupt controller support for PCA953x" 262 depends on GPIO_PCA953X=y 263 help 264 Say yes here to enable the pca953x to be used as an interrupt 265 controller. It requires the driver to be built in the kernel. 266 267config GPIO_PCF857X 268 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders" 269 depends on I2C 270 help 271 Say yes here to provide access to most "quasi-bidirectional" I2C 272 GPIO expanders used for additional digital outputs or inputs. 273 Most of these parts are from NXP, though TI is a second source for 274 some of them. Compatible models include: 275 276 8 bits: pcf8574, pcf8574a, pca8574, pca8574a, 277 pca9670, pca9672, pca9674, pca9674a, 278 max7328, max7329 279 280 16 bits: pcf8575, pcf8575c, pca8575, 281 pca9671, pca9673, pca9675 282 283 Your board setup code will need to declare the expanders in 284 use, and assign numbers to the GPIOs they expose. Those GPIOs 285 can then be used from drivers and other kernel code, just like 286 other GPIOs, but only accessible from task contexts. 287 288 This driver provides an in-kernel interface to those GPIOs using 289 platform-neutral GPIO calls. 290 291config GPIO_SX150X 292 bool "Semtech SX150x I2C GPIO expander" 293 depends on I2C=y 294 default n 295 help 296 Say yes here to provide support for Semtech SX150-series I2C 297 GPIO expanders. Compatible models include: 298 299 8 bits: sx1508q 300 16 bits: sx1509q 301 302config GPIO_STMPE 303 bool "STMPE GPIOs" 304 depends on MFD_STMPE 305 help 306 This enables support for the GPIOs found on the STMPE I/O 307 Expanders. 308 309config GPIO_TC3589X 310 bool "TC3589X GPIOs" 311 depends on MFD_TC3589X 312 help 313 This enables support for the GPIOs found on the TC3589X 314 I/O Expander. 315 316config GPIO_TPS65912 317 tristate "TI TPS65912 GPIO" 318 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI) 319 help 320 This driver supports TPS65912 gpio chip 321 322config GPIO_TWL4030 323 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs" 324 depends on TWL4030_CORE 325 help 326 Say yes here to access the GPIO signals of various multi-function 327 power management chips from Texas Instruments. 328 329config GPIO_WM831X 330 tristate "WM831x GPIOs" 331 depends on MFD_WM831X 332 help 333 Say yes here to access the GPIO signals of WM831x power management 334 chips from Wolfson Microelectronics. 335 336config GPIO_WM8350 337 tristate "WM8350 GPIOs" 338 depends on MFD_WM8350 339 help 340 Say yes here to access the GPIO signals of WM8350 power management 341 chips from Wolfson Microelectronics. 342 343config GPIO_WM8994 344 tristate "WM8994 GPIOs" 345 depends on MFD_WM8994 346 help 347 Say yes here to access the GPIO signals of WM8994 audio hub 348 CODECs from Wolfson Microelectronics. 349 350config GPIO_ADP5520 351 tristate "GPIO Support for ADP5520 PMIC" 352 depends on PMIC_ADP5520 353 help 354 This option enables support for on-chip GPIO found 355 on Analog Devices ADP5520 PMICs. 356 357config GPIO_ADP5588 358 tristate "ADP5588 I2C GPIO expander" 359 depends on I2C 360 help 361 This option enables support for 18 GPIOs found 362 on Analog Devices ADP5588 GPIO Expanders. 363 364config GPIO_ADP5588_IRQ 365 bool "Interrupt controller support for ADP5588" 366 depends on GPIO_ADP5588=y 367 help 368 Say yes here to enable the adp5588 to be used as an interrupt 369 controller. It requires the driver to be built in the kernel. 370 371comment "PCI GPIO expanders:" 372 373config GPIO_CS5535 374 tristate "AMD CS5535/CS5536 GPIO support" 375 depends on PCI && X86 && MFD_CS5535 376 help 377 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that 378 can be used for quite a number of things. The CS5535/6 is found on 379 AMD Geode and Lemote Yeeloong devices. 380 381 If unsure, say N. 382 383config GPIO_BT8XX 384 tristate "BT8XX GPIO abuser" 385 depends on PCI && VIDEO_BT848=n 386 help 387 The BT8xx frame grabber chip has 24 GPIO pins than can be abused 388 as a cheap PCI GPIO card. 389 390 This chip can be found on Miro, Hauppauge and STB TV-cards. 391 392 The card needs to be physically altered for using it as a 393 GPIO card. For more information on how to build a GPIO card 394 from a BT8xx TV card, see the documentation file at 395 Documentation/bt8xxgpio.txt 396 397 If unsure, say N. 398 399config GPIO_LANGWELL 400 bool "Intel Langwell/Penwell GPIO support" 401 depends on PCI && X86 402 help 403 Say Y here to support Intel Langwell/Penwell GPIO. 404 405config GPIO_PCH 406 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO" 407 depends on PCI && X86 408 select GENERIC_IRQ_CHIP 409 help 410 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff 411 which is an IOH(Input/Output Hub) for x86 embedded processor. 412 This driver can access PCH GPIO device. 413 414 This driver also can be used for LAPIS Semiconductor IOH(Input/ 415 Output Hub), ML7223 and ML7831. 416 ML7223 IOH is for MP(Media Phone) use. 417 ML7831 IOH is for general purpose use. 418 ML7223/ML7831 is companion chip for Intel Atom E6xx series. 419 ML7223/ML7831 is completely compatible for Intel EG20T PCH. 420 421config GPIO_ML_IOH 422 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support" 423 depends on PCI 424 select GENERIC_IRQ_CHIP 425 help 426 ML7213 is companion chip for Intel Atom E6xx series. 427 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output 428 Hub) which is for IVI(In-Vehicle Infotainment) use. 429 This driver can access the IOH's GPIO device. 430 431config GPIO_SODAVILLE 432 bool "Intel Sodaville GPIO support" 433 depends on X86 && PCI && OF 434 select GPIO_GENERIC 435 select GENERIC_IRQ_CHIP 436 help 437 Say Y here to support Intel Sodaville GPIO. 438 439config GPIO_TIMBERDALE 440 bool "Support for timberdale GPIO IP" 441 depends on MFD_TIMBERDALE && HAS_IOMEM 442 ---help--- 443 Add support for the GPIO IP in the timberdale FPGA. 444 445config GPIO_RDC321X 446 tristate "RDC R-321x GPIO support" 447 depends on PCI 448 select MFD_CORE 449 select MFD_RDC321X 450 help 451 Support for the RDC R321x SoC GPIOs over southbridge 452 PCI configuration space. 453 454comment "SPI GPIO expanders:" 455 456config GPIO_MAX7301 457 tristate "Maxim MAX7301 GPIO expander" 458 depends on SPI_MASTER 459 select GPIO_MAX730X 460 help 461 GPIO driver for Maxim MAX7301 SPI-based GPIO expander. 462 463config GPIO_MCP23S08 464 tristate "Microchip MCP23xxx I/O expander" 465 depends on SPI_MASTER || I2C 466 help 467 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017 468 I/O expanders. 469 This provides a GPIO interface supporting inputs and outputs. 470 471config GPIO_MC33880 472 tristate "Freescale MC33880 high-side/low-side switch" 473 depends on SPI_MASTER 474 help 475 SPI driver for Freescale MC33880 high-side/low-side switch. 476 This provides GPIO interface supporting inputs and outputs. 477 478config GPIO_74X164 479 tristate "74x164 serial-in/parallel-out 8-bits shift register" 480 depends on SPI_MASTER 481 help 482 Platform driver for 74x164 compatible serial-in/parallel-out 483 8-outputs shift registers. This driver can be used to provide access 484 to more gpio outputs. 485 486comment "AC97 GPIO expanders:" 487 488config GPIO_UCB1400 489 bool "Philips UCB1400 GPIO" 490 depends on UCB1400_CORE 491 help 492 This enables support for the Philips UCB1400 GPIO pins. 493 The UCB1400 is an AC97 audio codec. 494 495comment "MODULbus GPIO expanders:" 496 497config GPIO_JANZ_TTL 498 tristate "Janz VMOD-TTL Digital IO Module" 499 depends on MFD_JANZ_CMODIO 500 help 501 This enables support for the Janz VMOD-TTL Digital IO module. 502 This driver provides support for driving the pins in output 503 mode only. Input mode is not supported. 504 505config GPIO_AB8500 506 bool "ST-Ericsson AB8500 Mixed Signal Circuit gpio functions" 507 depends on AB8500_CORE && BROKEN 508 help 509 Select this to enable the AB8500 IC GPIO driver 510 511config GPIO_TPS65910 512 bool "TPS65910 GPIO" 513 depends on MFD_TPS65910 514 help 515 Select this option to enable GPIO driver for the TPS65910 516 chip family. 517endif 518