From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4] Add initial support for Wandboard dual lite and solo.
Date: Fri, 15 Mar 2013 19:26:53 +0100 [thread overview]
Message-ID: <514367ED.6070101@denx.de> (raw)
In-Reply-To: <20130315172741.353A42005F7@gemini.denx.de>
On 15/03/2013 18:27, Wolfgang Denk wrote:
> Dear Stefano Babic,
>
Hi Wolfgang,
> I agree that it is important information, and there should be a way
> that the user can get at this information. But I see no urgent need
> to print this for everyboot, where it is just costing us precious boot
> time (yes, it's only a few milliseconds, but they are trivial to
> save).
>
> That was why I suggested to add thjis information for example to the
> output of the "bdinfo" command.
That is fine - but then it should be consistent. We have tried to have a
consistent API between SOCs (I mean: iMX SOCs), that is, each SOC in the
i.MX family should implement the same functions and not invent a new
one, And the behavior must beconsistent, too. I know we are far away to
be perfect, and some code can be further factorized (this was the reason
to add imx_common).
To the specific case, each i.MX SOC implements a get_reset_cause() function:
arch/arm/cpu/arm1136/mx31/generic.c:static char *get_reset_cause(void)
arch/arm/cpu/arm1136/mx31/generic.c: printf("Reset cause: %s\n",
arch/arm/cpu/arm1136/mx35/generic.c:static char *get_reset_cause(void)
arch/arm/cpu/arm1136/mx35/generic.c: printf("Reset cause: %s\n",
get_reset_cause());
arch/arm/cpu/arm926ejs/mx25/generic.c:static char *get_reset_cause(void)
arch/arm/cpu/arm926ejs/mx25/generic.c: printf("Reset cause: %s\n\n",
arch/arm/imx-common/cpu.c:char *get_reset_cause(void)
arch/arm/imx-common/cpu.c: printf("Reset cause: %s\n", get_reset_cause());
Checking this I see also that the mx53loco does not use general code
(bad !):
board/freescale/mx53loco/mx53loco.c: printf("Reset cause: %s\n",
It is ok to move the information to bdinfo, but then it should not break
the consistence: all i.MX should follow the same rule. This makes also
easier for board maintainers to switch from a SOC to the next one,
because they have to provide quite the same functions in their code (and
using the same functions, too.).
> BTW: if I type "reset", I will get a message "Reset cause: WDOG".
> I know why, but most users will not know thy they see a watchdog reset
> here, so actually this information may be more confusing than helpful
> in a number of cases (which is IMO one more reason to not always to
> display it - it saves us a number of unproductive support requests).
I agree with you that this should be done by a separate patchset: it is
not related to the Wandboard. But if we go on this way, the same changes
should be done for all i.MX, not only for i.MX5/i.MX6.
Best regards,
Stefano Babic
--
=====================================================================
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:[~2013-03-15 18:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 2:32 [U-Boot] [PATCH v4] Add initial support for Wandboard dual lite and solo Fabio Estevam
2013-03-14 12:31 ` Wolfgang Denk
2013-03-14 17:01 ` Fabio Estevam
2013-03-14 17:36 ` Tom Rini
2013-03-14 20:36 ` Wolfgang Denk
2013-03-14 21:01 ` Tom Rini
2013-03-14 22:17 ` Scott Wood
2013-03-14 20:24 ` Wolfgang Denk
2013-03-15 14:55 ` Stefano Babic
2013-03-15 17:27 ` Wolfgang Denk
2013-03-15 18:26 ` Stefano Babic [this message]
2013-03-15 20:48 ` Wolfgang Denk
2013-03-14 20:13 ` Fabio Estevam
2013-03-14 20:37 ` Wolfgang Denk
2013-03-15 18:21 ` Fabio Estevam
2013-03-15 20:32 ` Fabio Estevam
2013-03-15 20:52 ` Wolfgang Denk
2013-03-20 10:12 ` 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=514367ED.6070101@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