All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/5] MX5: Add initial support for MX53
Date: Thu, 16 Dec 2010 14:34:40 +0100	[thread overview]
Message-ID: <4D0A1570.10300@denx.de> (raw)
In-Reply-To: <1292494665-25674-2-git-send-email-r64343@freescale.com>

On 12/16/2010 11:17 AM, Jason Liu wrote:
> Add initial support for Freescale MX53 processor,
> 
> - Add the iomux support and the pin definition,
> - Add the regs definition, clean up some unused def from mx51,
> - Add the low level init support, make use the freq input of setup_pll macro
> 
> ---
> Changes for v2:
> --address some comments of Stefano Babic,

Please add always the version number in the e-mail subject, if it is a
resubmission, so we can know there is a previous version. Please add a
small list with all changes, as I cannot know which of them you implemented.

> diff --git a/arch/arm/cpu/armv7/mx5/soc.c b/arch/arm/cpu/armv7/mx5/soc.c
> index 2900119..f5e0283 100644
> --- a/arch/arm/cpu/armv7/mx5/soc.c
> +++ b/arch/arm/cpu/armv7/mx5/soc.c
> @@ -35,6 +35,8 @@
>  
>  #if defined(CONFIG_MX51)
>  #define CPU_TYPE 0x51000
> +#elif defined(CONFIG_MX53)
> +#define CPU_TYPE 0x53000
>  #else
>  #error "CPU_TYPE not defined"
>  #endif

In the previous discussion on first submit it seemd to me you agreed to
change this part, as we have already CONFIG_MX51 and CONFIG_MX53 and
additional defines are not needed. However, you resubmit the same code.

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
=====================================================================

  parent reply	other threads:[~2010-12-16 13:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-16 10:17 [U-Boot] [PATCH 0/5] Add support for Freescale MX53 Jason Liu
2010-12-16 10:17 ` [U-Boot] [PATCH 1/5] MX5: Add initial support for MX53 Jason Liu
2010-12-16 12:27   ` Wolfgang Denk
2010-12-17  3:20     ` Jason Liu
2010-12-16 13:34   ` Stefano Babic [this message]
2010-12-17  3:18     ` Jason Liu
2010-12-16 10:17 ` [U-Boot] [PATCH 2/5] serial_mxc: add support for MX53 processor Jason Liu
2010-12-16 10:17 ` [U-Boot] [PATCH 3/5] fec_mxc: " Jason Liu
2010-12-16 10:17 ` [U-Boot] [PATCH 4/5] mxc_i2c: " Jason Liu
2010-12-16 10:37   ` Heiko Schocher
2010-12-17  3:28     ` Jason Liu
2010-12-16 10:17 ` [U-Boot] [PATCH 5/5] MX5:MX53: add initial support for MX53EVK board Jason Liu
2010-12-16 10:48   ` Albert ARIBAUD
2010-12-16 12:23     ` Wolfgang Denk
2010-12-16 13:19   ` Stefano Babic
2010-12-17  3:05     ` Jason Liu
2010-12-17  5:41       ` Wolfgang Denk
2010-12-17 10:20       ` Albert ARIBAUD
2010-12-17 13:05       ` Stefano Babic
2010-12-20  5:19         ` Jason Liu
2010-12-20  6:52           ` John Rigby
2010-12-22 13:40             ` Jason Liu
2010-12-27 10:03             ` Stefano Babic
2010-12-20  6:52           ` Albert ARIBAUD
2010-12-16 23:04   ` Wolfgang Denk
2010-12-17  3:04     ` Jason Liu
2010-12-17  5:36       ` Wolfgang Denk
2010-12-16 12:25 ` [U-Boot] [PATCH 0/5] Add support for Freescale MX53 Wolfgang Denk

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=4D0A1570.10300@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.