mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Prashanth K <prashanth.k@oss.qualcomm.com>,
	Steven Rostedt <rostedt@goodmis.org>
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] usb: dwc3: Log dwc3 instance name in traces
Date: Fri, 19 Sep 2025 21:01:54 +0000	[thread overview]
Message-ID: <20250919210150.lpawo24fq26pqls4@synopsys.com> (raw)
In-Reply-To: <4d6a555d-aa27-41ba-a194-06c51d86d1dc@oss.qualcomm.com>

++Steven

On Fri, Sep 19, 2025, Prashanth K wrote:
> 
> I think we need to go ahead with approach 1 (Passing dwc3 structure to
> dwc3_readl/writel), because we were wrong about the usage of
> container_of(), it wouldn't work since it's a __iomem pointer.
> 
> I'm planning to break this into a 3 patch series
> 1. Removal of dep->regs and use dwc->regs everywhere
> 2. Use dwc pointer in all dwc3_readl/writel()
> 3. Adding the base addr in traces.
> 

Ok.

Hi Steven,

I have a question about trace event configuration. Is there a mechanism
to associate tracepoints with specific device instances when defining
trace events?

This would be useful when we want to avoid extensive driver rewrites,
for both dwc3 and xHCI devices (and potentially others).

Thanks,
Thinh

      reply	other threads:[~2025-09-19 21:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 11:44 Prashanth K
2025-08-28 22:48 ` Thinh Nguyen
2025-09-01  9:56   ` Prashanth K
2025-09-02 23:44     ` Thinh Nguyen
2025-09-03  6:52       ` Prashanth K
2025-09-04  0:00         ` Thinh Nguyen
2025-09-04  9:09           ` Prashanth K
2025-09-04 23:44             ` Thinh Nguyen
2025-09-09  5:00               ` Prashanth K
2025-09-11  1:36                 ` Thinh Nguyen
2025-09-11  4:46                   ` Prashanth K
2025-09-12 21:54                     ` Thinh Nguyen
2025-09-12 23:11                       ` Thinh Nguyen
2025-09-19 10:59                       ` Prashanth K
2025-09-19 21:01                         ` 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=20250919210150.lpawo24fq26pqls4@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 \
    --cc=rostedt@goodmis.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®