From: sashiko-bot@kernel.org
To: "Laurentiu Palcu" <laurentiu.palcu@oss.nxp.com>
Cc: linux-clk@vger.kernel.org, imx@lists.linux.dev,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
robh@kernel.org, conor+dt@kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH v11 5/7] dt-bindings: clock: nxp,imx95-blk-ctl: Add LDB bridge child node
Date: Tue, 10 Nov 2026 14:46:54 +0000 [thread overview]
Message-ID: <sashiko-outbox-207210@kernel.org> (raw)
In-Reply-To: <20261110-dcif-upstreaming-v11-5-9e13c85ae0d8@oss.nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] dt-bindings: clock: nxp,imx95-blk-ctl: split variant schemas
with subnodes
--
commit 40c5ccb540e5f895cb96974a17da3a21e1ed5c2d
Author: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>
dt-bindings: clock: nxp,imx95-blk-ctl: Add LDB bridge child node
This commit adds a bridge child node pattern to the nxp,imx95-blk-ctl
binding schema for nxp,imx94-lvds-csr to support LVDS Display Bridge
controllers.
> diff --git a/Documentation/devicetree/bindings/clock/nxp,imx95-blk-ctl.yaml b/Documentation/devicetree/bindings/clock/nxp,imx95-blk-ctl.yaml
> index fbbf1b3f17904..c2aeb434a8102 100644
> --- a/Documentation/devicetree/bindings/clock/nxp,imx95-blk-ctl.yaml
> +++ b/Documentation/devicetree/bindings/clock/nxp,imx95-blk-ctl.yaml
> @@ -51,6 +51,10 @@ patternProperties:
> $ref: /schemas/media/fsl,imx95-csi-formatter.yaml#
> unevaluatedProperties: false
>
> + '^bridge@[0-9a-f]+$':
> + type: object
> + $ref: /schemas/display/bridge/fsl,ldb.yaml#
> +
> required:
> - compatible
> - reg
> @@ -63,7 +67,9 @@ allOf:
> properties:
> compatible:
> contains:
> - const: nxp,imx95-camera-csr
> + enum:
> + - nxp,imx94-lvds-csr
> + - nxp,imx95-camera-csr
> then:
> required:
> - '#address-cells'
> @@ -72,8 +78,24 @@ allOf:
> properties:
> '#address-cells': false
> '#size-cells': false
> + - if:
> + properties:
> + compatible:
> + not:
> + contains:
> + const: nxp,imx95-camera-csr
> + then:
> patternProperties:
> '^formatter@[0-9a-f]+$': false
> + - if:
> + properties:
> + compatible:
> + not:
> + contains:
> + const: nxp,imx94-lvds-csr
> + then:
> + patternProperties:
> + '^bridge@[0-9a-f]+$': false
>
> additionalProperties: false
[Severity: Low]
This isn't a bug, but would it be cleaner to split CSR variants that have
subnodes (such as nxp,imx94-lvds-csr and nxp,imx95-camera-csr) into
separate binding schemas, similar to nxp,imx95-display-master-csr.yaml?
Adding a second variant-specific child node pattern to
nxp,imx95-blk-ctl.yaml requires three separate per-compatible if-then
blocks in allOf to toggle #address-cells, #size-cells, formatter@[0-9a-f]+,
and bridge@[0-9a-f]+ across unrelated CSR blocks.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261110-dcif-upstreaming-v11-0-9e13c85ae0d8@oss.nxp.com?part=5
next prev parent reply other threads:[~2026-11-10 14:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 14:27 [PATCH v11 0/7] Add support for i.MX94 DCIF Laurentiu Palcu
2026-11-10 14:27 ` [PATCH v11 1/7] dt-bindings: display: fsl,ldb: Add i.MX94 LDB Laurentiu Palcu
2026-11-10 14:27 ` [PATCH v11 2/7] drm/bridge: fsl-ldb: Add support for i.MX94 Laurentiu Palcu
2026-11-10 14:27 ` [PATCH v11 3/7] dt-bindings: display: imx: Add i.MX94 DCIF Laurentiu Palcu
2026-11-10 14:27 ` [PATCH v11 4/7] drm/imx: Add support for " Laurentiu Palcu
2026-11-10 15:14 ` sashiko-bot
2026-11-12 15:23 ` Luca Ceresoli
2026-11-10 14:27 ` [PATCH v11 5/7] dt-bindings: clock: nxp,imx95-blk-ctl: Add LDB bridge child node Laurentiu Palcu
2026-11-10 14:27 ` [PATCH v11 5/7] dt-bindings: clock: nxp, imx95-blk-ctl: " Laurentiu Palcu
2026-11-10 14:46 ` sashiko-bot [this message]
2026-11-10 20:07 ` [PATCH v11 5/7] dt-bindings: clock: nxp,imx95-blk-ctl: " Rob Herring (Arm)
2026-11-10 14:27 ` [PATCH v11 6/7] arm64: dts: imx94: Add display pipeline nodes Laurentiu Palcu
2026-11-10 14:27 ` [PATCH v11 7/7] arm64: dts: imx943-evk: Add display support using IT6263 Laurentiu Palcu
2026-11-12 16:40 ` (subset) [PATCH v11 0/7] Add support for i.MX94 DCIF Luca Ceresoli
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=sashiko-outbox-207210@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=imx@lists.linux.dev \
--cc=laurentiu.palcu@oss.nxp.com \
--cc=linux-clk@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.