From: Conor Dooley <conor@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: shawnguo@kernel.org, marex@denx.de, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, conor+dt@kernel.org,
Fabio Estevam <festevam@denx.de>
Subject: Re: [PATCH v4 1/4] dt-bindings: display: bridge: ldb: Adjust imx6sx entries
Date: Sat, 20 May 2023 11:15:09 +0100 [thread overview]
Message-ID: <20230520-iphone-outreach-14f46c57b7cd@spud> (raw)
In-Reply-To: <20230519125236.352050-1-festevam@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1683 bytes --]
On Fri, May 19, 2023 at 09:52:33AM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <festevam@denx.de>
>
> On the i.MX6SX there is a single entry for 'reg' and 'reg-names', so add
> some logic to reflect that.
>
> Signed-off-by: Fabio Estevam <festevam@denx.de>
Whoops, didn't see this patch yesterday..
> ---
> Changes since v3:
> - None.
>
> .../bindings/display/bridge/fsl,ldb.yaml | 28 +++++++++++++++++--
> 1 file changed, 25 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/display/bridge/fsl,ldb.yaml b/Documentation/devicetree/bindings/display/bridge/fsl,ldb.yaml
> index 07388bf2b90d..cd63f9ef9484 100644
> --- a/Documentation/devicetree/bindings/display/bridge/fsl,ldb.yaml
> +++ b/Documentation/devicetree/bindings/display/bridge/fsl,ldb.yaml
> @@ -28,12 +28,12 @@ properties:
> const: ldb
>
> reg:
> + minItems: 1
> maxItems: 2
>
> reg-names:
> - items:
> - - const: ldb
> - - const: lvds
> + minItems: 1
> + maxItems: 2
>
> ports:
> $ref: /schemas/graph.yaml#/properties/ports
> @@ -74,6 +74,28 @@ allOf:
> properties:
> port@2: false
>
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - fsl,imx6sx-ldb
Why not const: for the single item?
Trying to avoid churn when you add your next one?
> + then:
> + properties:
> + reg:
> + maxItems: 1
> + reg-names:
> + items:
> + - const: ldb
Again, can drop the items: for const: for the single item, no?
Thanks,
Conor.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-05-20 10:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 12:52 [PATCH v4 1/4] dt-bindings: display: bridge: ldb: Adjust imx6sx entries Fabio Estevam
2023-05-19 12:52 ` [PATCH v4 2/4] dt-bindings: soc: Add i.MX6SX General Purpose Register Fabio Estevam
2023-05-19 13:24 ` Rob Herring
2023-05-19 15:45 ` Fabio Estevam
2023-05-19 19:23 ` Conor Dooley
2023-05-22 11:49 ` Fabio Estevam
2023-05-22 12:07 ` Conor Dooley
2023-05-19 12:52 ` [PATCH v4 3/4] ARM: dts: imx6sx: Add LDB support Fabio Estevam
2023-05-19 12:52 ` [PATCH v4 4/4] soc: imx: imx6sx-gpr: Introduce a GPR driver Fabio Estevam
2023-05-20 10:15 ` Conor Dooley [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=20230520-iphone-outreach-14f46c57b7cd@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marex@denx.de \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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