From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] AT91: at91sam9g10 chip identification changed
Date: Wed, 14 Apr 2010 10:14:47 +0200 [thread overview]
Message-ID: <4BC57977.7000705@atmel.com> (raw)
In-Reply-To: <l2ocd73a99e1004130042qfe9aba83l512a0fad50112d19@mail.gmail.com>
Le 13/04/2010 09:42, Andrew Victor :
> hi Nicolas,
>
>> A bit in the at91sam9g10 identification number changed between Engineering
>> Sample and final product. This patch will identify both as being at91sam9g10.
>
>> -#define ARCH_ID_AT91SAM9G10 0x819903a0
>> +#define ARCH_ID_AT91SAM9G10 0x019903a0
>
>> -#define cpu_is_at91sam9g10() (at91_cpu_identify() == ARCH_ID_AT91SAM9G10)
>> +#define cpu_is_at91sam9g10() ((at91_cpu_identify() & ~AT91_CIDR_EXT) == ARCH_ID_AT91SAM9G10)
>
>
> Wouldn't it be better to just mask out the AT91_CIDR_EXT bit in
> at91_cpu_identify()?
> That bit isn't really useful for "version" information.
>
> We'd then just need to modify:
> #define ARCH_ID_AT91SAM9G10 0x019903a0
> #define ARCH_ID_AT91SAM9G45 0x019b05a0
> #define ARCH_ID_AT91SAM9G45MRL 0x019b05a2 /* aka 9G45-ES2 &
> non ES lots */
> #define ARCH_ID_AT91SAM9G45ES 0x019b05a1 /* 9G45-ES
> (Engineering Sample) */
> (ie, drop bit AT91_CIDR_EXT)
I do not think it is a good idea:
1/ a little issue appears with AT91SAM9G45ES that is using the
at91_cpu_fully_identify() functions.
2/ we do not exclude raising the extended bit after a chip has been
created to introduce a variant of this chip. If we mask out the
AT91_CIDR_EXT bit in at91_cpu_identify() we will not be able to identify
this new variant as being different from the original chip.
Best regards,
--
Nicolas Ferre
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Andrew Victor <avictor.za@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] AT91: at91sam9g10 chip identification changed
Date: Wed, 14 Apr 2010 10:14:47 +0200 [thread overview]
Message-ID: <4BC57977.7000705@atmel.com> (raw)
In-Reply-To: <l2ocd73a99e1004130042qfe9aba83l512a0fad50112d19@mail.gmail.com>
Le 13/04/2010 09:42, Andrew Victor :
> hi Nicolas,
>
>> A bit in the at91sam9g10 identification number changed between Engineering
>> Sample and final product. This patch will identify both as being at91sam9g10.
>
>> -#define ARCH_ID_AT91SAM9G10 0x819903a0
>> +#define ARCH_ID_AT91SAM9G10 0x019903a0
>
>> -#define cpu_is_at91sam9g10() (at91_cpu_identify() == ARCH_ID_AT91SAM9G10)
>> +#define cpu_is_at91sam9g10() ((at91_cpu_identify() & ~AT91_CIDR_EXT) == ARCH_ID_AT91SAM9G10)
>
>
> Wouldn't it be better to just mask out the AT91_CIDR_EXT bit in
> at91_cpu_identify()?
> That bit isn't really useful for "version" information.
>
> We'd then just need to modify:
> #define ARCH_ID_AT91SAM9G10 0x019903a0
> #define ARCH_ID_AT91SAM9G45 0x019b05a0
> #define ARCH_ID_AT91SAM9G45MRL 0x019b05a2 /* aka 9G45-ES2 &
> non ES lots */
> #define ARCH_ID_AT91SAM9G45ES 0x019b05a1 /* 9G45-ES
> (Engineering Sample) */
> (ie, drop bit AT91_CIDR_EXT)
I do not think it is a good idea:
1/ a little issue appears with AT91SAM9G45ES that is using the
at91_cpu_fully_identify() functions.
2/ we do not exclude raising the extended bit after a chip has been
created to introduce a variant of this chip. If we mask out the
AT91_CIDR_EXT bit in at91_cpu_identify() we will not be able to identify
this new variant as being different from the original chip.
Best regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2010-04-14 8:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 9:48 [PATCH] AT91: at91sam9g10 chip identification changed Nicolas Ferre
2010-04-01 9:48 ` Nicolas Ferre
2010-04-12 18:44 ` Russell King - ARM Linux
2010-04-12 18:44 ` Russell King - ARM Linux
2010-04-13 7:42 ` Andrew Victor
2010-04-13 7:42 ` Andrew Victor
2010-04-14 8:14 ` Nicolas Ferre [this message]
2010-04-14 8:14 ` Nicolas Ferre
2010-04-14 15:01 ` Andrew Victor
2010-04-14 15:01 ` Andrew Victor
2010-04-14 15:40 ` Nicolas Ferre
2010-04-14 15:40 ` Nicolas Ferre
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=4BC57977.7000705@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.