diff options
| author |   Geert Uytterhoeven <geert+renesas@glider.be> | 2020-03-26 17:38:06 +0100 |
|---|---|---|
| committer |   Rob Herring <robh@kernel.org> | 2020-04-14 07:59:54 -0500 |
| commit | e5bff02a101d670960ffdb0d0600b4ff08507836 (patch) | |
| tree | f5cc7d4a8bf27a6785a7dbfa0649f56d8f3ce238 /Documentation/devicetree/bindings/usb/generic-ohci.yaml | |
| parent | dt-bindings: usb: generic-ehci: Document power-domains property (diff) | |
| download | linux-dev-e5bff02a101d670960ffdb0d0600b4ff08507836.tar.xz linux-dev-e5bff02a101d670960ffdb0d0600b4ff08507836.zip | |
dt-bindings: usb: generic-ohci: Document power-domains property
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>
Reviewed-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Signed-off-by: Rob Herring <robh@kernel.org>
Diffstat (limited to 'Documentation/devicetree/bindings/usb/generic-ohci.yaml')
| -rw-r--r-- | Documentation/devicetree/bindings/usb/generic-ohci.yaml | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/usb/generic-ohci.yaml b/Documentation/devicetree/bindings/usb/generic-ohci.yaml index bcffec1f1341..d7efddf27b22 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: |