[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5CqWRqg0YhyNKj0MW807i=kVahSDpVXibp3oDj7D91z4w@mail.gmail.com>
Date: Mon, 23 Sep 2024 09:03:08 -0300
From: Fabio Estevam <festevam@...il.com>
To: Lukasz Majewski <lukma@...x.de>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>, Pengutronix Kernel Team <kernel@...gutronix.de>,
devicetree@...r.kernel.org, imx@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 2/2] dts: nxp: mxs: Add descriptions for imx287 based
btt3-[012] devices
Hi Lukasz,
On Mon, Sep 23, 2024 at 6:47 AM Lukasz Majewski <lukma@...x.de> wrote:
> 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"
Yes, that would be a good solution, thanks.
Powered by blists - more mailing lists