public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: "Sébastien Szymanski" <sebastien.szymanski@armadeus.com>,
	u-boot@lists.denx.de, "Stefano Babic" <sbabic@denx.de>,
	"NXP i . MX U-Boot Team" <uboot-imx@nxp.com>,
	"Anatolij Gustschin" <agust@denx.de>
Subject: Re: [PATCH 1/2] opos6uldev: make the LCD work again
Date: Mon, 4 Mar 2024 08:34:58 -0500	[thread overview]
Message-ID: <20240304133458.GE1523872@bill-the-cat> (raw)
In-Reply-To: <CAOMZO5CBY4+CogKi767RVvT0F89Kpp6Hb9p1o7cw8jRE9PwUuA@mail.gmail.com>

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

On Mon, Mar 04, 2024 at 10:04:28AM -0300, Fabio Estevam wrote:
> Hi Tom,
> 
> On Tue, Feb 27, 2024 at 12:42 PM Tom Rini <trini@konsulko.com> wrote:
> 
> > What's the long term fix here? Why aren't these needed in Linux anymore,
> > and perhaps why was it OK to remove them? This is perhaps another case
> > where we as the U-Boot community need to go and talk with some Linux
> > Kernel community people. Thanks.
> 
> To fix the issue for 2024.04 I suggest that this series gets applied.
> 
> In the long term, I suggest Sébastien send a patch to the Linux DT to
> add back the panel timings.
> 
> Do you agree? If so, I can apply it to u-boot-imx master.

For v2024.04 yes, this is fine. For long term, we should parse the new
timing properties that the simple panel driver takes in our simple panel
driver instead.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2024-03-04 13:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27 15:40 [PATCH 1/2] opos6uldev: make the LCD work again Sébastien Szymanski
2024-02-27 15:40 ` [PATCH 2/2] video: mxsfb: add back imx6ul/imx6ull support Sébastien Szymanski
2024-02-27 15:42 ` [PATCH 1/2] opos6uldev: make the LCD work again Tom Rini
2024-03-04 13:04   ` Fabio Estevam
2024-03-04 13:34     ` Tom Rini [this message]
2024-03-04 13:36       ` Fabio Estevam
2024-02-28  7:09 ` Dan Carpenter
2024-02-28 13:10   ` Tom Rini
2024-02-28 14:14     ` Sumit Garg
2024-02-28 15:20       ` Tom Rini
2024-02-29  5:47         ` Sumit Garg
2024-02-29 13:42           ` Tom Rini
2024-02-29 14:01             ` Tom Rini
2024-03-01  6:02               ` Sumit Garg
2024-03-01  9:17                 ` Sébastien Szymanski
2024-03-01 13:32                   ` Conor Dooley
2024-03-01 18:54                     ` Tom Rini
2024-03-08 13:21                       ` Conor Dooley
2024-03-08 19:35                         ` Tom Rini
2024-03-01 18:54                   ` Tom Rini
2024-03-04 17:55 ` Fabio Estevam

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=20240304133458.GE1523872@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=agust@denx.de \
    --cc=festevam@gmail.com \
    --cc=sbabic@denx.de \
    --cc=sebastien.szymanski@armadeus.com \
    --cc=u-boot@lists.denx.de \
    --cc=uboot-imx@nxp.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