All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] Setup extra MIMC200 chip selects
Date: Sat, 24 Jan 2009 00:46:48 +0100	[thread overview]
Message-ID: <20090123234648.38B77832E425@gemini.denx.de> (raw)
In-Reply-To: <492A8D60.3090309@mimc.co.uk>

Dear Mark Jackson,

In message <492A8D60.3090309@mimc.co.uk> you wrote:
> Added code to setup the extra Flash and FRAM chip selects
> as used on the MIMC200 board.
> 
> Signed-off-by: Mark Jackson <mpfj@mimc.co.uk>
> 
> ---
>  cpu/at32ap/cpu.c |   14 ++++++++++++++
>  1 files changed, 14 insertions(+), 0 deletions(-)
> 
> diff --git a/cpu/at32ap/cpu.c b/cpu/at32ap/cpu.c
> index 1a13702..3902efe 100644
> --- a/cpu/at32ap/cpu.c
> +++ b/cpu/at32ap/cpu.c
> @@ -56,6 +56,20 @@ int cpu_init(void)
>  	hsmc3_writel(PULSE0, 0x0b0a0906);
>  	hsmc3_writel(SETUP0, 0x00010002);
>  
> +#ifdef CONFIG_MIMC200
> +	/* setup Data Flash chip select (NCS2) */
> +	hsmc3_writel(MODE2, 0x20121003);
> +	hsmc3_writel(CYCLE2, 0x000a0009);
> +	hsmc3_writel(PULSE2, 0x0a060806);
> +	hsmc3_writel(SETUP2, 0x00030102);
> +
> +	/* setup FRAM chip select (NCS3) */
> +	hsmc3_writel(MODE3, 0x10120001);
> +	hsmc3_writel(CYCLE3, 0x001e001d);
> +	hsmc3_writel(PULSE3, 0x08040704);
> +	hsmc3_writel(SETUP3, 0x02050204);
> +#endif

I feel it is conceptually wrong to add board specific code to a common
CPU specific file.

Haavard, please comment?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Accident: A condition in which presence of mind is good, but  absence
of body is better.

  reply	other threads:[~2009-01-23 23:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-24 11:17 [U-Boot] [PATCH 1/1] Setup extra MIMC200 chip selects Mark Jackson
2009-01-23 23:46 ` Wolfgang Denk [this message]
2009-02-06 19:48   ` Mark Jackson

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=20090123234648.38B77832E425@gemini.denx.de \
    --to=wd@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.