[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20260127023705.socfec5rijvqh7qh@synopsys.com>
Date: Tue, 27 Jan 2026 02:37:30 +0000
From: Thinh Nguyen <Thinh.Nguyen@...opsys.com>
To: Prashanth K <prashanth.k@....qualcomm.com>
CC: Thinh Nguyen <Thinh.Nguyen@...opsys.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6] usb: dwc3: Log dwc3 address in traces
On Thu, Jan 22, 2026, Prashanth K wrote:
> 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@....qualcomm.com>
> ---
> Changes in v6:
> - Fixed warning from kernel test robot: https://urldefense.com/v3/__https://lore.kernel.org/oe-kbuild-all/202601220002.cJKQOY2h-lkp@intel.com/__;!!A4F2R9G_pg!YCRybz4-8eH0gaaJYt-RzqY77nvISmYFv-OatMvbjqJmDgUTmhNXeDwV4L3LBD-8Gxfz2y6Gzc8IdS3AekA4_d0KwkNeCjk$
> - Link to v5: https://urldefense.com/v3/__https://lore.kernel.org/all/20260121084550.3112162-1-prashanth.k@oss.qualcomm.com/__;!!A4F2R9G_pg!YCRybz4-8eH0gaaJYt-RzqY77nvISmYFv-OatMvbjqJmDgUTmhNXeDwV4L3LBD-8Gxfz2y6Gzc8IdS3AekA4_d0K5NPDjyU$
>
> drivers/usb/dwc3/core.c | 2 +-
> drivers/usb/dwc3/ep0.c | 2 +-
> drivers/usb/dwc3/gadget.c | 2 +-
> drivers/usb/dwc3/io.h | 4 +-
> drivers/usb/dwc3/trace.h | 88 ++++++++++++++++++++++++---------------
> 5 files changed, 60 insertions(+), 38 deletions(-)
>
Acked-by: Thinh Nguyen <Thinh.Nguyen@...opsys.com>
Thanks,
Thinh
Powered by blists - more mailing lists