[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200326163807.23216-1-geert+renesas@glider.be>
Date: Thu, 26 Mar 2020 17:38:04 +0100
From: Geert Uytterhoeven <geert+renesas@...der.be>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Rob Herring <robh+dt@...nel.org>
Cc: Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>,
linux-usb@...r.kernel.org, devicetree@...r.kernel.org,
linux-renesas-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
Geert Uytterhoeven <geert+renesas@...der.be>
Subject: [PATCH 0/2] dt-bindings: usb: generic-ehci/ohci: Document power-domains property
Hi Greg, Rob,
It is quite common for a generic EHCI or OHCI block to be embedded in an
SoC in its own power domain. However, the current DT bindings do not
cover this yet, leading to "make dtbs_check" warnings like:
arch/arm64/boot/dts/renesas/r8a774a1-hihope-rzg2m.dt.yaml: usb@...80000: 'power-domains' does not match any of the regexes: 'pinctrl-[0-9]+'
arch/arm64/boot/dts/renesas/r8a774a1-hihope-rzg2m.dt.yaml: usb@...80100: 'power-domains' does not match any of the regexes: 'pinctrl-[0-9]+'
This patch series documents the optional presence of "power-domains"
properties in the EHCI and OHCI devices nodes, allowing the DTS writer
to describe the controllers' positions in the power hierarchy.
Thanks!
Geert Uytterhoeven (2):
dt-bindings: usb: generic-ehci: Document power-domains property
dt-bindings: usb: generic-ohci: Document power-domains property
Documentation/devicetree/bindings/usb/generic-ehci.yaml | 3 +++
Documentation/devicetree/bindings/usb/generic-ohci.yaml | 3 +++
2 files changed, 6 insertions(+)
--
2.17.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists