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