linux-toradex.git/drivers/gpio, branch v2.6.35-rc2

gpio: Fix inverted rdc321x gpio data out registers

2010-05-27T23:37:59+00:00

rdc_gpio_set_value_impl has the gpio data registers 1 and 2 inverted, fix this.

Signed-off-by: Bernhard Loos 
Signed-off-by: Florian Fainelli 
Signed-off-by: Samuel Ortiz

mfd: Change rdc321x resources flags to IORESOURCE_IO

2010-05-27T23:37:52+00:00

The rdc321x southbridge PCI device has no MEM PCI resources that we could
pass to mfd_add_devices. Since 33254dd5, mfd_add_device checks for the
mem_base argument that we set to NULL. Changing the resources passed to
our MFD cells from IORESOURCE_MEM to IORESOURCE_IO fixes that. Since we use
those resources as offsets to the PCI configuration space base address of
the southbridge device this is also more adequate.

Signed-off-by: Florian Fainelli 
Signed-off-by: Samuel Ortiz

gpio: rdc321x needs to select MFD_CORE

2010-05-27T23:37:48+00:00

Fix rdc321x-southbridge build:  GPIO_RDC321X needs to select
MFD_CORE so that the core is built at the same (or higher)
tristate level.

rdc321x-southbridge.c:(.devinit.text+0x6103): undefined reference to `mfd_add_devices'
rdc321x-southbridge.c:(.devexit.text+0xe5f): undefined reference to `mfd_remove_devices'

Signed-off-by: Randy Dunlap 
Cc:	Florian Fainelli 
Signed-off-by: Samuel Ortiz

gpio: Add TC35892 GPIO driver

2010-05-27T23:37:43+00:00

Add a GPIO driver to support the GPIOs on the TC35892 I/O Expander.

Acked-by: Linus Walleij 
Signed-off-by: Rabin Vincent 
Signed-off-by: Samuel Ortiz

gpio: Update gfp/slab.h includes for rdc321x

2010-05-27T23:37:36+00:00

Implicit slab.h inclusion via percpu.h is about to go away.  Make sure
gfp.h or slab.h is included as necessary.

Signed-off-by: Samuel Ortiz 
Signed-off-by: Tejun Heo

gpio: Add support for Janz VMOD-TTL Digital IO module

2010-05-27T23:37:33+00:00

The Janz VMOD-TTL is a MODULbus daughterboard which fits onto any MODULbus
carrier board. It essentially consists of some various logic and a Zilog
Z8536 CIO Counter/Timer and Parallel IO Unit.

The board must be physically configured with jumpers to enable a user to
drive output signals. I am only interested in outputs, so I have made this
driver as simple as possible. It only supports a very minimal subset of the
features provided by the Z8536 chip.

Signed-off-by: Ira W. Snyder 
Signed-off-by: Samuel Ortiz

gpio: Add support for RDC321x GPIO controller

2010-05-27T23:37:29+00:00

This patch adds a new GPIO driver for the RDC321x SoC GPIO controller.

Signed-off-by: Florian Fainelli 
Signed-off-by: Samuel Ortiz

drivers/gpio/it8761e_gpio: check return value of gpiochip_remove()

2010-05-27T16:12:42+00:00

This eliminates the following build warning:

drivers/gpio/it8761e_gpio.c: In function `it8761e_gpio_exit':
drivers/gpio/it8761e_gpio.c:220: warning: ignoring return value of `gpiochip_remove', declared with attribute warn_unused_result

Signed-off-by: Daniel Mack 
Cc: Denis Turischev 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

gpio: add Penwell gpio support

2010-05-27T16:12:42+00:00

Intel Penwell chip has two 96 pins GPIO blocks, which are very similiar as
Intel Langwell chip GPIO block, except for pin number difference. This
patch expends the original Langwell GPIO driver to support Penwell's.

Signed-off-by: Alek Du 
Cc: David Brownell 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

gpiolib: introduce set_debounce method

2010-05-27T16:12:42+00:00

A few architectures, like OMAP, allow you to set a debouncing time for the
gpio before generating the IRQ.  Teach gpiolib about that.

Mark said:
: This would be generally useful for embedded systems, especially where
: the interrupt concerned is a wake source.  It allows drivers to avoid
: spurious interrupts from noisy sources so if the hardware supports it
: the driver can avoid having to explicitly wait for the signal to become
: stable and software has to cope with fewer events.  We've lived without
: it for quite some time, though.

David said:
: I looked at adding debounce support to the generic GPIO calls (and thus
: gpiolib) some time back, but decided against it.  I forget why at this
: time (check list archives) but it wasn't because of lack of utility in
: certain contexts.
:
: One thing to watch out for is just how variable the hardware capabilities
: are.  Atmel GPIOs have something like a fixed number of 32K clock cycles
: for debounce, twl4030 had something odd, OMAPs were more like the Atmel
: chips but with a different clock.  In some cases debouncing had to be
: ganged, not per-GPIO.  And so forth.

Signed-off-by: Felipe Balbi 
Cc: Tony Lindgren 
Cc: David Brownell 
Reviewed-by: Mark Brown 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds