diff options
author | Nick Thompson <nick.thompson@ge.com> | 2011-04-11 22:37:41 +0000 |
---|---|---|
committer | Heiko Schocher <hs@denx.de> | 2011-04-14 08:33:23 +0200 |
commit | 0e57968a215d1b9d271f3fa5bebeddeaea0c8075 (patch) | |
tree | cac33061d68c9d6af986a3e1b52326259f0a9ee2 /post | |
parent | 73e5476e1edf1b860dbd9b5fc21ef32ac1b551ba (diff) | |
download | u-boot-imx-0e57968a215d1b9d271f3fa5bebeddeaea0c8075.zip u-boot-imx-0e57968a215d1b9d271f3fa5bebeddeaea0c8075.tar.gz u-boot-imx-0e57968a215d1b9d271f3fa5bebeddeaea0c8075.tar.bz2 |
I2C: OMAP: detect more devices when probing an i2c bus
The omap24xx driver only seems to support devices that have a single subaddress
byte. With these types of devices, the first access in a bus transaction is
usually a write (writes the subaddress) followed by either a read or write to
access the devices registers.
Many such devices will respond to a read as the first access, but there are at
least some that will NACK such a read. (e.g. ADV7180.)
The probe function attempts to detect a devices ACK to a read access only and
fails to find devices that NACK a read.
This commit modifies the probe function to start a write instead. This detects
devices that respond to reads (since they must also respond to writes) as well
as those that only respond to writes. The bus is immediately set to idle after a
(N)ACK avoiding actually writing anything to the device.
Signed-off-by: Nick Thompson <nick.thompson@ge.com>
Diffstat (limited to 'post')
0 files changed, 0 insertions, 0 deletions