devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
	John Youn <John.Youn@synopsys.com>
Subject: Re: [RFC PATCH 1/3] dt-bindings: usb: Add undetected disconnection quirk
Date: Fri, 30 Oct 2020 10:25:44 -0500	[thread overview]
Message-ID: <20201030152544.GA3868912@bogus> (raw)
In-Reply-To: <770d7a50caad241f07d656e29e89e282f727f5da.1603343705.git.Thinh.Nguyen@synopsys.com>

On Wed, Oct 21, 2020 at 10:15:43PM -0700, Thinh Nguyen wrote:
> Synopsys DWC_usb3x host controllers will not detect enhanced super-speed
> (eSS) device disconnection if it has active isochronous IN endpoint(s)

Why do you need a DT quirk if it's all DWC3? Imply it from the 
compatible.

> behind one or more eSS hubs. Introduce a quirk to workaround this for
> xhci and dwc3 device tree.
> 
> Signed-off-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
> ---
>  Documentation/devicetree/bindings/usb/dwc3.txt     | 3 +++
>  Documentation/devicetree/bindings/usb/usb-xhci.txt | 2 ++

These are getting converted to schema.

>  2 files changed, 5 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/usb/dwc3.txt b/Documentation/devicetree/bindings/usb/dwc3.txt
> index 1aae2b6160c1..b23b52f5842a 100644
> --- a/Documentation/devicetree/bindings/usb/dwc3.txt
> +++ b/Documentation/devicetree/bindings/usb/dwc3.txt
> @@ -105,6 +105,9 @@ Optional properties:
>  			this and tx-thr-num-pkt-prd to a valid, non-zero value
>  			1-16 (DWC_usb31 programming guide section 1.2.3) to
>  			enable periodic ESS TX threshold.
> + - snps,blocked-disconnection: enable workaround to undetected disconnection
> +			while isoc endpoint(s) are active for DWC_usb3x
> +			controllers operating as host

We certainly don't need 2 versions of the same property.

>   - <DEPRECATED> tx-fifo-resize: determines if the FIFO *has* to be reallocated.
>   - snps,incr-burst-type-adjustment: Value for INCR burst type of GSBUSCFG0
> diff --git a/Documentation/devicetree/bindings/usb/usb-xhci.txt b/Documentation/devicetree/bindings/usb/usb-xhci.txt
> index 0c5cff84a969..60812ae74d46 100644
> --- a/Documentation/devicetree/bindings/usb/usb-xhci.txt
> +++ b/Documentation/devicetree/bindings/usb/usb-xhci.txt
> @@ -28,6 +28,8 @@ Optional properties:
>    - quirk-broken-port-ped: set if the controller has broken port disable mechanism
>    - imod-interval-ns: default interrupt moderation interval is 5000ns
>    - phys : see usb-hcd.yaml in the current directory
> +  - blocked-disconnection: workaround undetected disconnection while isoc
> +		endpoint(s) are active
>  
>  additionally the properties from usb-hcd.yaml (in the current directory) are
>  supported.
> 
> base-commit: 270315b8235e3d10c2e360cff56c2f9e0915a252
> -- 
> 2.28.0
> 

      reply	other threads:[~2020-10-30 15:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22  5:15 [RFC PATCH 1/3] dt-bindings: usb: Add undetected disconnection quirk Thinh Nguyen
2020-10-30 15:25 ` Rob Herring [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=20201030152544.GA3868912@bogus \
    --to=robh@kernel.org \
    --cc=John.Youn@synopsys.com \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=devicetree@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).