diff options
| author | Marian Rotariu <marian.c.rotariu@gmail.com> | 2026-08-06 11:53:02 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2026-09-10 17:06:53 +0200 |
| commit | c5df31f10880737d13b75eff42faee7accb9f956 (patch) | |
| tree | 2c8e7a7c7b0a4822513e141d2e53dbf1aef73b72 /tools/lib/python/kdoc/python_version.py | |
| parent | 63b269ec537dc0fd26d0bd64872c26860d108c9d (diff) | |
| download | linux-next-c5df31f10880737d13b75eff42faee7accb9f956.tar.gz linux-next-c5df31f10880737d13b75eff42faee7accb9f956.zip | |
usb: typec: tipd: don't send GAID when probe fails in APP mode
When probe fails after the chip was already in APP mode (booted from
EEPROM), the err_reset_controller path unconditionally calls
tps->data->reset(), which for tps25750 sends the GAID 4CC command.
GAID transitions the chip from APP back to PTCH, causing a second
probe attempt that sees PTCH mode and tries to load the firmware from
/lib/firmware, instead of reading the EEPROM as it should.
The err_reset_controller path can be triggered by -EPROBE_DEFER from
the probe sequence. GAID should only be sent when the controller
actually loaded firmware at probe time.
The abnormal behavior was seen on a tps25751d that has an EEPROM
connected to it.
Fixes: d49f90822015 ("usb: typec: tipd: add init and reset functions to tipd_data")
Cc: stable <stable@kernel.org>
Signed-off-by: Marian Rotariu <marian.c.rotariu@gmail.com>
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Link: https://patch.msgid.link/20260806085302.1307606-1-marian.c.rotariu@gmail.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions