| Message ID | 20200326163807.23216-3-geert+renesas@glider.be |
|---|---|
| State | New |
| Headers | show |
| Series | dt-bindings: usb: generic-ehci/ohci: Document power-domains property | expand |
diff --git a/Documentation/devicetree/bindings/usb/generic-ohci.yaml b/Documentation/devicetree/bindings/usb/generic-ohci.yaml index bcffec1f1341e502..d7efddf27b22e264 100644 --- a/Documentation/devicetree/bindings/usb/generic-ohci.yaml +++ b/Documentation/devicetree/bindings/usb/generic-ohci.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:
It is quite common for a generic OHCI 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@ee080000: 'power-domains' does not match any of the regexes: 'pinctrl-[0-9]+' Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> --- Documentation/devicetree/bindings/usb/generic-ohci.yaml | 3 +++ 1 file changed, 3 insertions(+)