From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Kuen-Han Tsai <khtsai@google.com>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
"gregkh@linuxfoundation.org" <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 1/2] usb: dwc3: Add trace event for dwc3_set_prtcap
Date: Thu, 21 Aug 2025 23:30:36 +0000 [thread overview]
Message-ID: <20250821233035.e2yl3yvoq5i4jpdz@synopsys.com> (raw)
In-Reply-To: <20250818060757.2519126-1-khtsai@google.com>
On Mon, Aug 18, 2025, Kuen-Han Tsai wrote:
> Changes to the port capability can be indirectly observed by tracing
> register writes to DWC3_GCTL. However, this requires interpreting the
> raw value, which is neither intuitive nor precise for debugging.
> Monitoring these mode changes is essential for resolving issues related
> to USB role switching and enumeration.
>
> Introduce a dedicated trace event to provide a human-readable log when
> the port capability is configured.
>
> Signed-off-by: Kuen-Han Tsai <khtsai@google.com>
> ---
> drivers/usb/dwc3/core.c | 1 +
> drivers/usb/dwc3/debug.h | 18 ++++++++++++++++++
> drivers/usb/dwc3/trace.h | 17 +++++++++++++++++
> 3 files changed, 36 insertions(+)
>
> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
> index 8002c23a5a02..370fc524a468 100644
> --- a/drivers/usb/dwc3/core.c
> +++ b/drivers/usb/dwc3/core.c
> @@ -156,6 +156,7 @@ void dwc3_set_prtcap(struct dwc3 *dwc, u32 mode, bool ignore_susphy)
> dwc3_writel(dwc->regs, DWC3_GCTL, reg);
>
> dwc->current_dr_role = mode;
> + trace_dwc3_set_prtcap(mode);
> }
>
> static void __dwc3_set_mode(struct work_struct *work)
> diff --git a/drivers/usb/dwc3/debug.h b/drivers/usb/dwc3/debug.h
> index 09d703852a92..70d90790f872 100644
> --- a/drivers/usb/dwc3/debug.h
> +++ b/drivers/usb/dwc3/debug.h
> @@ -13,6 +13,24 @@
>
> #include "core.h"
>
> +/**
> + * dwc3_mode_string - returns mode name
> + * @mode: mode code
Minor nit: would be better to document as GCTL.PrtCapDir value, but it's
obvious looking at this small function. So it's fine.
> + */
> +static inline const char *dwc3_mode_string(u32 mode)
> +{
> + switch (mode) {
> + case DWC3_GCTL_PRTCAP_HOST:
> + return "host";
> + case DWC3_GCTL_PRTCAP_DEVICE:
> + return "device";
> + case DWC3_GCTL_PRTCAP_OTG:
> + return "otg";
> + default:
> + return "UNKNOWN";
> + }
> +}
> +
> /**
> * dwc3_gadget_ep_cmd_string - returns endpoint command string
> * @cmd: command code
> diff --git a/drivers/usb/dwc3/trace.h b/drivers/usb/dwc3/trace.h
> index bdeb1aaf65d8..b6ba984bafcd 100644
> --- a/drivers/usb/dwc3/trace.h
> +++ b/drivers/usb/dwc3/trace.h
> @@ -19,6 +19,23 @@
> #include "core.h"
> #include "debug.h"
>
> +DECLARE_EVENT_CLASS(dwc3_log_set_prtcap,
> + TP_PROTO(u32 mode),
> + TP_ARGS(mode),
> + TP_STRUCT__entry(
> + __field(u32, mode)
> + ),
> + TP_fast_assign(
> + __entry->mode = mode;
> + ),
> + TP_printk("mode %s", dwc3_mode_string(__entry->mode))
> +);
> +
> +DEFINE_EVENT(dwc3_log_set_prtcap, dwc3_set_prtcap,
> + TP_PROTO(u32 mode),
> + TP_ARGS(mode)
> +);
> +
> DECLARE_EVENT_CLASS(dwc3_log_io,
> TP_PROTO(void *base, u32 offset, u32 value),
> TP_ARGS(base, offset, value),
> --
> 2.51.0.rc1.163.g2494970778-goog
>
Acked-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Thanks,
Thinh
next prev parent reply other threads:[~2025-08-21 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 6:07 Kuen-Han Tsai
2025-08-18 6:07 ` [PATCH 2/2] usb: dwc3: Refactor dwc3_mode_show Kuen-Han Tsai
2025-08-21 23:30 ` Thinh Nguyen
2025-08-21 23:30 ` Thinh Nguyen [this message]
2025-08-22 9:27 ` [PATCH 1/2] usb: dwc3: Add trace event for dwc3_set_prtcap Kuen-Han Tsai
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=20250821233035.e2yl3yvoq5i4jpdz@synopsys.com \
--to=thinh.nguyen@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=khtsai@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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®