From: Marek Vasut <marex@denx.de>
To: Fabio Estevam <festevam@gmail.com>,
Fabio Estevam <fabio.estevam@nxp.com>
Cc: Stefan Agner <stefan@agner.ch>,
Sascha Hauer <kernel@pengutronix.de>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH v3] drm: mxsfb_crtc: Reset the eLCDIF controller
Date: Mon, 22 May 2017 16:20:12 +0200 [thread overview]
Message-ID: <eda79c17-4e58-fd57-40ff-48079cff75a3@denx.de> (raw)
In-Reply-To: <CAOMZO5C-YjQUrSBXPx+Ap1js-eJxoEmXDFc4K6eB66V7JYWOgA@mail.gmail.com>
On 05/22/2017 03:55 PM, Fabio Estevam wrote:
> Hi Marek,
>
> On Fri, May 5, 2017 at 3:01 PM, Fabio Estevam <fabio.estevam@nxp.com> wrote:
>> According to the eLCDIF initialization steps listed in the MX6SX
>> Reference Manual the eLCDIF block reset is mandatory.
>>
>> Without performing the eLCDIF reset the display shows garbage content
>> when the kernel boots.
>>
>> In earlier tests this issue has not been observed because the bootloader
>> was previously showing a splash screen and the bootloader display driver
>> does properly implement the eLCDIF reset.
>>
>> Add the eLCDIF reset to the driver, so that it can operate correctly
>> independently of the bootloader.
>>
>> Tested on a imx6sx-sdb board.
>>
>> Cc: <stable@vger.kernel.org>
>> Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
>> ---
>> Changes since v2:
>>
>> - Remove unneeded udelay(1) - Marek
>
> Any comments about v3?
>
IMO it's OK.
Reviewed-by: Marek Vasut <marex@denx.de>
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2017-05-22 14:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 18:01 [PATCH v3] drm: mxsfb_crtc: Reset the eLCDIF controller Fabio Estevam
2017-05-22 13:55 ` Fabio Estevam
2017-05-22 14:20 ` Marek Vasut [this message]
2017-05-22 18:52 ` Fabio Estevam
2017-05-22 20:33 ` Marek Vasut
2017-06-05 12:03 ` Fabio Estevam
2017-06-05 12:08 ` Marek Vasut
2017-06-15 15:12 ` Fabio Estevam
2017-06-15 17:26 ` Marek Vasut
2017-06-16 2:57 ` Stefan Agner
2017-06-16 8:29 ` Sanchayan Maity
2017-06-15 17:53 ` Sean Paul
2017-06-15 20:02 ` Sean Paul
2017-06-16 6:10 ` Marek Vasut
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=eda79c17-4e58-fd57-40ff-48079cff75a3@denx.de \
--to=marex@denx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=fabio.estevam@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=stable@vger.kernel.org \
--cc=stefan@agner.ch \
/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