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