From: Ilya Yanok <yanok@emcraft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] mpc8308: support for Freescale MPC8308 cpu
Date: Mon, 21 Jun 2010 15:41:20 +0400 [thread overview]
Message-ID: <4C1F4FE0.6050804@emcraft.com> (raw)
In-Reply-To: <20100621074434.D06EB13653E@gemini.denx.de>
Dear Wolfgang,
thanks for your review.
On 21.06.2010 11:44, Wolfgang Denk wrote:
>> This patch adds basic support for Freescale MPC8308 CPU. Serial ports,
>> NOR flash and integrated Ethernet controllers are supported.
>> PCI Express is also supported. eSDHC, NAND and USB may work but aren't
>> tested (using ULPI PHY requires additional patch).
>>
>> Signed-off-by: Ilya Yanok<yanok@emcraft.com>
>>
> ...
>
>> -#if defined(CONFIG_MPC834x) || defined(CONFIG_MPC837x) || defined(CONFIG_MPC8315)
>> +#if defined(CONFIG_MPC834x) || defined(CONFIG_MPC837x) || \
>> + defined(CONFIG_MPC8315) || defined(CONFIG_MPC8308)
>>
> Please sort this list.
>
Fixed.
>> +#if defined(CONFIG_MPC8308)
>> +#define SCCR_SDHCCM 0x0c000000
>> +#define SCCR_SDHCCM_SHIFT 26
>> +#define SCCR_SDHCCM_0 0x00000000
>> +#define SCCR_SDHCCM_1 0x04000000
>> +#define SCCR_SDHCCM_2 0x08000000
>> +#define SCCR_SDHCCM_3 0x0c000000
>> +#endif
>>
> Would it make sense to write this as:
>
> And: why do we need the #ifdef? Unused defines should not hurt?
>
> #define SCCR_SDHCCM_MASK 0x0c000000 /* is it a mask? */
> #define SCCR_SDHCCM_SHIFT 26
> #define SCCR_SDHCCM(arg) ((arg)<<SCCR_SDHCCM_SHIFT)
>
>
As you already mentioned I'm just following the style used in this file.
>> +#if defined(CONFIG_MPC8315)
>> #define SCCR_SATA1CM 0x00003000
>> #define SCCR_SATA1CM_SHIFT 12
>> #define SCCR_SATACM 0x00003c00
>> @@ -765,6 +776,7 @@
>> #define SCCR_SATACM_1 0x00001400
>> #define SCCR_SATACM_2 0x00002800
>> #define SCCR_SATACM_3 0x00003c00
>> +#endif
>>
> Do we need that #ifdef? Ok, the #defines don't apply to the 8308, but
> do they hurt if they are just there, unused?
>
Well, it seems to be safer not to have unused defines so that you can't
erroneously use some define not applicable for current CPU, but if you
wish I'll remove these ifdefs.
Regards, Ilya.
next prev parent reply other threads:[~2010-06-21 11:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-20 17:32 [U-Boot] [PATCH 0/2] Support for MPC8308ERDB board Ilya Yanok
2010-06-20 17:32 ` [U-Boot] [PATCH 1/2] mpc8308: support for Freescale MPC8308 cpu Ilya Yanok
2010-06-21 7:44 ` Wolfgang Denk
2010-06-21 11:41 ` Ilya Yanok [this message]
2010-06-22 16:11 ` Wolfgang Denk
2010-06-28 12:44 ` Ilya Yanok
2010-07-09 21:13 ` Kim Phillips
2010-06-20 17:32 ` [U-Boot] [PATCH 2/2] MPC8308ERDB: minimal support for devboard from Freescale Ilya Yanok
2010-06-21 7:44 ` Wolfgang Denk
2010-06-21 12:25 ` Ilya Yanok
2010-06-22 18:14 ` Wolfgang Denk
2010-06-22 19:10 ` Ben Warren
2010-06-23 12:01 ` Ilya Yanok
2010-06-23 11:57 ` Ilya Yanok
2010-06-23 0:17 ` Kim Phillips
2010-06-23 21:30 ` Ilya Yanok
2010-06-23 22:08 ` Wolfgang Denk
2010-06-24 15:59 ` Ilya Yanok
2010-06-24 18:00 ` Kim Phillips
2010-06-24 19:36 ` Ilya Yanok
2010-06-25 1:25 ` Aggrwal Poonam-B10812
[not found] ` <20100624190054.847e4452.kim.phillips@freescale.com>
2010-07-20 0:33 ` Kim Phillips
2010-07-20 5:46 ` Wolfgang Denk
2010-07-20 15:08 ` Ilya Yanok
2010-08-10 16:32 ` [U-Boot] [PATCH 2/2] MPC8308ERDB: minimal support for devboard from Freescale (ICache issue) Ilya Yanok
2010-06-28 12:45 ` [U-Boot] [PATCH 2/2] MPC8308ERDB: minimal support for devboard from Freescale Ilya Yanok
2010-07-01 0:30 ` Kim Phillips
2010-07-01 9:13 ` Ilya Yanok
2010-07-07 16:16 ` [U-Boot] [PATCH 2/2] MPC8308RDB: " Ilya Yanok
2010-07-09 21:14 ` Kim Phillips
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=4C1F4FE0.6050804@emcraft.com \
--to=yanok@emcraft.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