Kconfig 8.5 KB
Newer Older
1 2 3 4
#
# GPIO infrastructure and expanders
#

M
Michael Buesch 已提交
5
config ARCH_WANT_OPTIONAL_GPIOLIB
6
	bool
M
Michael Buesch 已提交
7 8 9 10 11 12 13 14 15 16 17
	help
	  Select this config option from the architecture Kconfig, if
	  it is possible to use gpiolib on the architecture, but let the
	  user decide whether to actually build it or not.
	  Select this instead of ARCH_REQUIRE_GPIOLIB, if your architecture does
	  not depend on GPIOs being available, but rather let the user
	  decide whether he needs it or not.

config ARCH_REQUIRE_GPIOLIB
	bool
	select GPIOLIB
18 19 20 21
	help
	  Platforms select gpiolib if they use this infrastructure
	  for all their GPIOs, usually starting with ones integrated
	  into SOC processors.
M
Michael Buesch 已提交
22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
	  Selecting this from the architecture code will cause the gpiolib
	  code to always get built in.



menuconfig GPIOLIB
	bool "GPIO Support"
	depends on ARCH_WANT_OPTIONAL_GPIOLIB || ARCH_REQUIRE_GPIOLIB
	select GENERIC_GPIO
	help
	  This enables GPIO support through the generic GPIO library.
	  You only need to enable this, if you also want to enable
	  one or more of the GPIO expansion card drivers below.

	  If unsure, say N.
37

M
Michael Buesch 已提交
38
if GPIOLIB
39 40 41 42 43 44

config DEBUG_GPIO
	bool "Debug GPIO calls"
	depends on DEBUG_KERNEL
	help
	  Say Y here to add some extra checks and diagnostics to GPIO calls.
45 46 47
	  These checks help ensure that GPIOs have been properly initialized
	  before they are used, and that sleeping calls are not made from
	  non-sleeping contexts.  They can make bitbanged serial protocols
48 49 50
	  slower.  The diagnostics help catch the type of setup errors
	  that are most common when setting up new platforms or boards.

D
David Brownell 已提交
51 52 53 54 55 56 57 58 59 60 61 62 63 64 65
config GPIO_SYSFS
	bool "/sys/class/gpio/... (sysfs interface)"
	depends on SYSFS && EXPERIMENTAL
	help
	  Say Y here to add a sysfs interface for GPIOs.

	  This is mostly useful to work around omissions in a system's
	  kernel support.  Those are common in custom and semicustom
	  hardware assembled using standard kernels with a minimum of
	  custom patches.  In those cases, userspace code may import
	  a given GPIO from the kernel, if no kernel driver requested it.

	  Kernel drivers may also request that a particular GPIO be
	  exported to userspace; this can be useful when debugging.

66 67
# put expanders in the right section, in alphabetical order

68 69 70
config GPIO_MAX730X
	tristate

71 72
comment "Memory mapped GPIO expanders:"

73 74 75 76 77 78
config GPIO_IT8761E
	tristate "IT8761E GPIO support"
	depends on GPIOLIB
	help
	  Say yes here to support GPIO functionality of IT8761E super I/O chip.

79 80 81 82 83 84
config GPIO_PL061
	bool "PrimeCell PL061 GPIO support"
	depends on ARM_AMBA
	help
	  Say yes here to support the PrimeCell PL061 GPIO device

85 86
config GPIO_XILINX
	bool "Xilinx GPIO support"
87
	depends on PPC_OF || MICROBLAZE
88 89 90
	help
	  Say yes here to support the Xilinx FPGA GPIO device

91 92 93 94 95 96
config GPIO_VR41XX
	tristate "NEC VR4100 series General-purpose I/O Uint support"
	depends on CPU_VR41XX
	help
	  Say yes here to support the NEC VR4100 series General-purpose I/O Uint

97 98
comment "I2C GPIO expanders:"

99 100 101 102 103 104 105
config GPIO_MAX7300
	tristate "Maxim MAX7300 GPIO expander"
	depends on I2C
	select GPIO_MAX730X
	help
	  GPIO driver for Maxim MAX7301 I2C-based GPIO expander.

E
Eric Miao 已提交
106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124
config GPIO_MAX732X
	tristate "MAX7319, MAX7320-7327 I2C Port Expanders"
	depends on I2C
	help
	  Say yes here to support the MAX7319, MAX7320-7327 series of I2C
	  Port Expanders. Each IO port on these chips has a fixed role of
	  Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
	  Input and Output (designed by 'P'). The combinations are listed
	  below:

	  8 bits:	max7319 (8I), max7320 (8O), max7321 (8P),
		  	max7322 (4I4O), max7323 (4P4O)

	  16 bits:	max7324 (8I8O), max7325 (8P8O),
		  	max7326 (4I12O), max7327 (4P12O)

	  Board setup code must specify the model to use, and the start
	  number for these GPIOs.

125
config GPIO_PCA953X
126
	tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports"
127 128
	depends on I2C
	help
129 130 131 132 133 134
	  Say yes here to provide access to several register-oriented
	  SMBus I/O expanders, made mostly by NXP or TI.  Compatible
	  models include:

	  4 bits:	pca9536, pca9537

135 136
	  8 bits:	max7310, pca9534, pca9538, pca9554, pca9557,
	  		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

143 144 145 146 147 148 149
config GPIO_PCA953X_IRQ
	bool "Interrupt controller support for PCA953x"
	depends on GPIO_PCA953X=y
	help
	  Say yes here to enable the pca953x to be used as an interrupt
	  controller. It requires the driver to be built in the kernel.

