[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <TYAPR01MB4544C0AD1F363CD0B5D8F43AD8CC0@TYAPR01MB4544.jpnprd01.prod.outlook.com>
Date: Fri, 27 Mar 2020 05:07:43 +0000
From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>
To: Geert Uytterhoeven <geert+renesas@...der.be>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Rob Herring <robh+dt@...nel.org>
CC: "linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-renesas-soc@...r.kernel.org"
<linux-renesas-soc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 0/2] dt-bindings: usb: generic-ehci/ohci: Document
power-domains property
Hi Geert-san,
> From: Geert Uytterhoeven, Sent: Friday, March 27, 2020 1:38 AM
>
> 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
Thank you for the patches!
Reviewed-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>
Best regards,
Yoshihiro Shimoda
Powered by blists - more mailing lists