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