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