From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: 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 v2] usb: dwc3: fix dwc3_readl() and dwc3_writel() calls in dwc3_ulpi_setup()
Date: Mon, 29 Jun 2026 12:36:13 +0100 [thread overview]
Message-ID: <1ac35409-be0d-478e-b6f3-0dd9b7b92304@codethink.co.uk> (raw)
In-Reply-To: <aj77LIT5EiOHze1f@vbox>
On 26/06/2026 23:23, Thinh Nguyen wrote:
> On Tue, Jun 23, 2026, Ben Dooks wrote:
>> The dwc3_ulpi_setup() calls the register read and write calls with
>> dwc3->regs when both these calls take the dwc3 structure directly.
>>
>> Chnage these two calls to fix the following sparse warning, and
>> possibly a nasty bug in the dwc3_ulpi_setup() code:
>>
>> drivers/usb/dwc3/core.c:796:45: warning: incorrect type in argument 1 (different address spaces)
>> drivers/usb/dwc3/core.c:796:45: expected struct dwc3 *dwc
>> drivers/usb/dwc3/core.c:796:45: got void [noderef] __iomem *regs
>> drivers/usb/dwc3/core.c:798:40: warning: incorrect type in argument 1 (different address spaces)
>> drivers/usb/dwc3/core.c:798:40: expected struct dwc3 *dwc
>> drivers/usb/dwc3/core.c:798:40: got void [noderef] __iomem *regs
>>
>> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
>> ---
>> drivers/usb/dwc3/core.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
>> index 517aa7f1486d..ceb49f2f8004 100644
>> --- a/drivers/usb/dwc3/core.c
>> +++ b/drivers/usb/dwc3/core.c
>> @@ -789,9 +789,9 @@ static void dwc3_ulpi_setup(struct dwc3 *dwc)
>>
>> if (dwc->enable_usb2_transceiver_delay) {
>> for (index = 0; index < dwc->num_usb2_ports; index++) {
>> - reg = dwc3_readl(dwc->regs, DWC3_GUSB2PHYCFG(index));
>> + reg = dwc3_readl(dwc, DWC3_GUSB2PHYCFG(index));
>> reg |= DWC3_GUSB2PHYCFG_XCVRDLY;
>> - dwc3_writel(dwc->regs, DWC3_GUSB2PHYCFG(index), reg);
>> + dwc3_writel(dwc, DWC3_GUSB2PHYCFG(index), reg);
>> }
>> }
>> }
>> --
>> 2.37.2.352.g3c44437643
>>
>
> Ah! How did we miss this. Thanks for the catch.
I think it is probably limited hardware as the commit it was introduced
in was: dcdc3f399e3b ("usb: dwc3: Support USB3340x ULPI PHY high-speed
negotiation.")
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
https://www.codethink.co.uk/privacy.html
next prev parent reply other threads:[~2026-06-29 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 10:08 Ben Dooks
2026-06-26 22:23 ` Thinh Nguyen
2026-06-29 11:36 ` Ben Dooks [this message]
2026-06-29 11:37 Ben Dooks
2026-06-30 0:33 ` Thinh Nguyen
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=1ac35409-be0d-478e-b6f3-0dd9b7b92304@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=Thinh.Nguyen@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--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