diff options
| author | Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> | 2026-10-16 10:52:43 +0300 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2026-10-16 20:59:46 +0100 |
| commit | ba83dd4a47bb47da3d2791b2ad6cd816a851b5d0 (patch) | |
| tree | 91211775e99e570e408b6d9fb715e73ec9cd405f /include/linux/extcon | |
| parent | 98a375660baf9c0f459489efac9eb4898bbad832 (diff) | |
regulator: rpi-panel-attiny: Fix probe failure after a host cold boot
attiny_i2c_probe() reads REG_ID with attiny_i2c_read(), a function added
in commit e4a7e3f741f7 ("regulator/rpi-panel-attiny: Use two
transactions for I2C read") specifically for fixing REG_ID read failures
at probe.
On TI's BeagleY-AI (but also on other TI boards tested) with the
Raspberry Pi 7-inch touchscreen, the first I2C transfer to the attiny
after a cold boot of the board usually fails, so the probe fails.
Retrying the transfer once fixes the problem.
It is unclear why this happens, but as the earlier commit adding
attiny_i2c_read() shows, attiny seems to have i2c issues. It is not out
of the question that the issue could be on the TI i2c side, but as the
other i2c peripherals (like sensors) work fine, adding this workaround
to attiny driver feels sensible.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Link: https://patch.msgid.link/20261016-attiny-probe-fix-v1-1-96337ba58dfa@ideasonboard.com
Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'include/linux/extcon')
0 files changed, 0 insertions, 0 deletions