linux.git/drivers/i2c, branch v2.6.26-rc2

i2c: Match dummy devices by type

2008-05-11T18:37:06+00:00

As the old driver_name/type matching scheme is going away soon, change
the dummy device mechanism to use the new matching scheme.

This has the downside that dummy i2c clients can no longer choose
their name, they'll all appear as "dummy" in sysfs and in log
messages. I don't think it is a problem in practice though, as there
is little reason to use these i2c clients to log messages.

Signed-off-by: Jean Delvare

i2c-sibyte: Mark i2c_sibyte_add_bus() as static

2008-05-11T18:37:05+00:00

The i2c_sibyte_add_bus() function is not called, nor meant to, from 
outside, so mark it as static; fixing a sparse warning too.

Signed-off-by: Maciej W. Rozycki 
Signed-off-by: Jean Delvare

i2c-sibyte: Correct a comment about frequency

2008-05-11T18:37:05+00:00

The frequency may have been once hardcoded to 100 kHz, but currently it is
passed as an argument to i2c_sibyte_add_bus(), so update the comment to
match code.  While at it, reformat a nearby comment for consistency.  No
functional changes.

Signed-off-by: Maciej W. Rozycki 
Signed-off-by: Jean Delvare

i2c-piix4: Blacklist two mainboards

2008-05-11T18:37:05+00:00

We had a report that running sensors-detect on a Sapphire AM2RD790
motherbord killed the CPU. While the exact cause is still unknown,
I'd rather play it safe and prevent any access to the SMBus on that
machine by not letting the i2c-piix4 driver attach to the SMBus host
device on that machine. Also blacklist a similar board made by DFI.

Signed-off-by: Jean Delvare

i2c-piix4: Increase the intitial delay for the ServerWorks CSB5

2008-05-11T18:37:05+00:00

Per the PIIX4 errata, there maybe a delay between setting the
start bit in the Smbus Host Controller Register and the transaction
actually starting. If the driver doesn't delay long enough, it
may appear that the transaction is complete when actually it
hasn't started, this may lead to bus collisions.

While 1 ms appears to be enough for most chips, the ServerWorks CSB5
wants 2 ms.

Signed-off-by: David Milburn 
Signed-off-by: Jean Delvare

i2c-mpc: Compare to NO_IRQ instead of zero

2008-05-11T18:37:04+00:00

Alter the mpc i2c driver to use the NO_IRQ symbol instead of the constant
zero when checking for valid interrupts. NO_IRQ=-1 on ppc and NO_IRQ=0 on
powerpc so the checks against zero are not correct.

Signed-off-by: Jon Smirl 
Signed-off-by: Jean Delvare

i2c: Convert most new-style drivers to use module aliasing

2008-04-29T21:11:40+00:00

Based on earlier work by Jon Smirl and Jochen Friedrich.

Update most new-style i2c drivers to use standard module aliasing
instead of the old driver_name/type driver matching scheme. I've
left the video drivers apart (except for SoC camera drivers) as
they're a bit more diffcult to deal with, they'll have their own
patch later.

Signed-off-by: Jean Delvare 
Cc: Jon Smirl 
Cc: Jochen Friedrich

i2c: Add support for device alias names

2008-04-29T21:11:39+00:00

Based on earlier work by Jon Smirl and Jochen Friedrich.

This patch allows new-style i2c chip drivers to have alias names using
the official kernel aliasing system and MODULE_DEVICE_TABLE(). At this
point, the old i2c driver binding scheme (driver_name/type) is still
supported.

Signed-off-by: Jean Delvare 
Cc: Jochen Friedrich 
Cc: Jon Smirl 
Cc: Kay Sievers

i2c-amd756-s4882: Fix an error path

2008-04-29T21:11:38+00:00

If initialization fails, we want to restore the physical bus, not delete
it again.

Signed-off-by: Jean Delvare

i2c/tps65010: Add missing intialization of client data

2008-04-29T21:11:38+00:00

tps65010_remove() calls i2c_get_clientdata(client) but the client data
is never set during initialization, so it gets a NULL pointer at best.

I guess it was never spotted because the tps65010 driver is typically
not built modular so this function is discarded.

Signed-off-by: Jean Delvare 
Cc: David Brownell