150
config GPIO_PCF857X
151
	tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders"
152 153 154 155 156 157 158 159
	depends on I2C
	help
	  Say yes here to provide access to most "quasi-bidirectional" I2C
	  GPIO expanders used for additional digital outputs or inputs.
	  Most of these parts are from NXP, though TI is a second source for
	  some of them.  Compatible models include:

	  8 bits:   pcf8574, pcf8574a, pca8574, pca8574a,
160 161
	            pca9670, pca9672, pca9674, pca9674a,
	  	    max7328, max7329
162 163 164 165 166 167 168 169 170 171 172 173

	  16 bits:  pcf8575, pcf8575c, pca8575,
	            pca9671, pca9673, pca9675

	  Your board setup code will need to declare the expanders in
	  use, and assign numbers to the GPIOs they expose.  Those GPIOs
	  can then be used from drivers and other kernel code, just like
	  other GPIOs, but only accessible from task contexts.

	  This driver provides an in-kernel interface to those GPIOs using
	  platform-neutral GPIO calls.

D
David Brownell 已提交
174 175 176 177 178 179 180
config GPIO_TWL4030
	tristate "TWL4030, TWL5030, and TPS659x0 GPIOs"
	depends on TWL4030_CORE
	help
	  Say yes here to access the GPIO signals of various multi-function
	  power management chips from Texas Instruments.

M
Mark Brown 已提交
181 182 183 184 185 186 187
config GPIO_WM831X
	tristate "WM831x GPIOs"
	depends on MFD_WM831X
	help
	  Say yes here to access the GPIO signals of WM831x power management
	  chips from Wolfson Microelectronics.

188 189 190 191 192 193 194
config GPIO_WM8350
	tristate "WM8350 GPIOs"
	depends on MFD_WM8350
	help
	  Say yes here to access the GPIO signals of WM8350 power management
	  chips from Wolfson Microelectronics.

195 196 197 198 199 200 201 202 203 204
config GPIO_ADP5520
	tristate "GPIO Support for ADP5520 PMIC"
	depends on PMIC_ADP5520
	help
	  This option enables support for on-chip GPIO found
	  on Analog Devices ADP5520 PMICs.

	  To compile this driver as a module, choose M here: the module will
	  be called adp5520-gpio.

205 206 207 208 209 210 211 212 213
config GPIO_ADP5588
	tristate "ADP5588 I2C GPIO expander"
	depends on I2C
	help
	  This option enables support for 18 GPIOs found
	  on Analog Devices ADP5588 GPIO Expanders.
	  To compile this driver as a module, choose M here: the module will be
	  called adp5588-gpio.

M
Michael Buesch 已提交
214 215
comment "PCI GPIO expanders:"

216 217
config GPIO_CS5535
	tristate "AMD CS5535/CS5536 GPIO support"
218
	depends on PCI && !CS5535_GPIO
219 220 221 222 223 224 225
	help
	  The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that
	  can be used for quite a number of things.  The CS5535/6 is found on
	  AMD Geode and Lemote Yeeloong devices.

	  If unsure, say N.

M
Michael Buesch 已提交
226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241
config GPIO_BT8XX
	tristate "BT8XX GPIO abuser"
	depends on PCI && VIDEO_BT848=n
	help
	  The BT8xx frame grabber chip has 24 GPIO pins than can be abused
	  as a cheap PCI GPIO card.

	  This chip can be found on Miro, Hauppauge and STB TV-cards.

	  The card needs to be physically altered for using it as a
	  GPIO card. For more information on how to build a GPIO card
	  from a BT8xx TV card, see the documentation file at
	  Documentation/bt8xxgpio.txt

	  If unsure, say N.

242 243 244 245 246 247
config GPIO_LANGWELL
	bool "Intel Moorestown Platform Langwell GPIO support"
	depends on PCI
	help
	  Say Y here to support Intel Moorestown platform GPIO.

248 249 250 251 252 253
config GPIO_TIMBERDALE
	bool "Support for timberdale GPIO IP"
	depends on MFD_TIMBERDALE && GPIOLIB && HAS_IOMEM
	---help---
	Add support for the GPIO IP in the timberdale FPGA.

254 255
comment "SPI GPIO expanders:"

256 257 258
config GPIO_MAX7301
	tristate "Maxim MAX7301 GPIO expander"
	depends on SPI_MASTER
259
	select GPIO_MAX730X
260
	help
261
	  GPIO driver for Maxim MAX7301 SPI-based GPIO expander.
262

263 264 265 266 267 268 269
config GPIO_MCP23S08
	tristate "Microchip MCP23S08 I/O expander"
	depends on SPI_MASTER
	help
	  SPI driver for Microchip MCP23S08 I/O expander.  This provides
	  a GPIO interface supporting inputs and outputs.

R
Richard Röjfors 已提交
270 271 272 273 274 275 276
config GPIO_MC33880
	tristate "Freescale MC33880 high-side/low-side switch"
	depends on SPI_MASTER
	help
	  SPI driver for Freescale MC33880 high-side/low-side switch.
	  This provides GPIO interface supporting inputs and outputs.

277 278 279 280 281 282 283 284 285 286 287 288
comment "AC97 GPIO expanders:"

config GPIO_UCB1400
	bool "Philips UCB1400 GPIO"
	depends on UCB1400_CORE
	help
	  This enables support for the Philips UCB1400 GPIO pins.
	  The UCB1400 is an AC97 audio codec.

	  To compile this driver as a module, choose M here: the
	  module will be called ucb1400_gpio.

M
Michael Buesch 已提交
289
endif