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