From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Prashanth K <prashanth.k@oss.qualcomm.com>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6] usb: dwc3: Log dwc3 address in traces
Date: Tue, 27 Jan 2026 02:37:30 +0000 [thread overview]
Message-ID: <20260127023705.socfec5rijvqh7qh@synopsys.com> (raw)
In-Reply-To: <20260122105000.4126769-1-prashanth.k@oss.qualcomm.com>
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@oss.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@synopsys.com>
Thanks,
Thinh
prev parent reply other threads:[~2026-01-27 2:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 10:50 Prashanth K
2026-01-27 2:37 ` Thinh Nguyen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260127023705.socfec5rijvqh7qh@synopsys.com \
--to=thinh.nguyen@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=prashanth.k@oss.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®