From: sashiko-bot@kernel.org
To: "Francesco Dolcini" <francesco@dolcini.it>
Cc: devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
Frank.Li@kernel.org, robh@kernel.org, conor+dt@kernel.org,
imx@lists.linux.dev
Subject: Re: [PATCH v5 1/4] dt-bindings: lcdif: Add endpoint bus-width property
Date: Thu, 17 Sep 2026 14:14:06 +0000 [thread overview]
Message-ID: <20260917141406.E97B01F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260917140042.118181-2-francesco@dolcini.it>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: fsl,lcdif: endpoint constraints bypassed for unit-addressed endpoints
--
commit fb72496bb41dc4492a1048af127118bf41d36a4a
Author: Francesco Dolcini <francesco.dolcini@toradex.com>
dt-bindings: lcdif: Add endpoint bus-width property
The DPI output of the LCD interface can be configured with a bus width
of 16, 18, or 24 bits. Introduce a bus-width property to the output
endpoint, specifying the number of parallel RGB bits connected.
> diff --git a/Documentation/devicetree/bindings/display/fsl,lcdif.yaml b/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
> index 2dd0411ec6516..89cea0c14cf1d 100644
> --- a/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
> +++ b/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
> @@ -68,9 +68,19 @@ properties:
> maxItems: 1
>
> port:
> - $ref: /schemas/graph.yaml#/properties/port
> + $ref: /schemas/graph.yaml#/$defs/port-base
> + unevaluatedProperties: false
> description: The LCDIF output port
>
> + properties:
> + endpoint:
[Severity: Low]
Does restricting this to the literal 'endpoint' key bypass validation for
unit-addressed endpoints?
Existing in-tree device trees, such as arch/arm64/boot/dts/freescale/imx93.dtsi,
define unit-addressed endpoints under the lcdif port:
lcdif_to_ldb: endpoint@1 {
reg = <1>;
Because this uses the literal 'endpoint' key rather than a pattern property
like "^endpoint(@[0-9a-f]+)?$", multi-endpoint configurations will fail
to match this rule.
This causes device tree validation to silently bypass the bus-width enum
constraints and other video-interfaces.yaml rules for those configurations.
> + $ref: /schemas/media/video-interfaces.yaml
> + unevaluatedProperties: false
> +
> + properties:
> + bus-width:
> + enum: [ 16, 18, 24 ]
> +
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260917140042.118181-1-francesco@dolcini.it?part=1
next prev parent reply other threads:[~2026-09-17 14:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 14:00 [PATCH v5 0/4] drm: mxsfb: Support LCDIF interface bus width Francesco Dolcini
2026-09-17 14:00 ` [PATCH v5 1/4] dt-bindings: lcdif: Add endpoint bus-width property Francesco Dolcini
2026-09-17 14:14 ` sashiko-bot [this message]
2026-09-17 14:00 ` [PATCH v5 2/4] drm: mxsfb: Add optional DPI output bus-width configuration Francesco Dolcini
2026-09-17 14:24 ` Frank Li
2026-09-17 15:31 ` Luca Ceresoli
2026-09-17 14:00 ` [PATCH v5 3/4] ARM: dts: imx6ull-colibri: Set LCDIF bus width Francesco Dolcini
2026-09-17 14:00 ` [PATCH v5 4/4] ARM: dts: imx7-colibri: " Francesco Dolcini
2026-09-28 11:40 ` [PATCH v5 0/4] drm: mxsfb: Support LCDIF interface " Francesco Dolcini
2026-09-30 10:43 ` (subset) " Luca Ceresoli
2026-09-30 15:45 ` Frank.Li
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=20260917141406.E97B01F000FF@smtp.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=francesco@dolcini.it \
--cc=imx@lists.linux.dev \
--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