public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Bo Shen <voice.shen@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/4] ARM: atmel: add sama5d3xek support
Date: Tue, 05 Mar 2013 10:03:57 +0800	[thread overview]
Message-ID: <5135528D.7050800@atmel.com> (raw)
In-Reply-To: <20130304151459.GA25797@bill-the-cat>

Hi Tom,

On 3/4/2013 23:14, Tom Rini wrote:
> On Thu, Feb 28, 2013 at 03:00:47PM +0800, Bo Shen wrote:
>
>> Add sama5d3xek support with following feature
>>    - boot from NAND flash, PMECC support, 4bit ECC @ 512 bytes sector
>>    - boot from SPI flash support
>>    - boot from SD card support
>>    - LCD support
>>    - EMAC support
>>    - USB support
>>
>> Signed-off-by: Bo Shen <voice.shen@atmel.com>
>
> Some minor comments:
>
> [snip]
>> +	if (cpu_is_sama5d3())
>> +		switch (extension_id) {
>> +		case ARCH_EXID_SAMA5D31:
>> +			return CONFIG_SYS_AT91_D31_CPU_NAME;
>> +		case ARCH_EXID_SAMA5D33:
>> +			return CONFIG_SYS_AT91_D33_CPU_NAME;
>> +		case ARCH_EXID_SAMA5D34:
>> +			return CONFIG_SYS_AT91_D34_CPU_NAME;
>> +		case ARCH_EXID_SAMA5D35:
>> +			return CONFIG_SYS_AT91_D35_CPU_NAME;
>> +		default:
>> +			return CONFIG_SYS_AT91_UNKNOWN_CPU;
>
> These aren't configurable, and are used once.  Just put the strings
> here.

OK, I will use strings here directly here in next version.

>
>> @@ -0,0 +1,268 @@
>> +/*
>> + * Configuation settings for the SAMA5D3xEK board.
> [snip]
>> +#undef CONFIG_USE_IRQ			/* we don't need IRQ/FIQ stuff	*/
>> +
>> +#undef CONFIG_CMDLINE_TAG		/* enable passing of ATAGs	*/
>> +#undef CONFIG_SETUP_MEMORY_TAGS
>> +#undef CONFIG_INITRD_TAG
>
> Just leave these, and the other #undef's out.

You mean I need not to #undef these, because these are not defined, am I 
right?

>> +/*
>> + * Command line configuration.
>> + */
>> +#include <config_cmd_default.h>
>> +#undef CONFIG_CMD_FPGA
>> +#undef CONFIG_CMD_IMI
>> +#undef CONFIG_CMD_IMLS
>> +#undef CONFIG_CMD_AUTOSCRIPT
>> +#undef CONFIG_CMD_LOADS
>
> These are fine to leave in 'tho.

These are no useful for us.
I will consider remove unneeded #undef

>> +#ifdef CONFIG_USE_IRQ
>> +#error CONFIG_USE_IRQ not supported
>> +#endif
>
> Just drop that part.

Ok, I will drop this in next version.

> And please check things with checkpatch.pl, I
> thought I saw a '#define<tab>FOO' in there.  Thanks!

I have checked this patch with checkpatch.pl, and get no errors and no 
warnings.

Best Regards,
Bo Shen

  reply	other threads:[~2013-03-05  2:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28  7:00 [U-Boot] [PATCH 0/4] ARM: atmel: add sama5d3xek board support Bo Shen
2013-02-28  7:00 ` [U-Boot] [PATCH 1/4] USB: ohci-at91: support sama5d3x devices Bo Shen
2013-03-07  9:12   ` Andreas Bießmann
2013-03-08  1:21     ` Bo Shen
2013-02-28  7:00 ` [U-Boot] [PATCH 2/4] NET: macb: " Bo Shen
2013-03-07  9:15   ` Andreas Bießmann
2013-02-28  7:00 ` [U-Boot] [PATCH 3/4] SPI: atmel_spi: " Bo Shen
2013-02-28  7:00 ` [U-Boot] [PATCH 4/4] ARM: atmel: add sama5d3xek support Bo Shen
2013-03-04 15:14   ` Tom Rini
2013-03-05  2:03     ` Bo Shen [this message]
2013-03-05  2:20       ` Tom Rini
2013-03-05  2:23         ` Bo Shen
2013-03-07 10:58   ` Andreas Bießmann
2013-03-08  3:31     ` Bo Shen
2013-03-08  7:32       ` Andreas Bießmann
2013-03-08  8:37         ` Bo Shen

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=5135528D.7050800@atmel.com \
    --to=voice.shen@atmel.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