1# 2# GPIO infrastructure and drivers 3# 4 5config ARCH_HAVE_CUSTOM_GPIO_H 6 bool 7 help 8 Selecting this config option from the architecture Kconfig allows 9 the architecture to provide a custom asm/gpio.h implementation 10 overriding the default implementations. New uses of this are 11 strongly discouraged. 12 13config ARCH_WANT_OPTIONAL_GPIOLIB 14 bool 15 help 16 Select this config option from the architecture Kconfig, if 17 it is possible to use gpiolib on the architecture, but let the 18 user decide whether to actually build it or not. 19 Select this instead of ARCH_REQUIRE_GPIOLIB, if your architecture does 20 not depend on GPIOs being available, but rather let the user 21 decide whether he needs it or not. 22 23config ARCH_REQUIRE_GPIOLIB 24 bool 25 select GPIOLIB 26 help 27 Platforms select gpiolib if they use this infrastructure 28 for all their GPIOs, usually starting with ones integrated 29 into SOC processors. 30 Selecting this from the architecture code will cause the gpiolib 31 code to always get built in. 32 33config GPIO_DEVRES 34 def_bool y 35 depends on HAS_IOMEM 36 37 38menuconfig GPIOLIB 39 bool "GPIO Support" 40 depends on ARCH_WANT_OPTIONAL_GPIOLIB || ARCH_REQUIRE_GPIOLIB 41 select GENERIC_GPIO 42 help 43 This enables GPIO support through the generic GPIO library. 44 You only need to enable this, if you also want to enable 45 one or more of the GPIO drivers below. 46 47 If unsure, say N. 48 49if GPIOLIB 50 51config OF_GPIO 52 def_bool y 53 depends on OF 54 55config GPIO_ACPI 56 def_bool y 57 depends on ACPI 58 59config DEBUG_GPIO 60 bool "Debug GPIO calls" 61 depends on DEBUG_KERNEL 62 help 63 Say Y here to add some extra checks and diagnostics to GPIO calls. 64 These checks help ensure that GPIOs have been properly initialized 65 before they are used, and that sleeping calls are not made from 66 non-sleeping contexts. They can make bitbanged serial protocols 67 slower. The diagnostics help catch the type of setup errors 68 that are most common when setting up new platforms or boards. 69 70config GPIO_SYSFS 71 bool "/sys/class/gpio/... (sysfs interface)" 72 depends on SYSFS 73 help 74 Say Y here to add a sysfs interface for GPIOs. 75 76 This is mostly useful to work around omissions in a system's 77 kernel support. Those are common in custom and semicustom 78 hardware assembled using standard kernels with a minimum of 79 custom patches. In those cases, userspace code may import 80 a given GPIO from the kernel, if no kernel driver requested it. 81 82 Kernel drivers may also request that a particular GPIO be 83 exported to userspace; this can be useful when debugging. 84 85config GPIO_GENERIC 86 tristate 87 88# put drivers in the right section, in alphabetical order 89 90config GPIO_DA9052 91 tristate "Dialog DA9052 GPIO" 92 depends on PMIC_DA9052 93 help 94 Say yes here to enable the GPIO driver for the DA9052 chip. 95 96config GPIO_DA9055 97 tristate "Dialog Semiconductor DA9055 GPIO" 98 depends on MFD_DA9055 99 help 100 Say yes here to enable the GPIO driver for the DA9055 chip. 101 102 The Dialog DA9055 PMIC chip has 3 GPIO pins that can be 103 be controller by this driver. 104 105 If driver is built as a module it will be called gpio-da9055. 106 107config GPIO_MAX730X 108 tristate 109 110comment "Memory mapped GPIO drivers:" 111 112config GPIO_CLPS711X 113 def_bool y 114 depends on ARCH_CLPS711X 115 116config GPIO_GENERIC_PLATFORM 117 tristate "Generic memory-mapped GPIO controller support (MMIO platform device)" 118 select GPIO_GENERIC 119 help 120 Say yes here to support basic platform_device memory-mapped GPIO controllers. 121 122config GPIO_IT8761E 123 tristate "IT8761E GPIO support" 124 depends on X86 # unconditional access to IO space. 125 help 126 Say yes here to support GPIO functionality of IT8761E super I/O chip. 127 128config GPIO_EM 129 tristate "Emma Mobile GPIO" 130 depends on ARM 131 help 132 Say yes here to support GPIO on Renesas Emma Mobile SoCs. 133 134config GPIO_EP93XX 135 def_bool y 136 depends on ARCH_EP93XX 137 select GPIO_GENERIC 138 139config GPIO_MM_LANTIQ 140 bool "Lantiq Memory mapped GPIOs" 141 depends on LANTIQ && SOC_XWAY 142 help 143 This enables support for memory mapped GPIOs on the External Bus Unit 144 (EBU) found on Lantiq SoCs. The gpios are output only as they are 145 created by attaching a 16bit latch to the bus. 146 147config GPIO_MPC5200 148 def_bool y 149 depends on PPC_MPC52xx 150 151config GPIO_MPC8XXX 152 bool "MPC512x/MPC8xxx GPIO support" 153 depends on PPC_MPC512x || PPC_MPC831x || PPC_MPC834x || PPC_MPC837x || \ 154 FSL_SOC_BOOKE || PPC_86xx 155 help 156 Say Y here if you're going to use hardware that connects to the 157 MPC512x/831x/834x/837x/8572/8610 GPIOs. 158 159config GPIO_MSM_V1 160 tristate "Qualcomm MSM GPIO v1" 161 depends on GPIOLIB && ARCH_MSM && (ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50) 162 help 163 Say yes here to support the GPIO interface on ARM v6 based 164 Qualcomm MSM chips. Most of the pins on the MSM can be 165 selected for GPIO, and are controlled by this driver. 166 167config GPIO_MSM_V2 168 tristate "Qualcomm MSM GPIO v2" 169 depends on GPIOLIB && ARCH_MSM 170 help 171 Say yes here to support the GPIO interface on ARM v7 based 172 Qualcomm MSM chips. Most of the pins on the MSM can be 173 selected for GPIO, and are controlled by this driver. 174 175config GPIO_MVEBU 176 def_bool y 177 depends on PLAT_ORION 178 depends on OF 179 select GPIO_GENERIC 180 select GENERIC_IRQ_CHIP 181 182config GPIO_MXC 183 def_bool y 184 depends on ARCH_MXC 185 select GPIO_GENERIC 186 select GENERIC_IRQ_CHIP 187 188config GPIO_MXS 189 def_bool y 190 depends on ARCH_MXS 191 select GPIO_GENERIC 192 select GENERIC_IRQ_CHIP 193 194config GPIO_PL061 195 bool "PrimeCell PL061 GPIO support" 196 depends on ARM && ARM_AMBA 197 select GENERIC_IRQ_CHIP 198 help 199 Say yes here to support the PrimeCell PL061 GPIO device 200 201config GPIO_PXA 202 bool "PXA GPIO support" 203 depends on ARCH_PXA || ARCH_MMP 204 help 205 Say yes here to support the PXA GPIO device 206 207config GPIO_SPEAR_SPICS 208 bool "ST SPEAr13xx SPI Chip Select as GPIO support" 209 depends on PLAT_SPEAR 210 select GENERIC_IRQ_CHIP 211 help 212 Say yes here to support ST SPEAr SPI Chip Select as GPIO device 213 214config GPIO_STA2X11 215 bool "STA2x11/ConneXt GPIO support" 216 depends on MFD_STA2X11 217 select GENERIC_IRQ_CHIP 218 help 219 Say yes here to support the STA2x11/ConneXt GPIO device. 220 The GPIO module has 128 GPIO pins with alternate functions. 221 222config GPIO_TS5500 223 tristate "TS-5500 DIO blocks and compatibles" 224 help 225 This driver supports Digital I/O exposed by pin blocks found on some 226 Technologic Systems platforms. It includes, but is not limited to, 3 227 blocks of the TS-5500: DIO1, DIO2 and the LCD port, and the TS-5600 228 LCD port. 229 230config GPIO_VT8500 231 bool "VIA/Wondermedia SoC GPIO Support" 232 depends on ARCH_VT8500 233 help 234 Say yes here to support the VT8500/WM8505/WM8650 GPIO controller. 235 236config GPIO_XILINX 237 bool "Xilinx GPIO support" 238 depends on PPC_OF || MICROBLAZE 239 help 240 Say yes here to support the Xilinx FPGA GPIO device 241 242config GPIO_VR41XX 243 tristate "NEC VR4100 series General-purpose I/O Uint support" 244 depends on CPU_VR41XX 245 help 246 Say yes here to support the NEC VR4100 series General-purpose I/O Uint 247 248config GPIO_SCH 249 tristate "Intel SCH/TunnelCreek/Centerton GPIO" 250 depends on PCI && X86 251 select MFD_CORE 252 select LPC_SCH 253 help 254 Say yes here to support GPIO interface on Intel Poulsbo SCH, 255 Intel Tunnel Creek processor or Intel Centerton processor. 256 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are 257 powered by the core power rail and are turned off during sleep 258 modes (S3 and higher). The remaining four GPIOs are powered by 259 the Intel SCH suspend power supply. These GPIOs remain 260 active during S3. The suspend powered GPIOs can be used to wake the 261 system from the Suspend-to-RAM state. 262 The Intel Tunnel Creek processor has 5 GPIOs powered by the 263 core power rail and 9 from suspend power supply. 264 The Intel Centerton processor has a total of 30 GPIO pins. 265 Twenty-one are powered by the core power rail and 9 from the 266 suspend power supply. 267 268config GPIO_ICH 269 tristate "Intel ICH GPIO" 270 depends on PCI && X86 271 select MFD_CORE 272 select LPC_ICH 273 help 274 Say yes here to support the GPIO functionality of a number of Intel 275 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8 276 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg 277 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake). 278 279 If unsure, say N. 280 281config GPIO_VX855 282 tristate "VIA VX855/VX875 GPIO" 283 depends on PCI && GENERIC_HARDIRQS 284 select MFD_CORE 285 select MFD_VX855 286 help 287 Support access to the VX855/VX875 GPIO lines through the gpio library. 288 289 This driver provides common support for accessing the device, 290 additional drivers must be enabled in order to use the 291 functionality of the device. 292 293config GPIO_GE_FPGA 294 bool "GE FPGA based GPIO" 295 depends on GE_FPGA 296 help 297 Support for common GPIO functionality provided on some GE Single Board 298 Computers. 299 300 This driver provides basic support (configure as input or output, read 301 and write pin state) for GPIO implemented in a number of GE single 302 board computers. 303 304config GPIO_LYNXPOINT 305 bool "Intel Lynxpoint GPIO support" 306 depends on ACPI && X86 307 select IRQ_DOMAIN 308 help 309 driver for GPIO functionality on Intel Lynxpoint PCH chipset 310 Requires ACPI device enumeration code to set up a platform device. 311 312comment "I2C GPIO expanders:" 313 314config GPIO_ARIZONA 315 tristate "Wolfson Microelectronics Arizona class devices" 316 depends on MFD_ARIZONA 317 help 318 Support for GPIOs on Wolfson Arizona class devices. 319 320config GPIO_MAX7300 321 tristate "Maxim MAX7300 GPIO expander" 322 depends on I2C 323 select GPIO_MAX730X 324 help 325 GPIO driver for Maxim MAX7301 I2C-based GPIO expander. 326 327config GPIO_MAX732X 328 tristate "MAX7319, MAX7320-7327 I2C Port Expanders" 329 depends on I2C 330 help 331 Say yes here to support the MAX7319, MAX7320-7327 series of I2C 332 Port Expanders. Each IO port on these chips has a fixed role of 333 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain 334 Input and Output (designed by 'P'). The combinations are listed 335 below: 336 337 8 bits: max7319 (8I), max7320 (8O), max7321 (8P), 338 max7322 (4I4O), max7323 (4P4O) 339 340 16 bits: max7324 (8I8O), max7325 (8P8O), 341 max7326 (4I12O), max7327 (4P12O) 342 343 Board setup code must specify the model to use, and the start 344 number for these GPIOs. 345 346config GPIO_MAX732X_IRQ 347 bool "Interrupt controller support for MAX732x" 348 depends on GPIO_MAX732X=y && GENERIC_HARDIRQS 349 help 350 Say yes here to enable the max732x to be used as an interrupt 351 controller. It requires the driver to be built in the kernel. 352 353config GPIO_MC9S08DZ60 354 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions" 355 depends on I2C=y && MACH_MX35_3DS 356 help 357 Select this to enable the MC9S08DZ60 GPIO driver 358 359config GPIO_PCA953X 360 tristate "PCA953x, PCA955x, PCA957x, TCA64xx, and MAX7310 I/O ports" 361 depends on I2C 362 help 363 Say yes here to provide access to several register-oriented 364 SMBus I/O expanders, made mostly by NXP or TI. Compatible 365 models include: 366 367 4 bits: pca9536, pca9537 368 369 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554, 370 pca9556, pca9557, pca9574, tca6408 371 372 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575, 373 tca6416 374 375config GPIO_PCA953X_IRQ 376 bool "Interrupt controller support for PCA953x" 377 depends on GPIO_PCA953X=y 378 help 379 Say yes here to enable the pca953x to be used as an interrupt 380 controller. It requires the driver to be built in the kernel. 381 382config GPIO_PCF857X 383 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders" 384 depends on I2C 385 select IRQ_DOMAIN 386 help 387 Say yes here to provide access to most "quasi-bidirectional" I2C 388 GPIO expanders used for additional digital outputs or inputs. 389 Most of these parts are from NXP, though TI is a second source for 390 some of them. Compatible models include: 391 392 8 bits: pcf8574, pcf8574a, pca8574, pca8574a, 393 pca9670, pca9672, pca9674, pca9674a, 394 max7328, max7329 395 396 16 bits: pcf8575, pcf8575c, pca8575, 397 pca9671, pca9673, pca9675 398 399 Your board setup code will need to declare the expanders in 400 use, and assign numbers to the GPIOs they expose. Those GPIOs 401 can then be used from drivers and other kernel code, just like 402 other GPIOs, but only accessible from task contexts. 403 404 This driver provides an in-kernel interface to those GPIOs using 405 platform-neutral GPIO calls. 406 407config GPIO_RC5T583 408 bool "RICOH RC5T583 GPIO" 409 depends on MFD_RC5T583 410 help 411 Select this option to enable GPIO driver for the Ricoh RC5T583 412 chip family. 413 This driver provides the support for driving/reading the gpio pins 414 of RC5T583 device through standard gpio library. 415 416config GPIO_SX150X 417 bool "Semtech SX150x I2C GPIO expander" 418 depends on I2C=y 419 default n 420 help 421 Say yes here to provide support for Semtech SX150-series I2C 422 GPIO expanders. Compatible models include: 423 424 8 bits: sx1508q 425 16 bits: sx1509q 426 427config GPIO_STMPE 428 bool "STMPE GPIOs" 429 depends on MFD_STMPE 430 help 431 This enables support for the GPIOs found on the STMPE I/O 432 Expanders. 433 434config GPIO_STP_XWAY 435 bool "XWAY STP GPIOs" 436 depends on SOC_XWAY 437 help 438 This enables support for the Serial To Parallel (STP) unit found on 439 XWAY SoC. The STP allows the SoC to drive a shift registers cascade, 440 that can be up to 24 bit. This peripheral is aimed at driving leds. 441 Some of the gpios/leds can be auto updated by the soc with dsl and 442 phy status. 443 444config GPIO_TC3589X 445 bool "TC3589X GPIOs" 446 depends on MFD_TC3589X 447 help 448 This enables support for the GPIOs found on the TC3589X 449 I/O Expander. 450 451config GPIO_TPS65912 452 tristate "TI TPS65912 GPIO" 453 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI) 454 help 455 This driver supports TPS65912 gpio chip 456 457config GPIO_TWL4030 458 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs" 459 depends on TWL4030_CORE 460 help 461 Say yes here to access the GPIO signals of various multi-function 462 power management chips from Texas Instruments. 463 464config GPIO_TWL6040 465 tristate "TWL6040 GPO" 466 depends on TWL6040_CORE 467 help 468 Say yes here to access the GPO signals of twl6040 469 audio chip from Texas Instruments. 470 471config GPIO_WM831X 472 tristate "WM831x GPIOs" 473 depends on MFD_WM831X 474 help 475 Say yes here to access the GPIO signals of WM831x power management 476 chips from Wolfson Microelectronics. 477 478config GPIO_WM8350 479 tristate "WM8350 GPIOs" 480 depends on MFD_WM8350 481 help 482 Say yes here to access the GPIO signals of WM8350 power management 483 chips from Wolfson Microelectronics. 484 485config GPIO_WM8994 486 tristate "WM8994 GPIOs" 487 depends on MFD_WM8994 488 help 489 Say yes here to access the GPIO signals of WM8994 audio hub 490 CODECs from Wolfson Microelectronics. 491 492config GPIO_ADP5520 493 tristate "GPIO Support for ADP5520 PMIC" 494 depends on PMIC_ADP5520 495 help 496 This option enables support for on-chip GPIO found 497 on Analog Devices ADP5520 PMICs. 498 499config GPIO_ADP5588 500 tristate "ADP5588 I2C GPIO expander" 501 depends on I2C 502 help 503 This option enables support for 18 GPIOs found 504 on Analog Devices ADP5588 GPIO Expanders. 505 506config GPIO_ADP5588_IRQ 507 bool "Interrupt controller support for ADP5588" 508 depends on GPIO_ADP5588=y 509 help 510 Say yes here to enable the adp5588 to be used as an interrupt 511 controller. It requires the driver to be built in the kernel. 512 513config GPIO_ADNP 514 tristate "Avionic Design N-bit GPIO expander" 515 depends on I2C && OF_GPIO 516 help 517 This option enables support for N GPIOs found on Avionic Design 518 I2C GPIO expanders. The register space will be extended by powers 519 of two, so the controller will need to accommodate for that. For 520 example: if a controller provides 48 pins, 6 registers will be 521 enough to represent all pins, but the driver will assume a 522 register layout for 64 pins (8 registers). 523 524comment "PCI GPIO expanders:" 525 526config GPIO_CS5535 527 tristate "AMD CS5535/CS5536 GPIO support" 528 depends on PCI && X86 && MFD_CS5535 529 help 530 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that 531 can be used for quite a number of things. The CS5535/6 is found on 532 AMD Geode and Lemote Yeeloong devices. 533 534 If unsure, say N. 535 536config GPIO_BT8XX 537 tristate "BT8XX GPIO abuser" 538 depends on PCI && VIDEO_BT848=n 539 help 540 The BT8xx frame grabber chip has 24 GPIO pins than can be abused 541 as a cheap PCI GPIO card. 542 543 This chip can be found on Miro, Hauppauge and STB TV-cards. 544 545 The card needs to be physically altered for using it as a 546 GPIO card. For more information on how to build a GPIO card 547 from a BT8xx TV card, see the documentation file at 548 Documentation/bt8xxgpio.txt 549 550 If unsure, say N. 551 552config GPIO_AMD8111 553 tristate "AMD 8111 GPIO driver" 554 depends on PCI 555 help 556 The AMD 8111 south bridge contains 32 GPIO pins which can be used. 557 558 Note, that usually system firmware/ACPI handles GPIO pins on their 559 own and users might easily break their systems with uncarefull usage 560 of this driver! 561 562 If unsure, say N 563 564config GPIO_LANGWELL 565 bool "Intel Langwell/Penwell GPIO support" 566 depends on PCI && X86 567 select IRQ_DOMAIN 568 help 569 Say Y here to support Intel Langwell/Penwell GPIO. 570 571config GPIO_PCH 572 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO" 573 depends on PCI && X86 574 select GENERIC_IRQ_CHIP 575 help 576 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff 577 which is an IOH(Input/Output Hub) for x86 embedded processor. 578 This driver can access PCH GPIO device. 579 580 This driver also can be used for LAPIS Semiconductor IOH(Input/ 581 Output Hub), ML7223 and ML7831. 582 ML7223 IOH is for MP(Media Phone) use. 583 ML7831 IOH is for general purpose use. 584 ML7223/ML7831 is companion chip for Intel Atom E6xx series. 585 ML7223/ML7831 is completely compatible for Intel EG20T PCH. 586 587config GPIO_ML_IOH 588 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support" 589 depends on PCI 590 select GENERIC_IRQ_CHIP 591 help 592 ML7213 is companion chip for Intel Atom E6xx series. 593 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output 594 Hub) which is for IVI(In-Vehicle Infotainment) use. 595 This driver can access the IOH's GPIO device. 596 597config GPIO_SODAVILLE 598 bool "Intel Sodaville GPIO support" 599 depends on X86 && PCI && OF 600 select GPIO_GENERIC 601 select GENERIC_IRQ_CHIP 602 help 603 Say Y here to support Intel Sodaville GPIO. 604 605config GPIO_TIMBERDALE 606 bool "Support for timberdale GPIO IP" 607 depends on MFD_TIMBERDALE && HAS_IOMEM 608 ---help--- 609 Add support for the GPIO IP in the timberdale FPGA. 610 611config GPIO_RDC321X 612 tristate "RDC R-321x GPIO support" 613 depends on PCI && GENERIC_HARDIRQS 614 select MFD_CORE 615 select MFD_RDC321X 616 help 617 Support for the RDC R321x SoC GPIOs over southbridge 618 PCI configuration space. 619 620comment "SPI GPIO expanders:" 621 622config GPIO_MAX7301 623 tristate "Maxim MAX7301 GPIO expander" 624 depends on SPI_MASTER 625 select GPIO_MAX730X 626 help 627 GPIO driver for Maxim MAX7301 SPI-based GPIO expander. 628 629config GPIO_MCP23S08 630 tristate "Microchip MCP23xxx I/O expander" 631 depends on SPI_MASTER || I2C 632 help 633 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017 634 I/O expanders. 635 This provides a GPIO interface supporting inputs and outputs. 636 637config GPIO_MC33880 638 tristate "Freescale MC33880 high-side/low-side switch" 639 depends on SPI_MASTER 640 help 641 SPI driver for Freescale MC33880 high-side/low-side switch. 642 This provides GPIO interface supporting inputs and outputs. 643 644config GPIO_74X164 645 tristate "74x164 serial-in/parallel-out 8-bits shift register" 646 depends on SPI_MASTER 647 help 648 Platform driver for 74x164 compatible serial-in/parallel-out 649 8-outputs shift registers. This driver can be used to provide access 650 to more gpio outputs. 651 652comment "AC97 GPIO expanders:" 653 654config GPIO_UCB1400 655 bool "Philips UCB1400 GPIO" 656 depends on UCB1400_CORE 657 help 658 This enables support for the Philips UCB1400 GPIO pins. 659 The UCB1400 is an AC97 audio codec. 660 661comment "MODULbus GPIO expanders:" 662 663config GPIO_JANZ_TTL 664 tristate "Janz VMOD-TTL Digital IO Module" 665 depends on MFD_JANZ_CMODIO 666 help 667 This enables support for the Janz VMOD-TTL Digital IO module. 668 This driver provides support for driving the pins in output 669 mode only. Input mode is not supported. 670 671config GPIO_PALMAS 672 bool "TI PALMAS series PMICs GPIO" 673 depends on MFD_PALMAS 674 help 675 Select this option to enable GPIO driver for the TI PALMAS 676 series chip family. 677 678config GPIO_TPS6586X 679 bool "TPS6586X GPIO" 680 depends on MFD_TPS6586X 681 help 682 Select this option to enable GPIO driver for the TPS6586X 683 chip family. 684 685config GPIO_TPS65910 686 bool "TPS65910 GPIO" 687 depends on MFD_TPS65910 688 help 689 Select this option to enable GPIO driver for the TPS65910 690 chip family. 691 692config GPIO_MSIC 693 bool "Intel MSIC mixed signal gpio support" 694 depends on MFD_INTEL_MSIC 695 help 696 Enable support for GPIO on intel MSIC controllers found in 697 intel MID devices 698 699comment "USB GPIO expanders:" 700 701config GPIO_VIPERBOARD 702 tristate "Viperboard GPIO a & b support" 703 depends on MFD_VIPERBOARD && USB 704 help 705 Say yes here to access the GPIO signals of Nano River 706 Technologies Viperboard. There are two GPIO chips on the 707 board: gpioa and gpiob. 708 See viperboard API specification and Nano 709 River Tech's viperboard.h for detailed meaning 710 of the module parameters. 711 712endif 713