Re: [PATCH] usb: dwc3: Log dwc3 instance name in traces
From: Thinh Nguyen
Date: Fri Sep 19 2025 - 17:02:31 EST
++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