All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wojciech Dubowik <wojciech.dubowik@mt.com>
To: Conor Dooley <conor@kernel.org>
Cc: sashiko-reviews@lists.linux.dev, 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: Wed, 8 Jul 2026 12:56:51 +0200	[thread overview]
Message-ID: <ak4s828nftsdeKx2@mt.com> (raw)
In-Reply-To: <20260707-aching-clutch-a71a6492cde2@spud>

On Tue, Jul 07, 2026 at 05:21:19PM +0100, Conor Dooley wrote:
Hi Conor,

> On Tue, Jul 07, 2026 at 07:45:00AM +0000, sashiko-bot@kernel.org wrote:
> > 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>?
> 
> I don't know much about display devices, but this seems like a
> reasonable thing to me. Why would it not work?

It makes perfectly sense. I am working on it already and will send soon V2.



  reply	other threads:[~2026-07-08 10:57 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
2026-07-07 16:21     ` Conor Dooley
2026-07-08 10:56       ` Wojciech Dubowik [this message]
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=ak4s828nftsdeKx2@mt.com \
    --to=wojciech.dubowik@mt.com \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.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.