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_XILINX 231 bool "Xilinx GPIO support" 232 depends on PPC_OF || MICROBLAZE 233 help 234 Say yes here to support the Xilinx FPGA GPIO device 235 236config GPIO_VR41XX 237 tristate "NEC VR4100 series General-purpose I/O Uint support" 238 depends on CPU_VR41XX 239 help 240 Say yes here to support the NEC VR4100 series General-purpose I/O Uint 241 242config GPIO_SCH 243 tristate "Intel SCH/TunnelCreek/Centerton GPIO" 244 depends on PCI && X86 245 select MFD_CORE 246 select LPC_SCH 247 help 248 Say yes here to support GPIO interface on Intel Poulsbo SCH, 249 Intel Tunnel Creek processor or Intel Centerton processor. 250 The Intel SCH contains a total of 14 GPIO pins. Ten GPIOs are 251 powered by the core power rail and are turned off during sleep 252 modes (S3 and higher). The remaining four GPIOs are powered by 253 the Intel SCH suspend power supply. These GPIOs remain 254 active during S3. The suspend powered GPIOs can be used to wake the 255 system from the Suspend-to-RAM state. 256 The Intel Tunnel Creek processor has 5 GPIOs powered by the 257 core power rail and 9 from suspend power supply. 258 The Intel Centerton processor has a total of 30 GPIO pins. 259 Twenty-one are powered by the core power rail and 9 from the 260 suspend power supply. 261 262config GPIO_ICH 263 tristate "Intel ICH GPIO" 264 depends on PCI && X86 265 select MFD_CORE 266 select LPC_ICH 267 help 268 Say yes here to support the GPIO functionality of a number of Intel 269 ICH-based chipsets. Currently supported devices: ICH6, ICH7, ICH8 270 ICH9, ICH10, Series 5/3400 (eg Ibex Peak), Series 6/C200 (eg 271 Cougar Point), NM10 (Tiger Point), and 3100 (Whitmore Lake). 272 273 If unsure, say N. 274 275config GPIO_VX855 276 tristate "VIA VX855/VX875 GPIO" 277 depends on PCI && GENERIC_HARDIRQS 278 select MFD_CORE 279 select MFD_VX855 280 help 281 Support access to the VX855/VX875 GPIO lines through the gpio library. 282 283 This driver provides common support for accessing the device, 284 additional drivers must be enabled in order to use the 285 functionality of the device. 286 287config GPIO_GE_FPGA 288 bool "GE FPGA based GPIO" 289 depends on GE_FPGA 290 help 291 Support for common GPIO functionality provided on some GE Single Board 292 Computers. 293 294 This driver provides basic support (configure as input or output, read 295 and write pin state) for GPIO implemented in a number of GE single 296 board computers. 297 298config GPIO_LYNXPOINT 299 bool "Intel Lynxpoint GPIO support" 300 depends on ACPI 301 select IRQ_DOMAIN 302 help 303 driver for GPIO functionality on Intel Lynxpoint PCH chipset 304 Requires ACPI device enumeration code to set up a platform device. 305 306comment "I2C GPIO expanders:" 307 308config GPIO_ARIZONA 309 tristate "Wolfson Microelectronics Arizona class devices" 310 depends on MFD_ARIZONA 311 help 312 Support for GPIOs on Wolfson Arizona class devices. 313 314config GPIO_MAX7300 315 tristate "Maxim MAX7300 GPIO expander" 316 depends on I2C 317 select GPIO_MAX730X 318 help 319 GPIO driver for Maxim MAX7301 I2C-based GPIO expander. 320 321config GPIO_MAX732X 322 tristate "MAX7319, MAX7320-7327 I2C Port Expanders" 323 depends on I2C 324 help 325 Say yes here to support the MAX7319, MAX7320-7327 series of I2C 326 Port Expanders. Each IO port on these chips has a fixed role of 327 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain 328 Input and Output (designed by 'P'). The combinations are listed 329 below: 330 331 8 bits: max7319 (8I), max7320 (8O), max7321 (8P), 332 max7322 (4I4O), max7323 (4P4O) 333 334 16 bits: max7324 (8I8O), max7325 (8P8O), 335 max7326 (4I12O), max7327 (4P12O) 336 337 Board setup code must specify the model to use, and the start 338 number for these GPIOs. 339 340config GPIO_MAX732X_IRQ 341 bool "Interrupt controller support for MAX732x" 342 depends on GPIO_MAX732X=y && GENERIC_HARDIRQS 343 help 344 Say yes here to enable the max732x to be used as an interrupt 345 controller. It requires the driver to be built in the kernel. 346 347config GPIO_MC9S08DZ60 348 bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions" 349 depends on I2C=y && MACH_MX35_3DS 350 help 351 Select this to enable the MC9S08DZ60 GPIO driver 352 353config GPIO_PCA953X 354 tristate "PCA953x, PCA955x, PCA957x, TCA64xx, and MAX7310 I/O ports" 355 depends on I2C 356 help 357 Say yes here to provide access to several register-oriented 358 SMBus I/O expanders, made mostly by NXP or TI. Compatible 359 models include: 360 361 4 bits: pca9536, pca9537 362 363 8 bits: max7310, max7315, pca6107, pca9534, pca9538, pca9554, 364 pca9556, pca9557, pca9574, tca6408 365 366 16 bits: max7312, max7313, pca9535, pca9539, pca9555, pca9575, 367 tca6416 368 369config GPIO_PCA953X_IRQ 370 bool "Interrupt controller support for PCA953x" 371 depends on GPIO_PCA953X=y 372 help 373 Say yes here to enable the pca953x to be used as an interrupt 374 controller. It requires the driver to be built in the kernel. 375 376config GPIO_PCF857X 377 tristate "PCF857x, PCA{85,96}7x, and MAX732[89] I2C GPIO expanders" 378 depends on I2C 379 select IRQ_DOMAIN 380 help 381 Say yes here to provide access to most "quasi-bidirectional" I2C 382 GPIO expanders used for additional digital outputs or inputs. 383 Most of these parts are from NXP, though TI is a second source for 384 some of them. Compatible models include: 385 386 8 bits: pcf8574, pcf8574a, pca8574, pca8574a, 387 pca9670, pca9672, pca9674, pca9674a, 388 max7328, max7329 389 390 16 bits: pcf8575, pcf8575c, pca8575, 391 pca9671, pca9673, pca9675 392 393 Your board setup code will need to declare the expanders in 394 use, and assign numbers to the GPIOs they expose. Those GPIOs 395 can then be used from drivers and other kernel code, just like 396 other GPIOs, but only accessible from task contexts. 397 398 This driver provides an in-kernel interface to those GPIOs using 399 platform-neutral GPIO calls. 400 401config GPIO_RC5T583 402 bool "RICOH RC5T583 GPIO" 403 depends on MFD_RC5T583 404 help 405 Select this option to enable GPIO driver for the Ricoh RC5T583 406 chip family. 407 This driver provides the support for driving/reading the gpio pins 408 of RC5T583 device through standard gpio library. 409 410config GPIO_SX150X 411 bool "Semtech SX150x I2C GPIO expander" 412 depends on I2C=y 413 default n 414 help 415 Say yes here to provide support for Semtech SX150-series I2C 416 GPIO expanders. Compatible models include: 417 418 8 bits: sx1508q 419 16 bits: sx1509q 420 421config GPIO_STMPE 422 bool "STMPE GPIOs" 423 depends on MFD_STMPE 424 help 425 This enables support for the GPIOs found on the STMPE I/O 426 Expanders. 427 428config GPIO_STP_XWAY 429 bool "XWAY STP GPIOs" 430 depends on SOC_XWAY 431 help 432 This enables support for the Serial To Parallel (STP) unit found on 433 XWAY SoC. The STP allows the SoC to drive a shift registers cascade, 434 that can be up to 24 bit. This peripheral is aimed at driving leds. 435 Some of the gpios/leds can be auto updated by the soc with dsl and 436 phy status. 437 438config GPIO_TC3589X 439 bool "TC3589X GPIOs" 440 depends on MFD_TC3589X 441 help 442 This enables support for the GPIOs found on the TC3589X 443 I/O Expander. 444 445config GPIO_TPS65912 446 tristate "TI TPS65912 GPIO" 447 depends on (MFD_TPS65912_I2C || MFD_TPS65912_SPI) 448 help 449 This driver supports TPS65912 gpio chip 450 451config GPIO_TWL4030 452 tristate "TWL4030, TWL5030, and TPS659x0 GPIOs" 453 depends on TWL4030_CORE 454 help 455 Say yes here to access the GPIO signals of various multi-function 456 power management chips from Texas Instruments. 457 458config GPIO_TWL6040 459 tristate "TWL6040 GPO" 460 depends on TWL6040_CORE 461 help 462 Say yes here to access the GPO signals of twl6040 463 audio chip from Texas Instruments. 464 465config GPIO_WM831X 466 tristate "WM831x GPIOs" 467 depends on MFD_WM831X 468 help 469 Say yes here to access the GPIO signals of WM831x power management 470 chips from Wolfson Microelectronics. 471 472config GPIO_WM8350 473 tristate "WM8350 GPIOs" 474 depends on MFD_WM8350 475 help 476 Say yes here to access the GPIO signals of WM8350 power management 477 chips from Wolfson Microelectronics. 478 479config GPIO_WM8994 480 tristate "WM8994 GPIOs" 481 depends on MFD_WM8994 482 help 483 Say yes here to access the GPIO signals of WM8994 audio hub 484 CODECs from Wolfson Microelectronics. 485 486config GPIO_ADP5520 487 tristate "GPIO Support for ADP5520 PMIC" 488 depends on PMIC_ADP5520 489 help 490 This option enables support for on-chip GPIO found 491 on Analog Devices ADP5520 PMICs. 492 493config GPIO_ADP5588 494 tristate "ADP5588 I2C GPIO expander" 495 depends on I2C 496 help 497 This option enables support for 18 GPIOs found 498 on Analog Devices ADP5588 GPIO Expanders. 499 500config GPIO_ADP5588_IRQ 501 bool "Interrupt controller support for ADP5588" 502 depends on GPIO_ADP5588=y 503 help 504 Say yes here to enable the adp5588 to be used as an interrupt 505 controller. It requires the driver to be built in the kernel. 506 507config GPIO_ADNP 508 tristate "Avionic Design N-bit GPIO expander" 509 depends on I2C && OF_GPIO 510 help 511 This option enables support for N GPIOs found on Avionic Design 512 I2C GPIO expanders. The register space will be extended by powers 513 of two, so the controller will need to accommodate for that. For 514 example: if a controller provides 48 pins, 6 registers will be 515 enough to represent all pins, but the driver will assume a 516 register layout for 64 pins (8 registers). 517 518comment "PCI GPIO expanders:" 519 520config GPIO_CS5535 521 tristate "AMD CS5535/CS5536 GPIO support" 522 depends on PCI && X86 && MFD_CS5535 523 help 524 The AMD CS5535 and CS5536 southbridges support 28 GPIO pins that 525 can be used for quite a number of things. The CS5535/6 is found on 526 AMD Geode and Lemote Yeeloong devices. 527 528 If unsure, say N. 529 530config GPIO_BT8XX 531 tristate "BT8XX GPIO abuser" 532 depends on PCI && VIDEO_BT848=n 533 help 534 The BT8xx frame grabber chip has 24 GPIO pins than can be abused 535 as a cheap PCI GPIO card. 536 537 This chip can be found on Miro, Hauppauge and STB TV-cards. 538 539 The card needs to be physically altered for using it as a 540 GPIO card. For more information on how to build a GPIO card 541 from a BT8xx TV card, see the documentation file at 542 Documentation/bt8xxgpio.txt 543 544 If unsure, say N. 545 546config GPIO_AMD8111 547 tristate "AMD 8111 GPIO driver" 548 depends on PCI 549 help 550 The AMD 8111 south bridge contains 32 GPIO pins which can be used. 551 552 Note, that usually system firmware/ACPI handles GPIO pins on their 553 own and users might easily break their systems with uncarefull usage 554 of this driver! 555 556 If unsure, say N 557 558config GPIO_LANGWELL 559 bool "Intel Langwell/Penwell GPIO support" 560 depends on PCI && X86 561 select IRQ_DOMAIN 562 help 563 Say Y here to support Intel Langwell/Penwell GPIO. 564 565config GPIO_PCH 566 tristate "Intel EG20T PCH/LAPIS Semiconductor IOH(ML7223/ML7831) GPIO" 567 depends on PCI && X86 568 select GENERIC_IRQ_CHIP 569 help 570 This driver is for PCH(Platform controller Hub) GPIO of Intel Topcliff 571 which is an IOH(Input/Output Hub) for x86 embedded processor. 572 This driver can access PCH GPIO device. 573 574 This driver also can be used for LAPIS Semiconductor IOH(Input/ 575 Output Hub), ML7223 and ML7831. 576 ML7223 IOH is for MP(Media Phone) use. 577 ML7831 IOH is for general purpose use. 578 ML7223/ML7831 is companion chip for Intel Atom E6xx series. 579 ML7223/ML7831 is completely compatible for Intel EG20T PCH. 580 581config GPIO_ML_IOH 582 tristate "OKI SEMICONDUCTOR ML7213 IOH GPIO support" 583 depends on PCI 584 select GENERIC_IRQ_CHIP 585 help 586 ML7213 is companion chip for Intel Atom E6xx series. 587 This driver can be used for OKI SEMICONDUCTOR ML7213 IOH(Input/Output 588 Hub) which is for IVI(In-Vehicle Infotainment) use. 589 This driver can access the IOH's GPIO device. 590 591config GPIO_SODAVILLE 592 bool "Intel Sodaville GPIO support" 593 depends on X86 && PCI && OF 594 select GPIO_GENERIC 595 select GENERIC_IRQ_CHIP 596 help 597 Say Y here to support Intel Sodaville GPIO. 598 599config GPIO_TIMBERDALE 600 bool "Support for timberdale GPIO IP" 601 depends on MFD_TIMBERDALE && HAS_IOMEM 602 ---help--- 603 Add support for the GPIO IP in the timberdale FPGA. 604 605config GPIO_RDC321X 606 tristate "RDC R-321x GPIO support" 607 depends on PCI && GENERIC_HARDIRQS 608 select MFD_CORE 609 select MFD_RDC321X 610 help 611 Support for the RDC R321x SoC GPIOs over southbridge 612 PCI configuration space. 613 614comment "SPI GPIO expanders:" 615 616config GPIO_MAX7301 617 tristate "Maxim MAX7301 GPIO expander" 618 depends on SPI_MASTER 619 select GPIO_MAX730X 620 help 621 GPIO driver for Maxim MAX7301 SPI-based GPIO expander. 622 623config GPIO_MCP23S08 624 tristate "Microchip MCP23xxx I/O expander" 625 depends on SPI_MASTER || I2C 626 help 627 SPI/I2C driver for Microchip MCP23S08/MCP23S17/MCP23008/MCP23017 628 I/O expanders. 629 This provides a GPIO interface supporting inputs and outputs. 630 631config GPIO_MC33880 632 tristate "Freescale MC33880 high-side/low-side switch" 633 depends on SPI_MASTER 634 help 635 SPI driver for Freescale MC33880 high-side/low-side switch. 636 This provides GPIO interface supporting inputs and outputs. 637 638config GPIO_74X164 639 tristate "74x164 serial-in/parallel-out 8-bits shift register" 640 depends on SPI_MASTER 641 help 642 Platform driver for 74x164 compatible serial-in/parallel-out 643 8-outputs shift registers. This driver can be used to provide access 644 to more gpio outputs. 645 646comment "AC97 GPIO expanders:" 647 648config GPIO_UCB1400 649 bool "Philips UCB1400 GPIO" 650 depends on UCB1400_CORE 651 help 652 This enables support for the Philips UCB1400 GPIO pins. 653 The UCB1400 is an AC97 audio codec. 654 655comment "MODULbus GPIO expanders:" 656 657config GPIO_JANZ_TTL 658 tristate "Janz VMOD-TTL Digital IO Module" 659 depends on MFD_JANZ_CMODIO 660 help 661 This enables support for the Janz VMOD-TTL Digital IO module. 662 This driver provides support for driving the pins in output 663 mode only. Input mode is not supported. 664 665config GPIO_PALMAS 666 bool "TI PALMAS series PMICs GPIO" 667 depends on MFD_PALMAS 668 help 669 Select this option to enable GPIO driver for the TI PALMAS 670 series chip family. 671 672config GPIO_TPS6586X 673 bool "TPS6586X GPIO" 674 depends on MFD_TPS6586X 675 help 676 Select this option to enable GPIO driver for the TPS6586X 677 chip family. 678 679config GPIO_TPS65910 680 bool "TPS65910 GPIO" 681 depends on MFD_TPS65910 682 help 683 Select this option to enable GPIO driver for the TPS65910 684 chip family. 685 686config GPIO_MSIC 687 bool "Intel MSIC mixed signal gpio support" 688 depends on MFD_INTEL_MSIC 689 help 690 Enable support for GPIO on intel MSIC controllers found in 691 intel MID devices 692 693comment "USB GPIO expanders:" 694 695config GPIO_VIPERBOARD 696 tristate "Viperboard GPIO a & b support" 697 depends on MFD_VIPERBOARD && USB 698 help 699 Say yes here to access the GPIO signals of Nano River 700 Technologies Viperboard. There are two GPIO chips on the 701 board: gpioa and gpiob. 702 See viperboard API specification and Nano 703 River Tech's viperboard.h for detailed meaning 704 of the module parameters. 705 706endif 707