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