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