dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Wojciech Dubowik" <wojciech.dubowik@mt.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] dt-bindings: display: sn65dsi83: Add reverse lanes property
Date: Tue, 07 Jul 2026 07:45:00 +0000	[thread overview]
Message-ID: <20260707074500.CAF1B1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260707070244.230546-2-wojciech.dubowik@mt.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The patch introduces a custom vendor-specific boolean property `ti,lvds-reverse-lanes` to indicate LVDS lane reversal. This is a device tree anti-pattern because the referenced standard `video-interfaces.yaml` already provides the `data-lanes` property for this exact purpose (e.g., `data-lanes = <4 3 2 1>;`).
--

--- Patch [1]: [PATCH 1/2] dt-bindings: display: sn65dsi83: Add reverse lanes property ---
commit c30eea01a74188461b7e527f71d282d68b885ec2
Author: Wojciech Dubowik <Wojciech.Dubowik@mt.com>

dt-bindings: display: sn65dsi83: Add reverse lanes property

This patch adds a boolean property to reverse the LVDS data lanes order for
endpoints.

> diff --git a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml
> --- a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml
> +++ b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml
[ ... ]
> @@ -115,6 +115,10 @@ $defs:
>              enum: [100, 200]
>              default: 200
>  
> +          ti,lvds-reverse-lanes:
> +            description: Reverse the order of LVDS lanes.
> +            type: boolean

[Severity: Low]
Is it necessary to introduce a custom vendor-specific boolean property
for this?

Since video-interfaces.yaml already provides the standard data-lanes property
which can be used to describe the exact lane routing, does this hardware
require a distinct property instead of using the standard data-lanes
approach with data-lanes = <4 3 2 1>?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260707070244.230546-1-wojciech.dubowik@mt.com?part=1

  reply	other threads:[~2026-07-07  7:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07  7:02 [PATCH 0/2] drm/bridge: ti-sn65dsi83: Add reverse lvds lanes DT property Wojciech Dubowik
2026-07-07  7:02 ` [PATCH 1/2] dt-bindings: display: sn65dsi83: Add reverse lanes property Wojciech Dubowik
2026-07-07  7:45   ` sashiko-bot [this message]
2026-07-07 16:21     ` Conor Dooley
2026-07-08 10:56       ` Wojciech Dubowik
2026-07-09  8:33   ` Alexander Stein
2026-07-09  9:17     ` Laurent Pinchart
2026-07-09 12:57       ` Wojciech Dubowik
2026-07-07  7:02 ` [PATCH 2/2] drm/bridge: ti-sn65dsi83: Add reverse lvds " Wojciech Dubowik

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=20260707074500.CAF1B1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=robh@kernel.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