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