All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Francesco Dolcini" <francesco@dolcini.it>
Cc: robh@kernel.org, devicetree@vger.kernel.org, Frank.Li@kernel.org,
	imx@lists.linux.dev, dri-devel@lists.freedesktop.org,
	conor+dt@kernel.org
Subject: Re: [PATCH v3 1/4] dt-bindings: lcdif: Add endpoint bus-width property
Date: Wed, 12 Aug 2026 13:39:40 +0000	[thread overview]
Message-ID: <20260812133941.1AF9A1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260812132954.148571-2-francesco@dolcini.it>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The device tree schema uses exact string matching (`properties: endpoint`) instead of pattern matching (`patternProperties`), failing to validate indexed endpoints with unit addresses (e.g., `endpoint@0`) and silently bypassing constraints for `bus-width`.
--

--- Patch [1]: [PATCH v3 1/4] dt-bindings: lcdif: Add endpoint bus-width property ---
commit 875819bc127ee9201c1b4dcfb35262deed8eb282
Author: Francesco Dolcini <francesco.dolcini@toradex.com>

dt-bindings: lcdif: Add endpoint bus-width property

This commit introduces a bus-width property to the output endpoint of the
LCDIF display binding. It allows configuring the DPI output with a bus
width of 16, 18, or 24 bits.

> diff --git a/Documentation/devicetree/bindings/display/fsl,lcdif.yaml b/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
> index 2dd0411ec6516..1f3daf0027075 100644
> --- a/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
> +++ b/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
> @@ -71,6 +71,15 @@ properties:
>      $ref: /schemas/graph.yaml#/properties/port
>      description: The LCDIF output port
>  
> +    properties:
> +      endpoint:

[Severity: Medium]
Will this exact string match cause validation to be skipped for indexed
endpoints?

If a device tree defines an endpoint with a unit address under the port node,
such as endpoint@0 or endpoint@1, the exact match on endpoint bypasses
validation of the constraints inside this block. As a result, incorrect
bus-width values on indexed endpoints would silently pass validation.

Does this need to use patternProperties to correctly match both standard and
indexed endpoints?

> +        $ref: /schemas/media/video-interfaces.yaml
> +        unevaluatedProperties: false
> +
> +        properties:
> +          bus-width:
> +            enum: [ 16, 18, 24 ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260812132954.148571-1-francesco@dolcini.it?part=1

  reply	other threads:[~2026-08-12 13:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12 13:29 [PATCH v3 0/4] drm: mxsfb: Support LCDIF interface bus width Francesco Dolcini
2026-08-12 13:29 ` [PATCH v3 1/4] dt-bindings: lcdif: Add endpoint bus-width property Francesco Dolcini
2026-08-12 13:39   ` sashiko-bot [this message]
2026-08-12 14:18   ` Frank Li
2026-08-12 13:29 ` [PATCH v3 2/4] drm: mxsfb: Add optional DPI output bus-width configuration Francesco Dolcini
2026-08-12 14:20   ` Frank Li
2026-08-12 15:02   ` Marco Felsch
2026-08-12 15:07     ` Francesco Dolcini
2026-08-12 13:29 ` [PATCH v3 3/4] ARM: dts: imx6ull-colibri: Set LCDIF bus-width Francesco Dolcini
2026-08-12 13:29 ` [PATCH v3 4/4] ARM: dts: imx7-colibri: " Francesco Dolcini

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=20260812133941.1AF9A1F000E9@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 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.