linux.git/drivers/i2c/algos, branch v2.6.31

i2c-algo-pca: Let PCA9564 recover from unacked data byte (state 0x30)

2009-05-05T06:39:25+00:00

Currently, the i2c-algo-pca driver does nothing if the chip enters state
0x30 (Data byte in I2CDAT has been transmitted; NOT ACK has been
received).  Thus, the i2c bus connected to the controller gets stuck
afterwards.

I have seen this kind of error on a custom board in certain load
situations most probably caused by interference or noise.

A possible reaction is to let the controller generate a STOP condition.
This is documented in the PCA9564 data sheet (2006-09-01) and the same
is done for other NACK states as well.

Further, state 0x38 isn't handled completely, either. Try to do another
START in this case like the data sheet says. As this couldn't be tested,
I've added a comment to try to reset the chip if the START doesn't help
as suggested by Wolfram Sang.

Signed-off-by: Enrik Berkhan 
Reviewed-by: Wolfram Sang 
Signed-off-by: Jean Delvare

i2c-algo-bit: Fix timeout test

2009-05-05T06:39:24+00:00

When fetching DDC using i2c algo bit, we were often seeing timeouts
before getting valid EDID on a retry. The VESA spec states 2ms is the
DDC timeout, so when this translates into 1 jiffie and we are close
to the end of the time period, it could return with a timeout less than
2ms.

Change this code to use time_after instead of time_after_eq.

Signed-off-by: Dave Airlie 
Signed-off-by: Jean Delvare

i2c-algo-pca: Fix use of uninitialized variable in debug message

2009-04-13T15:02:13+00:00

A recent change broke debugging of pca_xfer(), fix it.

Reported-by: Geert Uytterhoeven 
Signed-off-by: Jean Delvare 
Acked-by: Wolfram Sang

i2c: Delete unused i2c-algo-sgi helper module

2009-04-06T16:12:25+00:00

The i2c-algo-sgi code was merged into the vino driver, so we can
delete it now.

Signed-off-by: Jean Delvare

i2c-algo-pca: Use timeout for checking the state machine

2009-03-28T20:34:45+00:00

We now timeout also if the state machine does not change within the
given time. For that, the driver-specific completion-functions are
extended to return true or false depending on the timeout. This then
gets checked in the algorithm.

Signed-off-by: Wolfram Sang 
Signed-off-by: Jean Delvare

i2c-algo-pca: Rework waiting for a free bus

2009-03-28T20:34:45+00:00

Waiting for a free bus now accepts the timeout value in jiffies and does
proper checking using time_before.

Signed-off-by: Wolfram Sang 
Signed-off-by: Jean Delvare

i2c-algo-pca: Add PCA9665 support

2009-03-28T20:34:44+00:00

Add support for the PCA9665 I2C controller.

Signed-off-by: Wolfram Sang 
Signed-off-by: Jean Delvare

i2c: Adapt debug macros for KERN_* constants

2009-03-28T20:34:44+00:00

According to kerneljanitors todo list all printk calls (beginning
a new line) should have an according KERN_* constant.
Those are the changes to the debug macros in the i2c subsystem
to meet this requirement. Also changing no-debug statements
to raw printks again.

Signed-off-by: Frank Seidel 
Signed-off-by: Jean Delvare 
Tested-by: Wolfram Sang

i2c: Set a default timeout value for all adapters

2009-03-28T20:34:43+00:00

Setting a default timeout value on a per-algo basis doesn't make any
sense. Move the default value setting to i2c-core. Individual adapter
drivers can specify a different (non-zero) value if they wish.

Also express the timeout value in a way which results in the same
duration regarless of the value of HZ.

Signed-off-by: Jean Delvare 
Acked-by: Wolfram Sang

i2c: Add missing KERN_* constants to printks

2009-03-28T20:34:42+00:00

According to kerneljanitors todo list all printk calls (beginning
a new line) should have an according KERN_* constant.
Those are the missing pieces here for the i2c subsystem.

Signed-off-by: Frank Seidel 
Signed-off-by: Jean Delvare