linux-toradex.git/drivers/gpio, branch tegra-T30.ER5

cs5535-gpio: handle GPIO regs where higher (clear) bits are set

2011-01-07T21:58:40+00:00

commit 44658a11f312fb9217674cb90b1a11cbe17fd18d upstream.

The default for non-READ_BACK GPIO regs is to have the clear bits set;
this means that our original errata fix was too simplistic.  This
changes it to the following behavior:

 - when setting GPIOs, ignore the higher order bits (they're for
   clearing, we don't need to care about them).

 - when clearing GPIOs, keep all the bits, but unset (via XOR) the
   lower order bit that negates the clear bit that we care about.  That
   is, if we're clearing GPIO 26 (val = 0x04000000), we first XOR what's
   currently in the register with 0x0400 (GPIO 26's SET bit), and then
   OR that with the GPIO 26's CLEAR bit.

Tested-by: Daniel Drake 
Signed-off-by: Andres Salomon 
Signed-off-by: Linus Torvalds 
Signed-off-by: Greg Kroah-Hartman

cs5535-gpio: don't apply errata #36 to edge detect GPIOs

2011-01-07T21:58:39+00:00

commit 001851659354cce436b749a793f3512a53394d80 upstream.

The edge detect status GPIOs function differently from the other atomic
model CS5536 GPIO registers; writing 1 to the high bits clears the GPIO,
but writing 1 to the lower bits also clears the bit.

This means that read-modify-write doesn't actually work for it, so don't
apply the errata here.  If a negative edge status gets lost after
resume..  well, we tried our best!

Tested-by: Daniel Drake 
Signed-off-by: Andres Salomon 
Signed-off-by: Linus Torvalds 
Signed-off-by: Greg Kroah-Hartman

gpio: Fix null pointer dereference while accessing rdc321x platform_data

2011-01-07T21:58:38+00:00

commit fa6469cb5b2d16703464c344b943e2c025cb7858 upstream.

rdc321x-gpio currently fetches its driver specific data by using the
platform_device->platform_data pointer, this is wrong because the mfd
device which registers our platform_device has been added using
mfd_add_device() which sets the platform_device->driver_data pointer
instead.

Signed-off-by: Florian Fainelli 
Signed-off-by: Samuel Ortiz 
Signed-off-by: Greg Kroah-Hartman

cs5535-gpio: apply CS5536 errata workaround for GPIOs

2010-12-09T21:33:14+00:00

commit 853ff88324a248a9f5da6e110850223db353ec07 upstream.

The AMD Geode CS5536 Companion Device Silicon Revision B1 Specification
Update mentions the follow as issue #36:

 "Atomic write transactions to the atomic GPIO High Bank Feature Bit
  registers should only affect the bits selected [...]"

 "after Suspend, an atomic write transaction [...] will clear all
  non-selected bits of the accessed register."

In other words, writing to the high bank for a single GPIO bit will
clear every other GPIO bit (but only sometimes after a suspend).

The workaround described is obvious and simple; do a read-modify-write.
This patch does that, and documents why we're doing it.

Signed-off-by: Andres Salomon 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds 
Signed-off-by: Greg Kroah-Hartman

gpio: sx150x: correct and refine reset-on-probe behavior

2010-09-10T01:57:24+00:00

Replace the arbitrary software-reset call from the device-probe
method, because:

- It is defective.  To work correctly, it should be two byte writes,
  not a single word write.  As it stands, it does nothing.

- Some devices with sx150x expanders installed have their NRESET pins
  ganged on the same line, so resetting one causes the others to reset -
  not a nice thing to do arbitrarily!

- The probe, usually taking place at boot, implies a recent hard-reset,
  so a software reset at this point is just a waste of energy anyway.

Therefore, make it optional, defaulting to off, as this will match the
common case of probing at powerup and also matches the current broken
no-op behavior.

Signed-off-by: Gregory Bean 
Reviewed-by: Jean Delvare 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

gpiolib: Implement set_debounce for WM831x GPIOs

2010-08-12T09:27:57+00:00

The debounce times are approximate, they can be selected using the two
input functions.

Signed-off-by: Mark Brown 
Signed-off-by: Samuel Ortiz

gpio: Add STMPE GPIO driver

2010-08-12T09:27:55+00:00

Add support for the GPIOs on STMPE I/O Expanders.

[l.fu@pengutronix.de: fix set direction input]
[l.fu@pengutronix.de: set GPIO alternate function while requesting]
Acked-by: Luotao Fu 
Acked-by: Linus Walleij 
Signed-off-by: Rabin Vincent 
Signed-off-by: Samuel Ortiz

gpio: sx150x: add Semtech I2C sx150x gpio expander driver

2010-08-11T15:59:09+00:00

Add support for Semtech SX150-series I2C GPIO expanders.  Compatible
models include:

8 bits:  sx1508q
16 bits: sx1509q

Signed-off-by: Gregory Bean 
Cc: David Brownell 
Cc: Jean Delvare 
Cc: Trilok Soni 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

gpiolib: allow nested threaded irqs for poll(2)

2010-08-11T15:59:09+00:00

The pca953x driver requires the use of threaded irqs as its irq
demultiplexer can sleep.  Our irq handler can be called from any context,
so use request_any_context_irq to allow threaded irqs as well.

Signed-off-by: Daniel Gl?ckner 
Reported-by: Ian Jeffray 
Cc: David Brownell 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

gpiolib: get rid of struct poll_desc and worklet

2010-08-11T15:59:08+00:00

As sysfs_notify_dirent has been made irq safe, there is no reason to not
call it directly from irq.  With the work_struct removed, the remaining
element in poll_desc is a sysfs_dirent pointer which may not be NULL.  We
can therefore store it directly in the idr and pass it as context to the
irq handler.

Most part of the patch deals with renaming defines and variables to
reflect their new use without functional change.

I also took the opportunity to initialize the idr statically.

Signed-off-by: Daniel Gl?ckner 
Cc: David Brownell 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds