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