post/i2c: Don't probe address 0
authorPeter Tyser <ptyser@xes-inc.com>
Fri, 22 Oct 2010 05:20:29 +0000 (00:20 -0500)
committerKumar Gala <galak@kernel.crashing.org>
Fri, 22 Oct 2010 07:18:42 +0000 (02:18 -0500)
commit9f949c9ac2c1bb5077a146753e24c7b3fe099991
treef57970a4f08ab50c09371a7283ef95a4583038ce
parent7e263cea88995d0b4b9fb659a95c382128feca71
post/i2c: Don't probe address 0

According to the I2C specification device address 0 is the "general call
address", ie a broadcast address.  The I2C specification states that the
format of a general call uses at least 2 bytes, which U-Boot's probing
routine does not adhere to.

Not probing device address 0 will prevent possible issues with devices
that accept general calls.  Additionally, this change shouldn't reduce
POST coverage since each I2C device should still be accessed via its
own, unique address.

Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
Acked-by: Heiko Schocher <hs@denx.de>
Acked-by: Wolfgang Denk <wd@denx.de>
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
post/drivers/i2c.c