From: "Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx51evk: Add CONFIG_REVISION_TAG
Date: Tue, 18 Sep 2012 18:01:02 +0200 (CEST) [thread overview]
Message-ID: <1211243740.4667119.1347984062746.JavaMail.root@advansee.com> (raw)
In-Reply-To: <CAOMZO5CHfY99mTVhmqXwomjoyEj_HkzuDbR8qW0gyGJqqnK7aA@mail.gmail.com>
Fabio,
On Tuesday, September 18, 2012 5:24:57 AM, Fabio Estevam wrote:
> Hi Beno?t ,
>
> On Mon, Sep 17, 2012 at 4:04 PM, Beno?t Th?baudeau
> <benoit.thebaudeau@advansee.com> wrote:
>
> > +u32 get_board_rev(void)
> > +{
> > + return get_cpu_rev();
> > +}
>
> Is this enough? Looking at FSL U-boot there is also a:
>
> static inline void set_board_rev(void)
> {
> if ((__REG(GPIO1_BASE_ADDR + 0x0) & (0x1 << 22)) == 0)
> system_rev |= BOARD_REV_2_0 << BOARD_VER_OFFSET;
>
> }
I have a question regarding this code: Is it normal that it does not enable a
weak pull-up (100 k) on UART3_RXD's pad? According to the schematic history, the
pull-down R6001 (10 k) has been added to UART3_RXD for revision 2. By default,
the pad of this pin has its keeper enabled, not its pull, so everything is fine
with this code for revision 2, but what about revision 1?
To reformulate my question: Was there anything on this board before R6001
inputting a high level on UART3_RXD, or does the pad keeper guarantee some
default init level by design if the pin is externally left floating?
Best regards,
Beno?t
next prev parent reply other threads:[~2012-09-18 16:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CEF1C43EC1BF464090308EB428E1360001B95B@AMEXMB02.ds.jdsu.net>
2012-09-17 19:04 ` [U-Boot] [PATCH] mx51evk: Add CONFIG_REVISION_TAG Benoît Thébaudeau
2012-09-18 3:24 ` Fabio Estevam
[not found] ` <CEF1C43EC1BF464090308EB428E1360001BA57@AMEXMB02.ds.jdsu.net>
2012-09-18 13:36 ` Fabio Estevam
2012-09-18 13:41 ` Benoît Thébaudeau
2012-09-18 13:38 ` Fabio Estevam
2012-09-18 13:54 ` Benoît Thébaudeau
2012-09-18 14:02 ` Fabio Estevam
2012-09-18 14:11 ` Fabio Estevam
[not found] ` <CEF1C43EC1BF464090308EB428E1360001BAA1@AMEXMB02.ds.jdsu.net>
2012-09-18 14:19 ` Fabio Estevam
2012-09-18 14:36 ` Stefano Babic
2012-09-18 14:32 ` Stefano Babic
2012-09-18 16:01 ` Benoît Thébaudeau [this message]
2012-09-18 16:12 ` Fabio Estevam
2012-09-18 14:48 ` [U-Boot] [PATCH v2] " Benoît Thébaudeau
2012-09-18 15:11 ` Fabio Estevam
2012-09-23 17:55 ` 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=1211243740.4667119.1347984062746.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox