Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: Frank Li <Frank.li@oss.nxp.com>,
	sashiko-reviews@lists.linux.dev, devicetree@vger.kernel.org,
	dri-devel@lists.freedesktop.org, Frank.Li@kernel.org,
	conor+dt@kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH v1 1/4] dt-bindings: lcdif: Add interface pixel format
Date: Wed, 22 Jul 2026 14:30:44 -0500	[thread overview]
Message-ID: <20260722193044.GA1489843-robh@kernel.org> (raw)
In-Reply-To: <20260717211344.GC512678@francesco-nb>

On Fri, Jul 17, 2026 at 11:13:44PM +0200, Francesco Dolcini wrote:
> On Fri, Jul 17, 2026 at 10:57:54PM +0200, Francesco Dolcini wrote:
> > On Fri, Jul 17, 2026 at 10:55:51AM -0500, Frank Li wrote:
> > > On Fri, Jul 17, 2026 at 12:28:07PM +0000, sashiko-bot@kernel.org wrote:
> > > > Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> > > > - [Low] Introduction of the legacy, non-standard `interface-pix-fmt` property for a standard hardware concept (parallel bus width), violating modern DT principles.
> > > > --
> > > >
> > > > --- Patch [1]: [PATCH v1 1/4] dt-bindings: lcdif: Add interface pixel format ---
> > > > commit 7225ea545d2ff50540972dd75d375b8ecea4f315
> > > > Author: Francesco Dolcini <francesco.dolcini@toradex.com>
> > > >
> > > > dt-bindings: lcdif: Add interface pixel format
> > > >
> > > > This commit updates the fsl,lcdif device tree binding to support the
> > > > interface-pix-fmt property. The property is used to describe the hardware's
> > > > parallel data bus transfer width to match board wiring and prevent shifted
> > > > colors.
> > > >
> > > > > diff --git a/Documentation/devicetree/bindings/display/fsl,lcdif.yaml b/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
> > > > > index 2dd0411ec6516..209ee5a96e393 100644
> > > > > --- a/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
> > > > > +++ b/Documentation/devicetree/bindings/display/fsl,lcdif.yaml
> > > > > @@ -58,6 +58,13 @@ properties:
> > > > >      items:
> > > > >        - const: rx
> > > > >
> > > > > +  interface-pix-fmt:
> > > > > +    $ref: /schemas/types.yaml#/definitions/string
> > > > > +    enum:
> > > > > +      - rgb24
> > > > > +      - rgb565
> > > > > +      - rgb666
> > > >
> > > > [Severity: Low]
> > > > Is this introducing a legacy, non-standard property into the new schema ABI?
> > > >
> > > > Standard devicetree guidelines usually prefer endpoint properties like
> > > > bus-width (defined in video-interfaces.yaml) to describe physical parallel
> > > > data line configurations, such as setting bus-width = <18> for RGB666.
> > > 
> > > Make sense, can we use standard property?
> > 
> > video-interfaces.yaml is for video capture interfaces (cameras and the
> > media/v4l subsystem). It does not apply here for DPI display interfaces.
> 
> ok, looking at this closer, it seems this is a used property also in the
> DRM subsystem. I'll appreciate a feedback from some DT maintainer before
> reworking this patch accordingly.

I reject any custom properties for describing the format of the parallel 
interface. 

Rob

  reply	other threads:[~2026-07-22 19:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-17 12:18 [PATCH v1 0/4] drm: mxsfb: Support LCDIF interface pixel format Francesco Dolcini
2026-07-17 12:18 ` [PATCH v1 1/4] dt-bindings: lcdif: Add " Francesco Dolcini
2026-07-17 12:28   ` sashiko-bot
2026-07-17 15:55     ` Frank Li
2026-07-17 20:57       ` Francesco Dolcini
2026-07-17 21:13         ` Francesco Dolcini
2026-07-22 19:30           ` Rob Herring [this message]
2026-07-22 19:46             ` Francesco Dolcini
2026-07-17 12:18 ` [PATCH v1 2/4] drm: mxsfb: Allow optional LCDIF interface format override Francesco Dolcini
2026-07-21  8:52   ` Marco Felsch
2026-07-21  9:35     ` Francesco Dolcini
2026-07-21  9:03   ` Alexander Stein
2026-07-17 12:18 ` [PATCH v1 3/4] ARM: dts: imx6ull-colibri: Set LCDIF format Francesco Dolcini
2026-07-17 12:18 ` [PATCH v1 4/4] ARM: dts: imx7-colibri: " Francesco Dolcini
2026-07-17 12:30   ` 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=20260722193044.GA1489843-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=Frank.li@oss.nxp.com \
    --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=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