From: Yaqin Pan <akingchen@vivo.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>, Felipe Balbi <balbi@kernel.org>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: kernel@vivo.com, Yaqin Pan <akingchen@vivo.com>
Subject: [PATCH 2/2] dt-bindings: usb: document snps,dis_split_quirk property in dwc3
Date: Wed, 15 Dec 2021 21:03:24 +0800 [thread overview]
Message-ID: <20211215130325.19017-3-akingchen@vivo.com> (raw)
In-Reply-To: <20211215130325.19017-1-akingchen@vivo.com>
Add snps,dis_split_quirk property for dwc3 controller
Signed-off-by: Yaqin Pan <akingchen@vivo.com>
---
Documentation/devicetree/bindings/usb/snps,dwc3.yaml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/usb/snps,dwc3.yaml b/Documentation/devicetree/bindings/usb/snps,dwc3.yaml
index 41416fbd92aa..e9615ca8f447 100644
--- a/Documentation/devicetree/bindings/usb/snps,dwc3.yaml
+++ b/Documentation/devicetree/bindings/usb/snps,dwc3.yaml
@@ -226,6 +226,12 @@ properties:
avoid -EPROTO errors with usbhid on some devices (Hikey 970).
type: boolean
+ snps,dis_split_quirk:
+ description:
+ When set, change the way host controller schedules transations for a Control transfer.
+ Needed to avoid emurate some devices fail.
+ type: boolean
+
snps,is-utmi-l1-suspend:
description:
True when DWC3 asserts output signal utmi_l1_suspend_n, false when
--
2.17.1
next prev parent reply other threads:[~2021-12-15 13:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 13:03 [PATCH 0/2] usb: dwc3: Add a quirk to set GUCTL.SPRSCTRLTRANSEN bit Yaqin Pan
2021-12-15 13:03 ` [PATCH 1/2] " Yaqin Pan
2021-12-15 13:03 ` Yaqin Pan [this message]
2021-12-16 8:26 ` [PATCH 2/2] dt-bindings: usb: document snps,dis_split_quirk property in dwc3 Sergey Shtylyov
2021-12-16 15:59 ` Sergey Shtylyov
2021-12-16 20:19 ` Rob Herring
2021-12-17 14:45 ` Yaqin Pan
2022-01-05 16:47 ` Rob Herring
2021-12-17 14:47 ` Yaqin Pan
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=20211215130325.19017-3-akingchen@vivo.com \
--to=akingchen@vivo.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@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