All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>,
	Frank.Li@kernel.org, imx@lists.linux.dev, robh@kernel.org,
	devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
	conor+dt@kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH v10 6/9] dt-bindings: clock: nxp,imx95-blk-ctl: Add ldb child node
Date: Wed, 7 Oct 2026 14:11:27 +0100	[thread overview]
Message-ID: <20261007-e9f7f08f98c153f0d0c97c91@squawk> (raw)
In-Reply-To: <20261006123500.94C911F00893@smtp.kernel.org>

[-- Attachment #1: Type: text/plain, Size: 2787 bytes --]

On Tue, Oct 06, 2026 at 12:34:59PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] dt-bindings: missing LDB constraints for nxp,imx95-lvds-csr variant
> --
> 
> commit ef256d56e7840a3d6a825d4ac33adad77eacd513
> Author: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>
> 
> dt-bindings: clock: nxp,imx95-blk-ctl: Add ldb child node
> 
> Since the BLK CTL registers, like the LVDS CSR, can be used to control the
> LVDS Display Bridge controllers, add 'ldb' child node to handle
> these use cases.
> 
> > diff --git a/Documentation/devicetree/bindings/clock/nxp,imx95-blk-ctl.yaml b/Documentation/devicetree/bindings/clock/nxp,imx95-blk-ctl.yaml
> > index fbbf1b3f17904..97fe816a38f94 100644
> > --- a/Documentation/devicetree/bindings/clock/nxp,imx95-blk-ctl.yaml
> > +++ b/Documentation/devicetree/bindings/clock/nxp,imx95-blk-ctl.yaml
> [ ... ]
> > @@ -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'
> 
> [Severity: Medium]
> Could this introduce a regression where device tree validation incorrectly fails
> for i.MX95 devices that define an ldb child node under the LVDS CSR?

This ldb child is new, how could there be a regression like this?

> 
> This change restricts #address-cells and #size-cells to these two strings,
> forcing them to false for nxp,imx95-lvds-csr. Should nxp,imx95-lvds-csr also
> be included in this enum?
> 
> [ ... ]
> > @@ -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:
> > +        '^ldb@[0-9a-f]+$': false
> 
> [Severity: Medium]
> Does this introduce a regression by preventing nxp,imx95-lvds-csr from
> declaring an ldb child node?
> 
> This explicitly forbids the ldb child node for anything other than
> nxp,imx94-lvds-csr, thereby silently prohibiting it for nxp,imx95-lvds-csr.
> 
> -- 
> Sashiko AI review · https://sashiko.dev/#/patchset/20261006-dcif-upstreaming-v10-0-bcfb28de0aae@oss.nxp.com?part=6

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-10-07 13:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06 12:21 [PATCH v10 0/9] Add support for i.MX94 DCIF Laurentiu Palcu
2026-10-06 12:21 ` [PATCH v10 1/9] dt-bindings: display: fsl,ldb: Add i.MX94 LDB Laurentiu Palcu
2026-10-06 12:21 ` [PATCH v10 2/9] drm/bridge: fsl-ldb: Get the next non-panel bridge Laurentiu Palcu
2026-10-06 12:30   ` sashiko-bot
2026-10-06 12:21 ` [PATCH v10 3/9] drm/bridge: fsl-ldb: Add support for i.MX94 Laurentiu Palcu
2026-10-06 12:21 ` [PATCH v10 4/9] dt-bindings: display: imx: Add i.MX94 DCIF Laurentiu Palcu
2026-10-06 12:22 ` [PATCH v10 5/9] drm/imx: Add support for " Laurentiu Palcu
2026-10-06 12:39   ` sashiko-bot
2026-10-12 11:18   ` Uwe Kleine-König
2026-10-06 12:22 ` [PATCH v10 6/9] dt-bindings: clock: nxp,imx95-blk-ctl: Add ldb child node Laurentiu Palcu
2026-10-06 12:22   ` [PATCH v10 6/9] dt-bindings: clock: nxp, imx95-blk-ctl: " Laurentiu Palcu
2026-10-06 12:34   ` [PATCH v10 6/9] dt-bindings: clock: nxp,imx95-blk-ctl: " sashiko-bot
2026-10-07 13:11     ` Conor Dooley [this message]
2026-10-07 13:12   ` Conor Dooley
2026-10-07 13:57     ` Laurentiu Palcu
2026-10-07 14:02       ` Conor Dooley
2026-10-06 12:22 ` [PATCH v10 7/9] arm64: dts: imx94: Add display pipeline nodes Laurentiu Palcu
2026-10-06 12:22 ` [PATCH v10 8/9] arm64: dts: imx943-evk: Add display support using IT6263 Laurentiu Palcu
2026-10-06 12:22 ` [PATCH v10 9/9] MAINTAINERS: Add entry for i.MX94 DCIF driver Laurentiu Palcu

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=20261007-e9f7f08f98c153f0d0c97c91@squawk \
    --to=conor@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.