linux-stable.git/drivers/i2c, branch linux-2.6.38.y

i2c-parport: Fix adapter list handling

2011-05-09T22:06:37+00:00

commit 56acc7a39ac4ac7638cdc32cd3d0832ebbc834e4 upstream.

Use a standard list with proper locking to handle the list of
adapters. Thankfully it only matters on systems with more than one
parallel port, which are very rare.

Thanks to Lukasz Kapiec for reporting the problem to me.

Signed-off-by: Jean Delvare 
Signed-off-by: Greg Kroah-Hartman

i2c-algo-bit: Call pre/post_xfer for bit_test

2011-04-21T21:32:47+00:00

commit d3b3e15da14ded61c9654db05863b04a2435f4cc upstream.

Apparently some distros set i2c-algo-bit.bit_test to 1 by
default.  In some cases this causes i2c_bit_add_bus
to fail and prevents the i2c bus from being added.  In the
radeon case, we fail to add the ddc i2c buses which prevents
the driver from being able to detect attached monitors.
The i2c bus works fine even if bit_test fails.  This is likely
due to gpio switching that is required and handled in the
pre/post_xfer hooks, so call the pre/post_xfer hooks in the
bit test as well.

Fixes:
https://bugs.freedesktop.org/show_bug.cgi?id=36221

Signed-off-by: Alex Deucher 
Signed-off-by: Jean Delvare 
Signed-off-by: Greg Kroah-Hartman

i2c-eg20t: include slab.h for memory allocations

2011-03-08T23:13:30+00:00

Fixes (with v2.6.38-rc3/parisc/parisc-allmodconfig):
  src/drivers/i2c/busses/i2c-eg20t.c:720: error: implicit declaration of function 'kzalloc'
  src/drivers/i2c/busses/i2c-eg20t.c:790: error: implicit declaration of function 'kfree'

Reported-by: Geert Uytterhoeven 
Signed-off-by: Wolfram Sang 
Cc: Tomoya MORINAGA 
Cc: Ben Dooks 
Signed-off-by: Ben Dooks

i2c-ocores: Fix pointer type mismatch error

2011-03-08T22:57:51+00:00

ocores_i2c_of_probe needs to use a const __be32 type for handing
device tree property values.  This patch fixed the following build
warning:

 CC      drivers/i2c/busses/i2c-ocores.o
  drivers/i2c/busses/i2c-ocores.c: In function 'ocores_i2c_of_probe':
  drivers/i2c/busses/i2c-ocores.c:254: warning: assignment discards qualifiers from pointer target type
  drivers/i2c/busses/i2c-ocores.c:261: warning: assignment discards qualifiers from pointer target type

Signed-off-by: Grant Likely 
Cc: Peter Korsgaard 
Cc: Ben Dooks 
Cc: linux-i2c@vger.kernel.org
Signed-off-by: Ben Dooks

i2c-omap: Program I2C_WE on OMAP4 to enable i2c wakeup

2011-03-07T09:53:38+00:00

For the I2C module to be wakeup capable, programming I2C_WE register (which
was skipped for OMAP4430) is needed even on OMAP4.

This fixes i2c controller timeouts which were seen recently with the static
dependency being cleared between MPU and L4PER clockdomains.

Signed-off-by: Rajendra Nayak 
[ben-linux@fluff.org: re-flowed description]
Signed-off-by: Ben Dooks

i2c-omap: fixup commit cb527ede1bf6ff2008a025606f25344b8ed7b4ac whitespace

2011-02-23T00:43:55+00:00

Fixup the whitespace error noticed in cb527ede1bf6ff2008a025606f25344b8ed7b4ac

Signed-off-by: Ben Dooks

i2c-omap: Double clear of ARDY status in IRQ handler

2011-02-23T00:42:36+00:00

This errata occurs when the ARDY interrupt generation is enabled.
At the begining of every new transaction the ARDY interrupt is cleared.

On continuous i2c transactions where after clearing the ARDY bit from
I2C_STAT register (clearing the interrupt), the IRQ line is reasserted and the
I2C_STAT[ARDY] bit set again on 1. In fact, the ARDY status bit is not cleared
at the write access to I2C_STAT[ARDY] and only the IRQ line is deasserted and
then reasserted. This is not captured in the usual errata documents.

The workaround is to have a double clear of ARDY status in irq handler.

Signed-off-by: Richard woodruff 
Signed-off-by: Keerthy 
Signed-off-by: Ben Dooks

i2c-omap: fix build for !CONFIG_SUSPEND

2011-02-23T00:39:45+00:00

fix the build break when !CONFIG_SUSPEND

drivers/i2c/busses/i2c-omap.c:1173: error: lvalue required as unary '&' operand
make[3]: *** [drivers/i2c/busses/i2c-omap.o] Error 1
make[2]: *** [drivers/i2c/busses] Error 2
make[1]: *** [drivers/i2c] Error 2
make: *** [drivers] Error 2

Signed-off-by: Balaji T K 
Signed-off-by: Ben Dooks

i2c-omap: fix static suspend vs. runtime suspend

2011-02-22T23:53:44+00:00

When runtime PM is enabled, each OMAP i2c device is suspended after
each i2c xfer.  However, there are two cases when the static suspend
methods must be used to ensure the devices are suspended:

1) runtime PM is disabled, either at compile time or dynamically
    via /sys/devices/.../power/control.
2) an i2c client driver uses i2c during it's suspend callback, thus
   leaving the i2c driver active (NOTE: runtime suspend transitions are
   disabled during system suspend, so i2c activity during system
   suspend will runtime resume the device, but not runtime (re)suspend it.)

Since the actual work to suspend the device is handled by the
subsytem, call the bus methods to take care of it.

NOTE: This takes care of a known suspend problem on OMAP3 where the
TWL RTC driver does i2c xfers during its suspend path leaving the i2c
driver in an active state (since runtime suspend transistions are
disabled.)

Signed-off-by: Kevin Hilman 
Signed-off-by: Ben Dooks

i2c-stu300: make sure adapter-name is terminated

2011-02-22T23:53:44+00:00

Use strlcpy instead of strncpy.

Signed-off-by: Wolfram Sang 
Cc: Linus Walleij 
Cc: Ben Dooks 
Signed-off-by: Ben Dooks