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