From: Rob Herring <robh@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH 1/2] dt-bindings: usb: generic-ehci: Document power-domains property
Date: Fri, 10 Apr 2020 11:31:08 -0500 [thread overview]
Message-ID: <20200410163108.GA13579@bogus> (raw)
In-Reply-To: <20200326163807.23216-2-geert+renesas@glider.be>
On Thu, 26 Mar 2020 17:38:05 +0100, Geert Uytterhoeven wrote:
> 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 <geert+renesas@glider.be>
> ---
> Documentation/devicetree/bindings/usb/generic-ehci.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
Applied, thanks.
Rob
next prev parent reply other threads:[~2020-04-10 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 16:38 [PATCH 0/2] dt-bindings: usb: generic-ehci/ohci: Document power-domains property Geert Uytterhoeven
2020-03-26 16:38 ` [PATCH 1/2] dt-bindings: usb: generic-ehci: " Geert Uytterhoeven
2020-04-10 16:31 ` Rob Herring [this message]
2020-03-26 16:38 ` [PATCH 2/2] dt-bindings: usb: generic-ohci: " Geert Uytterhoeven
2020-04-10 16:31 ` Rob Herring
2020-03-27 5:07 ` [PATCH 0/2] dt-bindings: usb: generic-ehci/ohci: " Yoshihiro Shimoda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200410163108.GA13579@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.