devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: Fabio Estevam <festevam@gmail.com>, Rob Herring <robh@kernel.org>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	devicetree@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/2] dts: nxp: mxs: Add descriptions for imx287 based btt3-[012] devices
Date: Mon, 23 Sep 2024 11:47:11 +0200	[thread overview]
Message-ID: <20240923114711.1c294b6b@wsk> (raw)
In-Reply-To: <CAOMZO5DJ4=ARZEcq+vbisA4kJBg+WFkH3G8-hYDkL82GQBEPBw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2493 bytes --]

Hi Fabio,

> Hi Lukasz,
> 
> On Thu, Sep 12, 2024 at 9:48 AM Lukasz Majewski <lukma@denx.de> wrote:
> 
> > +&lcdif {
> > +       pinctrl-names = "default";
> > +       pinctrl-0 = <&lcdif_24bit_pins_a>, <&lcdif_sync_pins_bttc>,
> > +                   <&lcdif_reset_pins_bttc>;
> > +       lcd-supply = <&reg_3v3>;
> > +       display = <&display0>;
> > +       status = "okay";
> > +       display0: display0 {
> > +               bits-per-pixel = <32>;
> > +               bus-width = <24>;
> > +               display-timings {
> > +                       native-mode = <&timing0>;
> > +                       timing0: timing0 {
> > +                               clock-frequency = <6500000>;
> > +                               hactive = <320>;
> > +                               vactive = <240>;
> > +                               hfront-porch = <20>;
> > +                               hback-porch = <38>;
> > +                               hsync-len = <30>;
> > +                               vfront-porch = <4>;
> > +                               vback-porch = <14>;
> > +                               vsync-len = <4>;
> > +                               hsync-active = <0>;
> > +                               vsync-active = <0>;
> > +                               de-active = <0>;
> > +                               pixelclk-active = <1>;  
> 
> According to fsl,lcdif.yaml, a remote-endpoint to the display is
> needed.
> 
> See imx28-evk.dts for an example.

This file has the:
	panel {
		compatible = "sii,43wvf1g";

Whereas in those devices (i.e. btt3) - I don't know the names of the
displays - manufacturer buys them according to the timing properties.

Hence the question - how shall I proceed?

IMHO the most straightforward way is to modify fsl,lcdif.yaml to
not require "port" and "remote-endpoint" and instead add support for
"display-timings" and "timingX"

Especially that
Documentation/devicetree/bindings/display/panel/display-timings.yaml

are already defined and used by many imx boards (from imx25 to imx6q)
- git grep -n "display-timings"

Even the imx28-m28evk.dts is using the "display-timings" and not
"remote-endpoint" approach.


Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-09-23  9:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 12:48 [PATCH v6 1/2] dt-bindings: arm: Document the btt3 i.MX28 based board Lukasz Majewski
2024-09-12 12:48 ` [PATCH v6 2/2] dts: nxp: mxs: Add descriptions for imx287 based btt3-[012] devices Lukasz Majewski
2024-09-12 12:58   ` Fabio Estevam
2024-09-23  9:47     ` Lukasz Majewski [this message]
2024-09-23 12:03       ` Fabio Estevam
2024-09-13 12:36   ` Stefan Wahren
2024-10-08 11:41     ` Lukasz Majewski
2024-10-08 15:53       ` Stefan Wahren
2024-10-09  8:59         ` Lukasz Majewski
2024-09-12 17:57 ` [PATCH v6 1/2] dt-bindings: arm: Document the btt3 i.MX28 based board Conor Dooley

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=20240923114711.1c294b6b@wsk \
    --to=lukma@denx.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).