Devicetree
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: Wojciech Dubowik <wojciech.dubowik@mt.com>,
	conor+dt@kernel.org, dri-devel@lists.freedesktop.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v6 2/3] dt-bindings: display: sn65dsi83: Add output data-lanes property
Date: Tue, 21 Jul 2026 09:50:24 -0500	[thread overview]
Message-ID: <20260721145024.GA3790672-robh@kernel.org> (raw)
In-Reply-To: <20260721072022.52FFA1F00A3A@smtp.kernel.org>

On Tue, Jul 21, 2026 at 07:20:21AM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] Redefining `endpoint` in `port@2` and `port@3` with `unevaluatedProperties: false` unconditionally rejects valid vendor-specific properties (`ti,lvds-*`), breaking schema validation.
> --
> 
> --- Patch [2]: [PATCH v6 2/3] dt-bindings: display: sn65dsi83: Add output data-lanes property ---
> commit c8014187b83b236fe065488764ddd649223ae575
> Author: Wojciech Dubowik <Wojciech.Dubowik@mt.com>
> dt-bindings: display: sn65dsi83: Add output data-lanes property
> 
> Adds an optional output lvds data lanes property with two allowed values
> for standard and reversed layouts, informing the driver if the reverse
> lvds config option needs to be set.
> 
> > diff --git a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml
> > index e69b6343a8ebb..4000bf0b13709 100644
> > --- a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml
> > +++ b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml
> > @@ -86,10 +86,54 @@ properties:
> >          description: Video port for LVDS Channel-A output (panel or bridge).
> >          $ref: '#/$defs/lvds-port'
> >  
> > +        properties:
> > +          endpoint:
> > +            $ref: /schemas/media/video-interfaces.yaml#
> > +            unevaluatedProperties: false
> 
> [Severity: Medium]
> Does this local redefinition of endpoint with unevaluatedProperties: false 
> unconditionally reject valid vendor-specific properties (like ti,lvds-*) 
> and break schema validation? 
> 
> In JSON Schema, unevaluatedProperties only considers properties evaluated 
> within its own local evaluation path, so it won't see properties evaluated 
> by the parallel $ref: '#/$defs/lvds-port'.

sashiko is right here.

Rob

  reply	other threads:[~2026-07-21 14:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21  7:12 [PATCH v6 0/3] drm/bridge: ti-sn65dsi83: Add reverse lvds lanes support Wojciech Dubowik
2026-07-21  7:12 ` [PATCH v6 1/3] drm/bridge: ti-sn65dsi83: Simplify error condition logic Wojciech Dubowik
2026-07-21  7:12 ` [PATCH v6 2/3] dt-bindings: display: sn65dsi83: Add output data-lanes property Wojciech Dubowik
2026-07-21  7:20   ` sashiko-bot
2026-07-21 14:50     ` Rob Herring [this message]
2026-07-21  7:27   ` Krzysztof Kozlowski
2026-07-21 14:55     ` Rob Herring
2026-07-21  7:12 ` [PATCH v6 3/3] drm/bridge: ti-sn65dsi83: Add reversed lvds lanes support Wojciech Dubowik
2026-07-21  7:21   ` sashiko-bot

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=20260721145024.GA3790672-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=wojciech.dubowik@mt.com \
    /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