From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: reset: socionext,uniphier-glue-reset: add top-level constraints
Date: Wed, 21 Aug 2024 19:31:28 +0900 [thread overview]
Message-ID: <9fcb9c03-080d-4798-8173-a24c7d05b420@socionext.com> (raw)
In-Reply-To: <20240818172819.121697-1-krzysztof.kozlowski@linaro.org>
Hi Krzysztof,
On 2024/08/19 2:28, Krzysztof Kozlowski wrote:
> Properties with variable number of items per each device are expected to
> have widest constraints in top-level "properties:" block and further
> customized (narrowed) in "if:then:". Add missing top-level constraints
> for clock-names and reset-names.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> .../bindings/reset/socionext,uniphier-glue-reset.yaml | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git
> a/Documentation/devicetree/bindings/reset/socionext,uniphier-glue-reset.ya
> ml
> b/Documentation/devicetree/bindings/reset/socionext,uniphier-glue-reset.ya
> ml
> index fa253c518d79..babc563ae61e 100644
> ---
> a/Documentation/devicetree/bindings/reset/socionext,uniphier-glue-reset.ya
> ml
> +++
> b/Documentation/devicetree/bindings/reset/socionext,uniphier-glue-reset.ya
> ml
> @@ -38,13 +38,17 @@ properties:
> minItems: 1
> maxItems: 2
>
> - clock-names: true
> + clock-names:
> + minItems: 1
> + maxItems: 2
>
> resets:
> minItems: 1
> maxItems: 2
>
> - reset-names: true
> + reset-names:
> + minItems: 1
> + maxItems: 2
>
> allOf:
> - if:
Reviewed-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
I'd appreciate if it could be applied in devicetree or reset.
Thank you,
---
Best Regards
Kunihiko Hayashi
next prev parent reply other threads:[~2024-08-21 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 17:28 Krzysztof Kozlowski
2024-08-19 17:13 ` Rob Herring (Arm)
2024-08-21 10:31 ` Kunihiko Hayashi [this message]
2024-09-02 9:48 ` Philipp Zabel
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=9fcb9c03-080d-4798-8173-a24c7d05b420@socionext.com \
--to=hayashi.kunihiko@socionext.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@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
all inboxes | Powered by JetHome®