From: Tom Rini <trini@konsulko.com>
To: "Sébastien Szymanski" <sebastien.szymanski@armadeus.com>
Cc: u-boot@lists.denx.de, Stefano Babic <sbabic@denx.de>,
Fabio Estevam <festevam@gmail.com>,
"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: Tue, 27 Feb 2024 10:42:34 -0500 [thread overview]
Message-ID: <20240227154234.GK3040305@bill-the-cat> (raw)
In-Reply-To: <20240227154002.30257-1-sebastien.szymanski@armadeus.com>
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
On Tue, Feb 27, 2024 at 04:40:01PM +0100, Sébastien Szymanski wrote:
> Commit 5d7a95f49999 ("imx6ul/imx6ull: synchronise device trees with
> linux") removed the display timings from the board device tree whereas
> they are still needed by the mxsfb driver.
> Add the timings back (the correct ones) in the
> imx6ul-opos6uldev-u-boot.dtsi file and remove them from the
> opos6uldev.env file.
>
> Update the opos6uldev_defconfig file so that the LCD turns on at boot.
>
> Fixes: 5d7a95f49999 ("imx6ul/imx6ull: synchronise device trees with linux")
> Signed-off-by: Sébastien Szymanski <sebastien.szymanski@armadeus.com>
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.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-02-27 15:42 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 ` Tom Rini [this message]
2024-03-04 13:04 ` [PATCH 1/2] opos6uldev: make the LCD work again Fabio Estevam
2024-03-04 13:34 ` Tom Rini
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=20240227154234.GK3040305@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