| Message ID | 20191117033230.259647-1-ikjn@chromium.org |
|---|---|
| State | Superseded, archived |
| Headers | show |
| Series | usb: override hub device bInterval with device node | expand |
| Context | Check | Description |
|---|---|---|
| robh/checkpatch | success |
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 */
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(+)