public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Rohloff <ingo.rohloff@lauterbach.com>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH] usb: dwc3: Support for USB3340x ULPI PHY, via "snps,enable_xcvrdly_quirk"
Date: Wed, 25 Feb 2026 13:49:59 +0100	[thread overview]
Message-ID: <20260225134959.39e775ff@ingpc2.intern.lauterbach.com> (raw)
In-Reply-To: <20260225000512.tle2eu4gkd4ut6bf@synopsys.com>

On Wed, 25 Feb 2026 00:05:17 +0000
Thinh Nguyen <Thinh.Nguyen@synopsys.com> wrote:

> > +	/*
> > +	 * Fixes High-speed negotiation issue with USB3340, see:
> > +	 * https://.../80000645A.pdf
> > +	 *    "Device Enumeration Failure with Link IP Systems"  
> 
> This platform specific info and how it was found should go into the
> commit message and not here.
>

Done.

> > +	 * According to documentation on the Internet,  
> 
> We should not just reference the "Internet". If you want to reference
> some documentation, please provide the DWC_usb3x document section and
> version.
>

I would love to, but Synopsys was completely unwilling to provide
a programming manual to me.

Synopsys told me I should contact Xilinx (now AMD) for access to the
programming manual; and of course Xilinx refused, because Xilinx
has signed an NDA.

The "Internet" was the only source, where I found this information.
The description I provide is from the forum post I now mention in the
commit message.
I put the description in the code, because I am afraid, that the forum
post vanishes and then this information is lost to the public.

I guess, if I were to gain access to the official programming manual,
citing it might be a violation of the NDA I likely would have signed,
but I am not a lawyer.

> 
> > +	 * DWC3_GUSB2PHYCFG_XCVRDLY:
> > +	 *    Adds a delay between the assertion of the
> > +	 *    ULPI Transceiver Select signal (for HS) and  
> 
> It can be for both ULPI and UTMI.
> 

Ah of course :-)
I now mention both: ULPI/UTMI.


> > +	dwc->enable_xcvrdly_quirk = device_property_read_bool(dev,
> > +				"snps,enable_xcvrdly_quirk");  
> 
> Use "-" instead of "_" for property name, and change it to
> "snps,enable-usb2-transceiver-delay"
> 
> ...
> > +	unsigned		enable_xcvrdly_quirk:1;  
> 
> Document the new field. Rename to enable_usb2_transceiver_delay.

Done.
Note: I used "-" before to avoid having different strings for the
member variable and the property name to make it easier to grep
for both at the same time.

> Also, how are you passing this quirk? Through devicetree or software
> node? I don't see the user of this property.
> 

On the hardware I have got (Xilinx Ultrascale+ ZynqMP) I pass it via
devicetree. I now added a 2nd commit, which adds documentation for the
devicetree bindings.

with best regards
  Ingo Rohloff

-------------------------------------------------------------------------
Dipl.-Inform.
Ingo ROHLOFF
Senior Staff Embedded Systems Engineering
phone +49 8102 9876-142 - ingo.rohloff@lauterbach.com

Lauterbach Engineering GmbH & Co. KG
Altlaufstrasse 40, 85635 Hoehenkirchen-Siegertsbrunn, GERMANY
www.lauterbach.com

Registered Office: Hoehenkirchen-Siegertsbrunn, Germany,
Local Court: Munich, HRA 87406, VAT ID: DE246770537,
Managing Directors: Lothar Lauterbach, Stephan Lauterbach, Dr. Thomas Ullmann

-------------------------------------------------------------------------

  reply	other threads:[~2026-02-25 12:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24 14:14 [PATCH] usb: dwc3: Support for USB3340x ULPI PHY, via "snps,enable_xcvrdly_quirk" Ingo Rohloff
2026-02-25  0:05 ` Thinh Nguyen
2026-02-25 12:49   ` Ingo Rohloff [this message]
2026-02-26  2:39     ` Thinh Nguyen
2026-02-26 11:32       ` Ingo Rohloff
2026-02-26 19:26         ` Thinh Nguyen
2026-02-26 20:27           ` Ingo Rohloff
2026-02-26 23:51             ` Thinh Nguyen
2026-02-27  0:02               ` Thinh Nguyen
2026-02-25 13:03   ` [PATCH v2 0/2] Re: [PATCH] usb: dwc3: Support for USB3340x ULPI PHY Ingo Rohloff
2026-02-25 13:03     ` [PATCH v2 1/2] usb: dwc3: Support USB3340x ULPI PHY high-speed negotiation Ingo Rohloff
2026-02-25 13:03     ` [PATCH v2 2/2] dt-bindings: usb: dwc3: Add property to insert delay before TxValid Ingo Rohloff
2026-02-26 10:51       ` Krzysztof Kozlowski
2026-02-26 16:12         ` Ingo Rohloff
2026-02-26 19:04           ` Thinh Nguyen
2026-02-27  0:20             ` Thinh Nguyen
2026-02-27 11:04               ` Ingo Rohloff
2026-02-28  1:05                 ` Thinh Nguyen
2026-02-26 10:51     ` [PATCH v2 0/2] Re: [PATCH] usb: dwc3: Support for USB3340x ULPI PHY Krzysztof Kozlowski

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=20260225134959.39e775ff@ingpc2.intern.lauterbach.com \
    --to=ingo.rohloff@lauterbach.com \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=gregkh@linuxfoundation.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