From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] i.MX6DL/S: add drive-strength back to pads DISP0_DAT2/DAT10
Date: Thu, 10 Jul 2014 15:20:03 +0200 [thread overview]
Message-ID: <53BE9303.3070903@denx.de> (raw)
In-Reply-To: <CAP9ODKouimrG1-0opW-WnLYkUKW7LEzvmLnq5BN-HHp=7Bupwg@mail.gmail.com>
Hi Eric, hi Otavio,
On 09/07/2014 21:40, Otavio Salvador wrote:
> On Wed, Jul 9, 2014 at 4:27 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> The pad settings for DISP0_DATA02 and DISP0_DAT10 were not
>> set in the same way as DISP0_DAT00-23, causing much flicker
>> in parallel RGB displays on Dual-Lite and Solo processors.
>>
>> These settings now match the i.MX6 Dual and Quad core versions.
>>
>> Note that this fixes a regression in commit b47abc3 and that
>> this is the second time we've had a regression on these two
>> pads (See commit e654ddf).
>>
>> Signed-off-by: Eric Nelson <eric.nelson@boundarydevices.com>
>
> Acked-by: Otavio Salvador <otavio@ossystems.com.br>
>
> Stephano, can it be included in the upcoming release?
I will try: I merge it and I send a PR to Tom, as I did yesterday.
Regards,
Stefano
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2014-07-10 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 19:27 [U-Boot] [PATCH] i.MX6DL/S: add drive-strength back to pads DISP0_DAT2/DAT10 Eric Nelson
2014-07-09 19:40 ` Otavio Salvador
2014-07-10 13:20 ` Stefano Babic [this message]
2014-07-10 13:31 ` Eric Nelson
-- strict thread matches above, loose matches on Subject: below --
2013-09-13 16:19 Eric Nelson
2013-09-13 20:41 ` Otavio Salvador
2013-09-20 16:09 ` Stefano Babic
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=53BE9303.3070903@denx.de \
--to=sbabic@denx.de \
--cc=u-boot@lists.denx.de \
/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