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