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