* [U-Boot] i.MX6DL/S regression in mx6dl_pins.h
@ 2013-09-12 21:56 Eric Nelson
2013-09-12 23:15 ` Fabio Estevam
2013-09-13 5:38 ` Pierre AUBERT
0 siblings, 2 replies; 3+ messages in thread
From: Eric Nelson @ 2013-09-12 21:56 UTC (permalink / raw)
To: u-boot
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* [U-Boot] i.MX6DL/S regression in mx6dl_pins.h
2013-09-12 21:56 [U-Boot] i.MX6DL/S regression in mx6dl_pins.h Eric Nelson
@ 2013-09-12 23:15 ` Fabio Estevam
2013-09-13 5:38 ` Pierre AUBERT
1 sibling, 0 replies; 3+ messages in thread
From: Fabio Estevam @ 2013-09-12 23:15 UTC (permalink / raw)
To: u-boot
Hi Eric,
On Thu, Sep 12, 2013 at 6:56 PM, Eric Nelson
<eric.nelson@boundarydevices.com> wrote:
> 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.
Yes, please send a patch for this when you have a chance.
Thanks,
Fabio Estevam
^ permalink raw reply [flat|nested] 3+ messages in thread
* [U-Boot] i.MX6DL/S regression in mx6dl_pins.h
2013-09-12 21:56 [U-Boot] i.MX6DL/S regression in mx6dl_pins.h Eric Nelson
2013-09-12 23:15 ` Fabio Estevam
@ 2013-09-13 5:38 ` Pierre AUBERT
1 sibling, 0 replies; 3+ messages in thread
From: Pierre AUBERT @ 2013-09-13 5:38 UTC (permalink / raw)
To: u-boot
Hello Eric,
Le 12/09/2013 23:56, Eric Nelson a ?crit :
> 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
You're right, it was a mistake for these two pads.
>
> 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
Best regards
Pierre
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-09-13 5:38 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-09-12 21:56 [U-Boot] i.MX6DL/S regression in mx6dl_pins.h Eric Nelson
2013-09-12 23:15 ` Fabio Estevam
2013-09-13 5:38 ` Pierre AUBERT
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox