From: Ikjoon Jang <ikjn@chromium.org>
To: linux-usb@vger.kernel.org, devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alan Stern <stern@rowland.harvard.edu>,
Suwan Kim <suwan.kim027@gmail.com>,
"Gustavo A . R . Silva" <gustavo@embeddedor.com>,
Johan Hovold <johan@kernel.org>,
Nicolas Boitchat <drinkcat@chromium.org>,
Ikjoon Jang <ikjn@chromium.org>
Subject: [PATCH 1/2] dt-bindings: usb: add "hub,interval" property
Date: Sun, 17 Nov 2019 11:32:30 +0800 [thread overview]
Message-ID: <20191117033230.259647-1-ikjn@chromium.org> (raw)
Add "hub,interval" property to usb-device, so hub device can override
endpoint descriptor's bInterval.
Some existing hub devices have adjustable interval so the device is
allowed to use different bInterval. This is useful when the hub's default
bInterval is too big, so child device's waking up from autosuspend
takes much time.
Signed-off-by: Ikjoon Jang <ikjn@chromium.org>
---
Documentation/devicetree/bindings/usb/usb-device.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/usb/usb-device.txt b/Documentation/devicetree/bindings/usb/usb-device.txt
index 036be172b1ae..44bef2ff2704 100644
--- a/Documentation/devicetree/bindings/usb/usb-device.txt
+++ b/Documentation/devicetree/bindings/usb/usb-device.txt
@@ -66,6 +66,9 @@ Required properties for host-controller nodes with device nodes:
- #size-cells: shall be 0
+Optional properties for hub nodes
+- hub,interval: bInterval of status change endpoint. The range is 1-255.
+
Example:
&usb1 { /* host controller */
@@ -75,6 +78,7 @@ Example:
hub@1 { /* hub connected to port 1 */
compatible = "usb5e3,608";
reg = <1>;
+ hub,interval = <8>;
};
device@2 { /* device connected to port 2 */
--
2.24.0.432.g9d3f5f5b63-goog
reply other threads:[~2019-11-17 3:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20191117033230.259647-1-ikjn@chromium.org \
--to=ikjn@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@embeddedor.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=suwan.kim027@gmail.com \
/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).