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 66# put drivers in the right section, in alphabetical order 67 68config GPIO_MAX730X 69 tristate 70 71comment "Memory mapped GPIO drivers:" 72 73config GPIO_BASIC_MMIO_CORE 74 tristate 75 help 76 Provides core functionality for basic memory-mapped GPIO controllers. 77 78config GPIO_BASIC_MMIO 79 tristate "Basic memory-mapped GPIO controllers support" 80 select GPIO_BASIC_MMIO_CORE 81 help 82 Say yes here to support basic memory-mapped GPIO controllers. 83 84config GPIO_IT8761E 85 tristate "IT8761E GPIO support" 86 help 87 Say yes here to support GPIO functionality of IT8761E super I/O chip. 88 89config GPIO_PLAT_SAMSUNG 90 bool "Samsung SoCs GPIO library support" 91 default y if SAMSUNG_GPIOLIB_4BIT 92 help 93 Say yes here to support Samsung SoCs GPIO library 94 95config GPIO_PL061 96 bool "PrimeCell PL061 GPIO support" 97 depends on ARM_AMBA 98 help 99 Say yes here to support the PrimeCell PL061 GPIO device 100 101config GPIO_XILINX 102 bool "Xilinx GPIO support" 103 depends on PPC_OF || MICROBLAZE 104 help 105 Say yes here to support the Xilinx FPGA GPIO device 106 107config GPIO_VR41XX 108 tristate "NEC VR4100 series General-purpose I/O Uint support" 109 depends on CPU_VR41XX 110 help 111 Say yes here to support the NEC VR4100 series General-purpose I/O Uint 112 113config GPIO_SCH 114 tristate "Intel SCH/TunnelCreek GPIO" 115 depends on PCI && X86 116 select MFD_CORE 117 select LPC_SCH 118 help 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. 129 130 This driver can also be built as a module. If so, the module 131 will be called sch-gpio. 132 133config GPIO_VX855 134 tristate "VIA VX855/VX875 GPIO" 135 depends on MFD_SUPPORT && PCI 136 select MFD_CORE 137 select MFD_VX855 138 help 139 Support access to the VX855/VX875 GPIO lines through the gpio library. 140 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. 144 145comment "I2C GPIO expanders:" 146 147config GPIO_MAX7300 148 tristate "Maxim MAX7300 GPIO expander" 149 depends on I2C 150 select GPIO_MAX730X 151 help 152 GPIO driver for Maxim MAX7301 I2C-based GPIO expander. 153 154config GPIO_MAX732X 155 tristate "MAX7319, MAX7320-7327 I2C Port Expanders" 156 depends on I2C 157 help 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 162 below: 163 164 8 bits: max7319 (8I), max7320 (8O), max7321 (8P), 165 max7322 (4I4O), max7323 (4P4O) 166 167 16 bits: max7324 (8I8O), max7325 (8P8O), 168 max7326 (4I12O), max7327 (4P12O) 169 170 Board setup code must specify the model to use, and the start 171 number for these GPIOs. 172 173config GPIO_MAX732X_IRQ 174 bool "Interrupt controller support for MAX732x" 175 depends on GPIO_MAX732X=y && GENERIC_HARDIRQS 176 help 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. 179 180config GPIO_PCA953X 181 tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports" 182 depends on I2C 183 help 184 Say yes here to provide access to several register-oriented 185 SMBus I/O expanders, made mostly by NXP or TI. Compatible 186 models include: 187 188 4 bits: pca9536, pca9537 189 190 8 bits: max7310, pca9534, pca9538, pca9554, pca9557, 191 tca6408 192 193 16 bits: pca9535, pca9539, pca9555, tca6416 194 195 This driver can also be built as a module. If so, the module 196 will be called pca953x. 197 198config GPIO_PCA953X_IRQ 199 bool "Interrupt controller support for PCA953x" 200 depends on GPIO_PCA953X=y 201 help 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. 204 205config GPIO_PCF857X 206 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders" 207 depends on I2C 208 help 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: 213 214 8 bits: pcf8574, pcf8574a, pca8574, pca8574a, 215 pca9670, pca9672, pca9674, pca9674a, 216 max7328, max7329 217 218 16 bits: pcf8575, pcf8575c, pca8575, 219 pca9671, pca9673, pca9675 220 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. 225 226 This driver provides an in-kernel interface to those GPIOs using 227 platform-neutral GPIO calls. 228 229config GPIO_SX150X 230 bool "Semtech SX150x I2C GPIO expander" 231 depends on I2C=y 232 default n 233 help 234 Say yes here to provide support for Semtech SX150-series I2C 235 GPIO expanders. Compatible models include: 236 237 8 bits: sx1508q 238 16 bits: sx1509q 239 240config GPIO_STMPE 241 bool "STMPE GPIOs" 242 depends on MFD_STMPE 243 help 244 This enables support for the GPIOs found on the STMPE I/O 245 Expanders. 246 247config GPIO_TC3589X 248 bool "TC3589X GPIOs" 249 depends on MFD_TC3589X 250 help 251 This enables support for the GPIOs found on the TC3589X 252 I/O Expander. 253 254config GPIO_TWL4030 255 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs" 256 depends on TWL4030_CORE 257 help 258 Say yes here to access the GPIO signals of various multi-function 259 power management chips from Texas Instruments. 260 261config GPIO_WM831X 262 tristate "WM831x GPIOs" 263 depends on MFD_WM831X 264 help 265 Say yes here to access the GPIO signals of WM831x power management 266 chips from Wolfson Microelectronics. 267 268config GPIO_WM8350 269 tristate "WM8350 GPIOs" 270 depends on MFD_WM8350 271 help 272 Say yes here to access the GPIO signals of WM8350 power management 273 chips from Wolfson Microelectronics. 274 275config GPIO_WM8994 276 tristate "WM8994 GPIOs" 277 depends on MFD_WM8994 278 help 279 Say yes here to access the GPIO signals of WM8994 audio hub 280 CODECs from Wolfson Microelectronics. 281 282config GPIO_ADP5520 283 tristate "GPIO Support for ADP5520 PMIC" 284 depends on PMIC_ADP5520 285 help 286 This option enables support for on-chip GPIO found 287 on Analog Devices ADP5520 PMICs. 288 289 To compile this driver as a module, choose M here: the module will 290 be called adp5520-gpio. 291 292config GPIO_ADP5588 293 tristate "ADP5588 I2C GPIO expander" 294 depends on I2C 295 help 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 299 called adp5588-gpio. 300 301config GPIO_ADP5588_IRQ 302 bool "Interrupt controller support for ADP5588" 303 depends on GPIO_ADP5588=y 304 help 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. 307 308comment "PCI GPIO expanders:" 309 310config GPIO_CS5535 311 tristate "AMD CS5535/CS5536 GPIO support" 312 depends on PCI && X86 && !CS5535_GPIO && MFD_CS5535 313 help 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. 317 318 If unsure, say N. 319 320config GPIO_BT8XX 321 tristate "BT8XX GPIO abuser" 322 depends on PCI && VIDEO_BT848=n 323 help 324 The BT8xx frame grabber chip has 24 GPIO pins than can be abused 325 as a cheap PCI GPIO card. 326 327 This chip can be found on Miro, Hauppauge and STB TV-cards. 328 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 333 334 If unsure, say N. 335 336config GPIO_LANGWELL 337 bool "Intel Langwell/Penwell GPIO support" 338 depends on PCI && X86 339 help 340 Say Y here to support Intel Langwell/Penwell GPIO. 341 342config GPIO_PCH 343 tristate "PCH GPIO of Intel Topcliff" 344 depends on PCI && X86 345 help 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. 349 350config GPIO_ML_IOH 351 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support" 352 depends on PCI 353 help 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. 358 359config GPIO_TIMBERDALE 360 bool "Support for timberdale GPIO IP" 361 depends on MFD_TIMBERDALE && HAS_IOMEM 362 ---help--- 363 Add support for the GPIO IP in the timberdale FPGA. 364 365config GPIO_RDC321X 366 tristate "RDC R-321x GPIO support" 367 depends on PCI 368 select MFD_SUPPORT 369 select MFD_CORE 370 select MFD_RDC321X 371 help 372 Support for the RDC R321x SoC GPIOs over southbridge 373 PCI configuration space. 374 375comment "SPI GPIO expanders:" 376 377config GPIO_MAX7301 378 tristate "Maxim MAX7301 GPIO expander" 379 depends on SPI_MASTER 380 select GPIO_MAX730X 381 help 382 GPIO driver for Maxim MAX7301 SPI-based GPIO expander. 383 384config GPIO_MCP23S08 385 tristate "Microchip MCP23Sxx I/O expander" 386 depends on SPI_MASTER 387 help 388 SPI driver for Microchip MCP23S08/MPC23S17 I/O expanders. 389 This provides a GPIO interface supporting inputs and outputs. 390 391config GPIO_MC33880 392 tristate "Freescale MC33880 high-side/low-side switch" 393 depends on SPI_MASTER 394 help 395 SPI driver for Freescale MC33880 high-side/low-side switch. 396 This provides GPIO interface supporting inputs and outputs. 397 398config GPIO_74X164 399 tristate "74x164 serial-in/parallel-out 8-bits shift register" 400 depends on SPI_MASTER 401 help 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. 405 406comment "AC97 GPIO expanders:" 407 408config GPIO_UCB1400 409 bool "Philips UCB1400 GPIO" 410 depends on UCB1400_CORE 411 help 412 This enables support for the Philips UCB1400 GPIO pins. 413 The UCB1400 is an AC97 audio codec. 414 415 To compile this driver as a module, choose M here: the 416 module will be called ucb1400_gpio. 417 418comment "MODULbus GPIO expanders:" 419 420config GPIO_JANZ_TTL 421 tristate "Janz VMOD-TTL Digital IO Module" 422 depends on MFD_JANZ_CMODIO 423 help 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. 427 428config AB8500_GPIO 429 bool "ST-Ericsson AB8500 Mixed Signal Circuit gpio functions" 430 depends on AB8500_CORE && BROKEN 431 help 432 Select this to enable the AB8500 IC GPIO driver 433endif 434