public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Hong Xu <hong.xu@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2 V3] AT91: Makes AT91SAM9RL SoC build correctly against u-boot-atmel/master
Date: Mon, 01 Aug 2011 16:13:59 +0800	[thread overview]
Message-ID: <4E366047.3050908@atmel.com> (raw)
In-Reply-To: <1312185615.3635.105.camel@ubuntu>

Hi Reinhard,

On 08/01/2011 04:00 PM, Reinhard Meyer wrote:
> Dear Hong Xu,
>  > Rework for AT91SAM9RL SoC, makes it build again.
>  > arch/arm/include/asm/arch-at91/at91sam9rl_matrix.h | 121 +++++---------
>
> When I compare at91sam9rl_matrix.h to at91sam9260_matrix.h there is only
> one subtle difference:
>
> at91sam9260_matrix.h:
>
> struct at91_matrix {
> u32 mcfg[16]; /* Master Configuration Registers */
> u32 scfg[16]; /* Slave Configuration Registers */
> u32 pras[16][2]; /* Priority Assignment Slave Registers */
> u32 mrcr; /* Master Remap Control Register */
> u32 filler[0x06];
> u32 ebicsa; /* EBI Chip Select Assignment Register */
>
> at91sam9rl_matrix.h:
>
> struct at91_matrix {
> u32 mcfg[16]; /* Master Configuration Registers */
> u32 scfg[16]; /* Slave Configuration Registers */
> u32 pras[16][2]; /* Priority Assignment Slave Registers */
> u32 mrcr; /* Master Remap Control Register */
> u32 filler[7];
> u32 ebicsa; /* EBI Chip Select Assignment Register */
> };
>
> 1. Is it really filler[7] for the 9rl - can you verify with the data
> sheet?

Confirmed. ebicsa is at 0x120 for SAM9RL, but 0x11c for SAM9260.

> 2. It seems there is a possibility to unify all those _matrix files into
> one in the future (we are not going to do this now!) ?

There are many differents among chips. For example, on SAM9260/SAM9G10

struct at91_matrix {
         u32     mcfg;   /* Master Configuration Registers */
         u32     scfg[5];        /* Slave Configuration Registers */
         u32     filler[6];
         u32     ebicsa;         /* EBI Chip Select Assignment Register */
};

And for newer chips, some new fields are added. Can we keep current 
scheme and then have a look to see whether we have an elegant way to 
handle this? BTW, we're going to add some new chips soon.

Thanks.

BR,
Eric

      reply	other threads:[~2011-08-01  8:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-15  3:11 [U-Boot] [PATCH 1/2 V3] AT91: Makes AT91SAM9RL SoC build correctly against u-boot-atmel/master Hong Xu
2011-06-15  3:11 ` [U-Boot] [PATCH 2/2 V3] AT91: Makes AT91SAM9RL-EK " Hong Xu
2011-06-22  8:14   ` Hong Xu
2011-06-22  8:13 ` [U-Boot] [PATCH 1/2 V3] AT91: Makes AT91SAM9RL SoC " Hong Xu
2011-06-22  9:03   ` Wolfgang Denk
2011-06-22  9:15     ` Hong Xu
2011-08-01  2:28 ` Reinhard Meyer
2011-08-01  8:00 ` Reinhard Meyer
2011-08-01  8:13   ` Hong Xu [this message]

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=4E366047.3050908@atmel.com \
    --to=hong.xu@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