diff options
| author | Dmitry Baryshkov <dmitry.baryshkov@linaro.org> | 2024-04-08 04:04:17 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-04-09 17:38:58 +0200 |
| commit | 1a395af9d53c6240bf7799abc43b4dc292ca9dd0 (patch) | |
| tree | b065fc567a2605aa40c4383d383a02d1ed338c57 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | c82d6cbb03ccb7ca0162f144ffa320479588b792 (diff) | |
usb: typec: ucsi_glink: drop special handling for CCI_BUSY
Newer Qualcomm platforms (sm8450+) successfully handle busy state and
send the Command Completion after sending the Busy state. Older devices
have firmware bug and can not continue after sending the CCI_BUSY state,
but the command that leads to CCI_BUSY is already forbidden by the
NO_PARTNER_PDOS quirk.
Follow other UCSI glue drivers and drop special handling for CCI_BUSY
event. Let the UCSI core properly handle this state.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Link: https://lore.kernel.org/r/20240408-qcom-ucsi-fixes-bis-v1-3-716c145ca4b1@linaro.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions