From: "Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx5: add iomux-mx51.h include
Date: Fri, 17 Aug 2012 21:35:05 +0200 (CEST) [thread overview]
Message-ID: <163515253.2522936.1345232105380.JavaMail.root@advansee.com> (raw)
In-Reply-To: <CAKGA1bkEO_2TskWs2ZeV3s=UU19k+oqaOc33wh2_A7KGQhtDDg@mail.gmail.com>
Dear Matt Sealey,
> On Fri, Aug 17, 2012 at 1:42 PM, Beno?t Th?baudeau
> <benoit.thebaudeau@advansee.com> wrote:
> > Dear Matt Sealey,
> >
> > These pad settings are broken. All the pins of each peripheral
> > should not always
> > have the same pad settings. E.g., UART input pins should have their
> > pull-up
> > enabled in order to avoid spurious character input if these pins
> > are left
> > floating from time to time. The same applies to eCSPI.
>
> I'm not going to comment on the quality of the pad settings, but
> since
> MX51 arrived in any kernel these have been the pad settings for *all*
> MX51, MX53, MX6 boards and in the case of MX6 are applied in U-Boot
> right now for example on mx6qsabrelite if not the others too. These
> settings are in device trees now, too.
>
> If you want to "correct" years of reliable operation in U-Boot, go
> ahead, and fix Linux while you're at it. I'm just porting the status
> quo.
I'm just saying that from experience. I've already seen issues related to that
kind of things.
Best regards,
Beno?t
next prev parent reply other threads:[~2012-08-17 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 18:16 [U-Boot] [PATCH] mx5: add iomux-mx51.h include Matt Sealey
2012-08-17 18:42 ` Benoît Thébaudeau
2012-08-17 19:01 ` Matt Sealey
2012-08-17 19:35 ` Benoît Thébaudeau [this message]
2012-08-17 20:25 ` Matt Sealey
2012-08-18 15:18 ` Stefano Babic
2012-08-18 21:18 ` Matt Sealey
2012-08-18 21:46 ` Benoît Thébaudeau
2012-08-18 21:52 ` Matt Sealey
2012-08-20 14:43 ` Shawn Guo
2012-08-18 22:51 ` 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=163515253.2522936.1345232105380.JavaMail.root@advansee.com \
--to=benoit.thebaudeau@advansee.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.