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