summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorMichal Pecio <michal.pecio@gmail.com>2025-03-11 18:45:50 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-03-11 19:58:43 +0300
commitdfc88357b6b6356dadea06b2c0bc8041f5e11720 (patch)
tree26c7a4a3722517b31a0c5465249f44355b1a4364 /tools/perf/scripts/python/stackcollapse.py
parent0c74d232578b1a7071e0312312811cb75b26b202 (diff)
downloadlinux-dfc88357b6b6356dadea06b2c0bc8041f5e11720.tar.xz
usb: xhci: Don't change the status of stalled TDs on failed Stop EP
When the device stalls an endpoint, current TD is assigned -EPIPE status and Reset Endpoint is queued. If a Stop Endpoint is pending at the time, it will run before Reset Endpoint and fail due to the stall. Its handler will change TD's status to -EPROTO before Reset Endpoint handler runs and initiates giveback. Check if the stall has already been handled and don't try to do it again. Since xhci_handle_halted_endpoint() performs this check too, not overwriting td->status is the only difference. I haven't seen this case yet, but I have seen a related one where the xHC has already executed Reset Endpoint, EP Context state is now Stopped and EP_HALTED is set. If the xHC took a bit longer to execute Reset Endpoint, said case would become this one. Signed-off-by: Michal Pecio <michal.pecio@gmail.com> Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com> Link: https://lore.kernel.org/r/20250311154551.4035726-3-mathias.nyman@linux.intel.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions