| 1 | # |
| 2 | # GPIO infrastructure and expanders |
| 3 | # |
| 4 | |
| 5 | config HAVE_GPIO_LIB |
| 6 | bool |
| 7 | help |
| 8 | Platforms select gpiolib if they use this infrastructure |
| 9 | for all their GPIOs, usually starting with ones integrated |
| 10 | into SOC processors. |
| 11 | |
| 12 | menu "GPIO Support" |
| 13 | depends on HAVE_GPIO_LIB |
| 14 | |
| 15 | config DEBUG_GPIO |
| 16 | bool "Debug GPIO calls" |
| 17 | depends on DEBUG_KERNEL |
| 18 | help |
| 19 | Say Y here to add some extra checks and diagnostics to GPIO calls. |
| 20 | The checks help ensure that GPIOs have been properly initialized |
| 21 | before they are used and that sleeping calls aren not made from |
| 22 | nonsleeping contexts. They can make bitbanged serial protocols |
| 23 | slower. The diagnostics help catch the type of setup errors |
| 24 | that are most common when setting up new platforms or boards. |
| 25 | |
| 26 | # put expanders in the right section, in alphabetical order |
| 27 | |
| 28 | comment "I2C GPIO expanders:" |
| 29 | |
| 30 | config GPIO_PCA953X |
| 31 | tristate "PCA953x, PCA955x, and MAX7310 I/O ports" |
| 32 | depends on I2C |
| 33 | help |
| 34 | Say yes here to provide access to several register-oriented |
| 35 | SMBus I/O expanders, made mostly by NXP or TI. Compatible |
| 36 | models include: |
| 37 | |
| 38 | 4 bits: pca9536, pca9537 |
| 39 | |
| 40 | 8 bits: max7310, pca9534, pca9538, pca9554, pca9557 |
| 41 | |
| 42 | 16 bits: pca9535, pca9539, pca9555 |
| 43 | |
| 44 | This driver can also be built as a module. If so, the module |
| 45 | will be called pca953x. |
| 46 | |
| 47 | config GPIO_PCF857X |
| 48 | tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders" |
| 49 | depends on I2C |
| 50 | help |
| 51 | Say yes here to provide access to most "quasi-bidirectional" I2C |
| 52 | GPIO expanders used for additional digital outputs or inputs. |
| 53 | Most of these parts are from NXP, though TI is a second source for |
| 54 | some of them. Compatible models include: |
| 55 | |
| 56 | 8 bits: pcf8574, pcf8574a, pca8574, pca8574a, |
| 57 | pca9670, pca9672, pca9674, pca9674a, |
| 58 | max7328, max7329 |
| 59 | |
| 60 | 16 bits: pcf8575, pcf8575c, pca8575, |
| 61 | pca9671, pca9673, pca9675 |
| 62 | |
| 63 | Your board setup code will need to declare the expanders in |
| 64 | use, and assign numbers to the GPIOs they expose. Those GPIOs |
| 65 | can then be used from drivers and other kernel code, just like |
| 66 | other GPIOs, but only accessible from task contexts. |
| 67 | |
| 68 | This driver provides an in-kernel interface to those GPIOs using |
| 69 | platform-neutral GPIO calls. |
| 70 | |
| 71 | comment "SPI GPIO expanders:" |
| 72 | |
| 73 | config GPIO_MAX7301 |
| 74 | tristate "Maxim MAX7301 GPIO expander" |
| 75 | depends on SPI_MASTER |
| 76 | help |
| 77 | gpio driver for Maxim MAX7301 SPI GPIO expander. |
| 78 | |
| 79 | config GPIO_MCP23S08 |
| 80 | tristate "Microchip MCP23S08 I/O expander" |
| 81 | depends on SPI_MASTER |
| 82 | help |
| 83 | SPI driver for Microchip MCP23S08 I/O expander. This provides |
| 84 | a GPIO interface supporting inputs and outputs. |
| 85 | |
| 86 | endmenu |