From: Philipp Zabel <p.zabel@pengutronix.de>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: reset: Add parent "resets" property as optional
Date: Mon, 04 Apr 2022 12:19:42 +0200 [thread overview]
Message-ID: <1787d3136a36e58e25a5906ac3807f14ed4f5e17.camel@pengutronix.de> (raw)
In-Reply-To: <1648617078-8312-1-git-send-email-hayashi.kunihiko@socionext.com>
On Mi, 2022-03-30 at 14:11 +0900, Kunihiko Hayashi wrote:
> LD11 mio reset controller has a reset lines from system controller.
> Add parent "resets" property to fix the following warning.
>
> uniphier-ld11-global.dt.yaml: reset: 'resets' does not match any of
> the regexes: 'pinctrl-[0-9]+'
> From schema:
> Documentation/devicetree/bindings/reset/socionext,uniphier-reset.yaml
>
> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
> ---
>
> Changes since v1:
> - Use maxItems for a single reset
>
> .../devicetree/bindings/reset/socionext,uniphier-reset.yaml | 3
> +++
> 1 file changed, 3 insertions(+)
>
> diff --git
> a/Documentation/devicetree/bindings/reset/socionext,uniphier-
> reset.yaml
> b/Documentation/devicetree/bindings/reset/socionext,uniphier-
> reset.yaml
> index 377a7d242323..6566804ec567 100644
> --- a/Documentation/devicetree/bindings/reset/socionext,uniphier-
> reset.yaml
> +++ b/Documentation/devicetree/bindings/reset/socionext,uniphier-
> reset.yaml
> @@ -55,6 +55,9 @@ properties:
> "#reset-cells":
> const: 1
>
> + resets:
> + maxItems: 1
> +
> additionalProperties: false
>
> required:
Thank you, applied to reset/fixes.
regards
Philipp
prev parent reply other threads:[~2022-04-04 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 5:11 [PATCH v2] dt-bindings: reset: Add parent "resets" property as optional Kunihiko Hayashi
2022-03-30 7:05 ` Krzysztof Kozlowski
2022-04-04 10:19 ` Philipp Zabel [this message]
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=1787d3136a36e58e25a5906ac3807f14ed4f5e17.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=robh+dt@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).