linux-toradex.git/drivers/i2c, branch v2.6.32.15

i2c: Fix probing of FSC hardware monitoring chips

2010-05-12T21:57:04+00:00

commit b1d4b390ea4bb480e65974ce522a04022608a8df upstream.

Some FSC hardware monitoring chips (Syleus at least) doesn't like
quick writes we typically use to probe for I2C chips. Use a regular
byte read instead for the address they live at (0x73). These are the
only known chips living at this address on PC systems.

For clarity, this fix should not be needed for kernels 2.6.30 and
later, as we started instantiating the hwmon devices explicitly based
on DMI data. Still, this fix is valuable in the following two cases:
* Support for recent FSC chips on older kernels. The DMI-based device
  instantiation is more difficult to backport than the device support
  itself.
* Case where the DMI-based device instantiation fails, whatever the
  reason. We fall back to probing in that case, so it should work.

This fixes kernel bug #15634:
https://bugzilla.kernel.org/show_bug.cgi?id=15634

Signed-off-by: Jean Delvare 
Acked-by: Hans de Goede 
Signed-off-by: Greg Kroah-Hartman

i2c-i801: Add Intel Cougar Point device IDs

2010-04-26T14:41:32+00:00

commit 393764340beb595c1ad7dd2d2243c2b6551aaa71 upstream.

Add the Intel Cougar Point (PCH) SMBus controller device IDs.

Signed-off-by: Seth Heasley 
Signed-off-by: Jean Delvare 
Cc: maximilian attems 
Signed-off-by: Greg Kroah-Hartman

i2c-i801: Don't use the block buffer for I2C block writes

2010-04-01T22:58:07+00:00

commit c074c39d62306efa5ba7c69c1a1531bc7333d252 upstream.

Experience has shown that the block buffer can only be used for SMBus
(not I2C) block transactions, even though the datasheet doesn't
mention this limitation.

Reported-by: Felix Rubinstein 
Signed-off-by: Jean Delvare 
Cc: Oleg Ryjkov 
Signed-off-by: Greg Kroah-Hartman

i2c-tiny-usb: Fix on big-endian systems

2010-02-23T15:37:48+00:00

commit 1c010ff8912cbc08d80e865aab9c32b6b00c527d upstream.

The functionality bit vector is always returned as a little-endian
32-bit number by the device, so it must be byte-swapped to the host
endianness.

On the other hand, the delay value is handled by the USB stack, so no
byte swapping is needed on our side.

This fixes bug #15105:
http://bugzilla.kernel.org/show_bug.cgi?id=15105

Reported-by: Jens Richter 
Signed-off-by: Jean Delvare 
Tested-by: Jens Richter 
Cc: Till Harbaum 
Signed-off-by: Greg Kroah-Hartman

i2c/pca: Don't use *_interruptible

2010-01-22T23:18:35+00:00

commit 22f8b2695eda496026623020811cae34590ee3d7 upstream.

Unexpected signals can disturb the bus-handling and lock it up. Don't use
interruptible in 'wait_event_*' and 'wake_*' as in commits
dc1972d02747d2170fb1d78d114801f5ecb27506 (for cpm),
1ab082d7cbd0f34e39a5396cc6340c00bc5d66ef (for mpc),
b7af349b175af45f9d87b3bf3f0a221e1831ed39 (for omap).

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

i2c: Do not use device name after device_unregister

2010-01-22T23:18:34+00:00

commit c556752109794a5ff199b80a1673336b4df8433a upstream.

dev_dbg outputs dev_name, which is released with device_unregister. This bug
resulted in output like this:

i2c Xy2�0: adapter [SMBus I801 adapter at 1880] unregistered

The right output would be:
i2c i2c-0: adapter [SMBus I801 adapter at 1880] unregistered

Signed-off-by: Thadeu Lima de Souza Cascardo 
Signed-off-by: Jean Delvare 
Signed-off-by: Greg Kroah-Hartman

Merge branch 'i2c-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging

2009-11-30T22:50:44+00:00

* 'i2c-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging:
  at24: Use timeout also for read
  i2c: Fix userspace_device list corruption
  MAINTAINERS: Add missing i2c files
  i2c/tsl2550: Fix lux value in extended mode

i2c: Fix userspace_device list corruption

2009-11-26T08:22:33+00:00

Fix userspace_device list corruption. The corruption was caused by
clients not being removed when adapters with such clients were
themselves removed. Something like the following would trigger it
(assuming i2c-stub gets adapter number 3):

# modprobe i2c-stub chip_addr=0x50
# echo 24c08 0x50 > /sys/bus/i2c/devices/i2c-3/new_device 
# rmmod i2c-stub
# modprobe i2c-stub chip_addr=0x50
# echo 24c08 0x50 > /sys/bus/i2c/devices/i2c-3/new_device 

For the records, the stack trace in the kernel logs look like this:

kernel: WARNING: at lib/list_debug.c:30 __list_add+0x8b/0x90()
kernel: Hardware name: (...)
kernel: list_add corruption. prev->next should be next (c137fc84), but was (null). (prev=f57111b8).
kernel: Modules linked in: (...)
kernel: Pid: 4669, comm: bash Not tainted 2.6.32-rc8 #259
kernel: Call Trace:
kernel:  [] ? __list_add+0x8b/0x90
kernel:  [] ? __list_add+0x8b/0x90
kernel:  [] warn_slowpath_common+0x6c/0xc0
kernel:  [] ? __list_add+0x8b/0x90
kernel:  [] warn_slowpath_fmt+0x26/0x30
kernel:  [] __list_add+0x8b/0x90
kernel:  [] i2c_sysfs_new_device+0x1c5/0x250
kernel:  [] ? might_fault+0x2e/0x80
kernel:  [] ? i2c_sysfs_new_device+0x0/0x250
kernel:  [] dev_attr_store+0x25/0x30
kernel:  [] sysfs_write_file+0x9c/0xf0
kernel:  [] vfs_write+0x9c/0x160
kernel:  [] ? sysfs_write_file+0x0/0xf0
kernel:  [] sys_write+0x3d/0x70
kernel:  [] sysenter_do_call+0x12/0x36

Signed-off-by: Jean Delvare

i2c/tsl2550: Fix lux value in extended mode

2009-11-26T08:22:32+00:00

According to the TAOS Application Note 'Controlling a Backlight with
the TSL2550 Ambient Light Sensor' (page 14), the actual lux value in
extended mode should be obtained multiplying the calculated lux value
by 5.

Signed-off-by: Michele Jr De Candia 
Signed-off-by: Jean Delvare

ARM: PNX4008: i2c-pnx: use the same dev_id for request_irq and free_irq

2009-11-21T19:01:05+00:00

This allows i2c-pnx to free its interrupt handler when the module
is removed or if an error occurs; using the same dev_id for both
request_irq and free_irq is desirable.

Signed-off-by: Russell King 
Acked-by: Ben Dooks