From: Liu Ying <victor.liu@nxp.com>
To: sashiko-reviews@lists.linux.dev
Cc: conor+dt@kernel.org, robh@kernel.org, imx@lists.linux.dev,
krzk+dt@kernel.org, Frank.Li@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: soc: imx: fsl,imx93-media-blk-ctrl: Allow LVDS Display Bridge child node
Date: Thu, 14 May 2026 13:08:58 +0800 [thread overview]
Message-ID: <agVY6tynKIsaJ03D@raspi> (raw)
In-Reply-To: <20260514035156.A6874C2BCC7@smtp.kernel.org>
On Thu, May 14, 2026 at 03:51:55AM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] The `bridge@20` child node is allowed unconditionally for all hardware variants in the binding, even though the i.MX91 hardware lacks an LVDS Display Bridge (LDB).
> --
>
> commit 1215972eab31b33c83565fc6226eed3ff41fba34
> Author: Liu Ying <victor.liu@nxp.com>
>
> dt-bindings: soc: imx: fsl,imx93-media-blk-ctrl: Allow LVDS Display Bridge child node
>
> This commit allows the LVDS Display Bridge child node in the i.MX93 media
> blk-ctrl binding and adds it to the example. The LDB_CTRL and LVDS registers
> control video output through the LVDS interface.
>
> > diff --git a/Documentation/devicetree/bindings/soc/imx/fsl,imx93-media-blk-ctrl.yaml b/Documentation/devicetree/bindings/soc/imx/fsl,imx93-media-blk-ctrl.yaml
> > index d828c2e82965c..ab563b457e07a 100644
> > --- a/Documentation/devicetree/bindings/soc/imx/fsl,imx93-media-blk-ctrl.yaml
> > +++ b/Documentation/devicetree/bindings/soc/imx/fsl,imx93-media-blk-ctrl.yaml
>
> [ ... ]
>
> > @@ -92,6 +98,11 @@ properties:
> > - compatible
> > - ports
> >
> > + bridge@20:
> > + type: object
> > + $ref: /schemas/display/bridge/fsl,ldb.yaml#
> > + unevaluatedProperties: false
> > +
> > allOf:
> > - if:
> > properties:
>
> Since this binding is shared between fsl,imx91-media-blk-ctrl and
> fsl,imx93-media-blk-ctrl, does adding bridge@20 to the top-level properties
> unconditionally allow it for both variants?
>
> If the i.MX91 hardware lacks the LVDS Display Bridge, should this child node
> be explicitly disallowed by adding bridge@20: false to the allOf conditional
> block for the i.MX91 compatible string?
Yes, this should be disallowed for i.MX91.
>
> Without this restriction, device trees incorrectly instantiating the LDB on
> i.MX91 hardware might silently pass schema validation.
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260513-imx93-ldb-v1-0-d11c5c3cc197@nxp.com?part=1
--
Regards,
Liu Ying
next prev parent reply other threads:[~2026-05-14 5:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 10:02 [PATCH 0/3] arm64: dts: imx93-11x11-evk: Add DY1212W-4856 LVDS panel Liu Ying
2026-05-13 10:02 ` [PATCH 1/3] dt-bindings: soc: imx: fsl,imx93-media-blk-ctrl: Allow LVDS Display Bridge child node Liu Ying
2026-05-13 10:29 ` Marco Felsch
2026-05-14 3:51 ` sashiko-bot
2026-05-14 5:08 ` Liu Ying [this message]
2026-05-13 10:02 ` [PATCH 2/3] arm64: dts: imx93: Add LVDS Display Bridge support Liu Ying
2026-05-13 10:02 ` [PATCH 3/3] arm64: dts: imx93-11x11-evk: Add DY1212W-4856 LVDS panel Liu Ying
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=agVY6tynKIsaJ03D@raspi \
--to=victor.liu@nxp.com \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox