diff options
author | Stefani Seibold <stefani@seibold.net> | 2011-01-03 09:28:59 +0000 |
---|---|---|
committer | Paul Mundt <lethal@linux-sh.org> | 2011-01-06 15:52:19 +0900 |
commit | 748103e7235892bf9a3ee568d7d4dd7e5a3beece (patch) | |
tree | 64e9ab69ea39b169d96df92cc2cf0073fb6617ed /fs | |
parent | 529ed806d4540d23ca2f68b28c3715d1566fc3ac (diff) | |
download | linux-3.10-748103e7235892bf9a3ee568d7d4dd7e5a3beece.tar.gz linux-3.10-748103e7235892bf9a3ee568d7d4dd7e5a3beece.tar.bz2 linux-3.10-748103e7235892bf9a3ee568d7d4dd7e5a3beece.zip |
drivers/video/i810/i810-i2c.c: fix i2c bus handling
These patch fix a longstanding bug in the i810 frame buffer driver.
The handling of the i2c bus is wrong: A 1 bit should not written to the
i2c, these will be done by switch the i2c to input. Driving an 1 bit
active is against the i2c spec.
An active driven of a 1 bit will result in very strange error, depending
which side is the more powerful one. In my case it depends on the
temperature of the Display-Controller-EEprom: With an cold eprom a got
the correct EDID datas, with a warm one some of the 1 bits was 0 :-(
The same bug is also in the intelfb driver in the file
drivers/video/intelfb/intelfb_i2c.c. The functions intelfb_gpio_setscl()
and intelfb_gpio_setsda() do drive the 1 bit active to the i2c bus. But
since i have no card which is used by the intelfb driver i cannot fix
it.
Signed-off-by: Stefani Seibold <stefani@seibold.net>
Cc: Paul Mundt <lethal@linux-sh.org>
Cc: Jean Delvare <khali@linux-fr.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions