summaryrefslogtreecommitdiff
path: root/cmd/ti
diff options
context:
space:
mode:
authorNishanth Menon <nm@ti.com>2022-09-21 08:38:42 -0500
committerTom Rini <trini@konsulko.com>2022-09-29 10:10:39 -0400
commitd2ab2a2bafd53ace79da900900d5220931c7ef5a (patch)
tree89e9a295e37af1da9066a0d55c517dd93221a120 /cmd/ti
parentc47bb10a4dd937b35852bbbf082d1deee694c384 (diff)
downloadu-boot-d2ab2a2bafd53ace79da900900d5220931c7ef5a.tar.gz
u-boot-d2ab2a2bafd53ace79da900900d5220931c7ef5a.tar.bz2
u-boot-d2ab2a2bafd53ace79da900900d5220931c7ef5a.zip
board: ti: common: board_detect: Fix EEPROM read quirk for AM6 style data
The situation is similar to commit bf6376642fe8 ("board: ti: common: board_detect: Fix EEPROM read quirk"). This is seen on a variant of eeproms seen on some BeagleBone-AI64 which now has a mix of both 1 byte addressing and 2 byte addressing eeproms. Unlike the am335x (ti_i2c_eeprom_am_get) and dra7 (ti_i2c_eeprom_dra7_get) which use constant data structure which allows us to do a complete read of the data, the am6(ti_i2c_eeprom_am6_get) eeprom parse operation is dynamic. This removes the option of being able to read the complete eeprom data in one single shot. Fortunately, on the I2C bus, we do see the following behavior: In 1 byte mode, if we attempt to read the first header data yet again, the misbehaving 2 byte addressing device acts in constant addressing mode which results in the header not matching up and follow on attempt at 2 byte addressing scheme grabs the correct data. This costs us an extra ~3 milliseconds, which is a minor penalty compared to the consistent image support we need to have. Reported-by: Jason Kridner <jkridner@beagleboard.org> Fixes: a58147c2dbbf ("board: ti: common: board_detect: Do 1byte address checks first.") Signed-off-by: Nishanth Menon <nm@ti.com>
Diffstat (limited to 'cmd/ti')
0 files changed, 0 insertions, 0 deletions