diff options
| author | Geert Uytterhoeven <[email protected]> | 2020-03-26 17:38:05 +0100 |
|---|---|---|
| committer | Rob Herring <[email protected]> | 2020-04-14 07:59:54 -0500 |
| commit | f98d7c3abca05471706c32ac47ec42fb4c71264d (patch) | |
| tree | 9dd8b944c84c26bf793bcbe3fdee8ff40599d589 | |
| parent | 8f3d9f354286745c751374f5f1fcafee6b3f3136 (diff) | |
dt-bindings: usb: generic-ehci: Document power-domains property
It is quite common for a generic EHCI block to be embedded in an SoC in
its own power domain. Hence allow the DTS writer to describe the
controller's position in the power hierarchy, by documenting the
optional presence of a "power-domains" property.
This gets rid of "make dtbs_check" warnings like:
arch/arm64/boot/dts/renesas/r8a774a1-hihope-rzg2m.dt.yaml: usb@ee080100: 'power-domains' does not match any of the regexes: 'pinctrl-[0-9]+'
Signed-off-by: Geert Uytterhoeven <[email protected]>
Reviewed-by: Yoshihiro Shimoda <[email protected]>
Signed-off-by: Rob Herring <[email protected]>
| -rw-r--r-- | Documentation/devicetree/bindings/usb/generic-ehci.yaml | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/usb/generic-ehci.yaml b/Documentation/devicetree/bindings/usb/generic-ehci.yaml index 10edd05872ea..848eea59bc00 100644 --- a/Documentation/devicetree/bindings/usb/generic-ehci.yaml +++ b/Documentation/devicetree/bindings/usb/generic-ehci.yaml @@ -36,6 +36,9 @@ properties: - if a USB DRD channel: first clock should be host and second one should be peripheral + power-domains: + maxItems: 1 + big-endian: $ref: /schemas/types.yaml#/definitions/flag description: |