From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] mx5: drop boot cause code from board support code
Date: Thu, 21 Apr 2011 19:18:30 +0200 [thread overview]
Message-ID: <4DB066E6.7050705@denx.de> (raw)
In-Reply-To: <1303296425-14806-1-git-send-email-jason.hui@linaro.org>
On 04/20/2011 12:47 PM, Jason Liu wrote:
> The boot cause code has been factor out to soc common
> code,we need drop the part from the board support code
>
> Signed-off-by: Jason Liu <jason.hui@linaro.org>
Hi Jason,
> ---
> board/efikamx/efikamx.c | 30 ++++++------------------------
> board/freescale/mx51evk/mx51evk.c | 26 ++++++--------------------
> board/freescale/mx53evk/mx53evk.c | 21 +--------------------
> board/ttcontrol/vision2/vision2.c | 28 ++++++----------------------
> 4 files changed, 19 insertions(+), 86 deletions(-)
>
> diff --git a/board/efikamx/efikamx.c b/board/efikamx/efikamx.c
> index f735260..0aef654 100644
> --- a/board/efikamx/efikamx.c
> +++ b/board/efikamx/efikamx.c
> @@ -644,46 +644,28 @@ int board_late_init(void)
> int checkboard(void)
> {
> u32 system_rev = get_cpu_rev();
> - u32 cause;
> - struct src *src_regs = (struct src *)SRC_BASE_ADDR;
This seems to me not the best solution. If we have now factored out code
to print the reset cause and the silicon version (inside print_cpuinfo),
why do we need to repeat this code for each board ? Calling get_cpu_rev
seems to me redundant (then each board should only set
CONFIG_DISPLAY_CPUINFO). And then the CPU revision is printed again, and
this is redundant.
>
> puts("Board: Efika MX ");
>
> switch (system_rev & 0xff) {
As I see in code, in system_rev & 0xff we can find the cpu revision, and
the output is already part of print_cpuinfo.
I think we need more clean up, removing all part related to CPU revision
and leaving (if any) only the output related to the board revision.
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-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2011-04-21 17:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 10:47 [U-Boot] [PATCH 1/1] mx5: drop boot cause code from board support code Jason Liu
2011-04-20 10:47 ` [U-Boot] [PATCH V5 1/2] MX5: factor out boot cause funciton to common code Jason Liu
2011-04-21 17:53 ` Stefano Babic
2011-04-20 10:47 ` [U-Boot] [PATCH V5 2/2] MX53: support for freescale MX53LOCO board Jason Liu
2011-04-21 17:43 ` Stefano Babic
2011-04-21 23:24 ` Wolfgang Denk
2011-04-22 4:36 ` Jason Hui
2011-04-22 5:10 ` Jason Hui
2011-04-22 6:57 ` Stefano Babic
2011-04-22 8:33 ` Jason Liu
2011-04-22 9:11 ` Stefano Babic
2011-04-22 12:45 ` Wolfgang Denk
2011-04-22 13:18 ` Jason Liu
2011-04-21 17:18 ` Stefano Babic [this message]
2011-04-22 5:45 ` [U-Boot] [PATCH 1/1] mx5: drop boot cause code from board support code Jason Hui
2011-04-22 7:06 ` Stefano Babic
2011-04-22 8:34 ` Jason Liu
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=4DB066E6.7050705@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 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.