summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/task-analyzer.py
diff options
context:
space:
mode:
authorPrashanth K <prashanth.k@oss.qualcomm.com>2026-01-22 16:20:00 +0530
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2026-01-27 15:52:45 +0100
commit0a06917432a762d6233f88963c0b53e48dbac6b4 (patch)
tree588c53e094be1faabaf766e8ea02b8e17bf9a5aa /tools/perf/scripts/python/task-analyzer.py
parent1132e90840abf3e7db11f1d28199e9fbc0b0e69e (diff)
downloadlinux-0a06917432a762d6233f88963c0b53e48dbac6b4.tar.gz
linux-0a06917432a762d6233f88963c0b53e48dbac6b4.zip
usb: dwc3: Log dwc3 address in traces
When multiple DWC3 controllers are being used, trace events from different instances get mixed up making debugging difficult as there's no way to distinguish which instance generated the trace. Use the register base address of dwc3 controller and append it to trace events, so that the source instance is clearly identifiable. Example trace output, before -> dwc3_event: event (00000101): Reset [U0] after -> dwc3_event: 0x000000000a600000: event (00000101): Reset [U0] Signed-off-by: Prashanth K <prashanth.k@oss.qualcomm.com> Acked-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com> Link: https://patch.msgid.link/20260122105000.4126769-1-prashanth.k@oss.qualcomm.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions