From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] i.MX6DL/S regression in mx6dl_pins.h
Date: Thu, 12 Sep 2013 14:56:48 -0700 [thread overview]
Message-ID: <523238A0.8080008@boundarydevices.com> (raw)
Hi all,
It seems to be all about displays and mux/pad registers for
me these days.
I just tracked down an issue related to commit 87d720e0c that
causes improper display on our RGB displays.
In particular, the pad settings for these two registers lost
their drive-strength value:
MX6_PAD_DISP0_DAT2__IPU1_DISP0_DAT_2
MX6_PAD_DISP0_DAT10__IPU1_DISP0_DAT_10
I could make the case that things like pad drive strength
are a board-level tuning function, and belong in board-specific
files, but I think all RGB displays used with i.MX6 need
these values (and they should probably match the 6DQ).
Let me know if you'd like me to send a patch for this.
I have some other notes regarding consolidation of 6DQ and
6DLS that I'll send separately.
Regards,
Eric
next reply other threads:[~2013-09-12 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 21:56 Eric Nelson [this message]
2013-09-12 23:15 ` [U-Boot] i.MX6DL/S regression in mx6dl_pins.h Fabio Estevam
2013-09-13 5:38 ` Pierre AUBERT
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=523238A0.8080008@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--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