From: Conor Dooley <conor@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
dri-devel@lists.freedesktop.org,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: display: renesas,du: add top-level constraints
Date: Mon, 19 Aug 2024 18:11:48 +0100 [thread overview]
Message-ID: <20240819-destiny-sampling-e9bdaa79e128@spud> (raw)
In-Reply-To: <20240818173003.122025-2-krzysztof.kozlowski@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 2087 bytes --]
On Sun, Aug 18, 2024 at 07:30:03PM +0200, 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 clocks, clock-names, interrupts, resets, reset-names, renesas,cmms
> and renesas,vsps.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> .../bindings/display/renesas,du.yaml | 26 ++++++++++++++++---
> 1 file changed, 22 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/display/renesas,du.yaml b/Documentation/devicetree/bindings/display/renesas,du.yaml
> index 147842b6465a..9a2d1c08cb1f 100644
> --- a/Documentation/devicetree/bindings/display/renesas,du.yaml
> +++ b/Documentation/devicetree/bindings/display/renesas,du.yaml
> @@ -46,12 +46,26 @@ properties:
> maxItems: 1
>
> # See compatible-specific constraints below.
> - clocks: true
> - clock-names: true
> + clocks:
> + minItems: 1
> + maxItems: 8
> +
> + clock-names:
> + minItems: 1
> + maxItems: 8
> +
> interrupts:
> + minItems: 1
> + maxItems: 4
> description: Interrupt specifiers, one per DU channel
> - resets: true
> - reset-names: true
> +
> + resets:
> + minItems: 1
> + maxItems: 2
> +
> + reset-names:
> + minItems: 1
> + maxItems: 2
>
> power-domains:
> maxItems: 1
> @@ -77,6 +91,8 @@ properties:
>
> renesas,cmms:
> $ref: /schemas/types.yaml#/definitions/phandle-array
> + minItems: 2
> + maxItems: 4
> items:
> maxItems: 1
> description:
> @@ -85,6 +101,8 @@ properties:
>
> renesas,vsps:
> $ref: /schemas/types.yaml#/definitions/phandle-array
> + minItems: 1
> + maxItems: 4
> items:
> items:
> - description: phandle to VSP instance that serves the DU channel
> --
> 2.43.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-08-19 17:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 17:30 [PATCH 1/2] dt-bindings: display: renesas,du: narrow interrupts and resets per variants Krzysztof Kozlowski
2024-08-18 17:30 ` [PATCH 1/2] dt-bindings: display: renesas, du: " Krzysztof Kozlowski
2024-08-18 17:30 ` [PATCH 2/2] dt-bindings: display: renesas,du: add top-level constraints Krzysztof Kozlowski
2024-08-18 17:30 ` [PATCH 2/2] dt-bindings: display: renesas, du: " Krzysztof Kozlowski
2024-08-18 17:46 ` [PATCH 2/2] dt-bindings: display: renesas,du: " Laurent Pinchart
2024-08-19 17:11 ` Conor Dooley [this message]
2024-08-18 17:41 ` [PATCH 1/2] dt-bindings: display: renesas,du: narrow interrupts and resets per variants Laurent Pinchart
2024-08-18 17:44 ` Krzysztof Kozlowski
2024-08-18 17:51 ` Laurent Pinchart
2024-08-18 18:48 ` Krzysztof Kozlowski
2024-08-28 12:45 ` Laurent Pinchart
2024-08-28 12:52 ` Krzysztof Kozlowski
2024-08-28 13:29 ` Laurent Pinchart
2024-08-19 17:12 ` Conor Dooley
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=20240819-destiny-sampling-e9bdaa79e128@spud \
--to=conor@kernel.org \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert+renesas@glider.be \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=magnus.damm@gmail.com \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=tzimmermann@suse.de \
/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.