public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: R Sricharan <r.sricharan@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 1/5] ARM: OMAP5: Add silicon id support for ES2.0 revision.
Date: Tue, 5 Feb 2013 18:02:13 +0530	[thread overview]
Message-ID: <5110FBCD.1020703@ti.com> (raw)
In-Reply-To: <20130204194114.GA4740@kahuna>

On Tuesday 05 February 2013 01:11 AM, Nishanth Menon wrote:
> On 19:59-20130204, R Sricharan wrote:
>> Adding the CPU detection suport for OMAP5430 and
>> OMAP5432 ES2.0 SOCs.
>>
>> Signed-off-by: R Sricharan <r.sricharan@ti.com>
>> ---
>>   arch/arm/cpu/armv7/omap5/hwinit.c      |   13 +++++++++++--
>>   arch/arm/include/asm/arch-omap5/omap.h |    2 ++
>>   arch/arm/include/asm/armv7.h           |    1 +
>>   arch/arm/include/asm/omap_common.h     |    2 ++
>>   4 files changed, 16 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm/cpu/armv7/omap5/hwinit.c b/arch/arm/cpu/armv7/omap5/hwinit.c
>> index dfc0e44..0d8c95d 100644
>> --- a/arch/arm/cpu/armv7/omap5/hwinit.c
>> +++ b/arch/arm/cpu/armv7/omap5/hwinit.c
>> @@ -216,8 +216,17 @@ void init_omap_revision(void)
>>   			break;
>>   		}
>>   		break;
>> -	default:
>> -		*omap_si_rev = OMAP5430_SILICON_ID_INVALID;
>> +	case MIDR_CORTEX_A15_R2P2:
>> +		switch (readl(CONTROL_ID_CODE)) {
>> +		case OMAP5430_CONTROL_ID_CODE_ES2_0:
>> +			*omap_si_rev = OMAP5430_ES2_0;
>> +			break;
>> +		case OMAP5432_CONTROL_ID_CODE_ES2_0:
>> +			*omap_si_rev = OMAP5432_ES2_0;
>> +			break;
>> +		default:
>> +			*omap_si_rev = OMAP5430_SILICON_ID_INVALID;
>> +		}
>
> A first few samples of both ES1.0 and ES2.0 (in the few 10s of samples) came with wrong efuse
> ID fused in, why would we want to make it a standard to check ARMsilicon
> revision *and then* cross verify against control fuse verification, *and
> then* give up saying we dont support it?
>
> Looks like an over check for me -> IMHO, we should drop the MIDR checks
> entirely.
  In the same context, for some boards in past even in the actual samples
  the CONTROL ID code was reading the older revision. So in those
  cases ARM revision will help to differentiate them.

  But then it should have been in the opposite way, like reading the 
CONTROL_CODE first and then reading the ARM revision if required in 
those cases where is it broken. I will change this logic here.

Regards,
  Sricharan

  reply	other threads:[~2013-02-05 12:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 14:29 [U-Boot] [PATCH V2 0/5] ARM: OMAP5: Add support for OMAP543x ES2.0 Socs R Sricharan
2013-02-04 14:29 ` [U-Boot] [PATCH V2 1/5] ARM: OMAP5: Add silicon id support for ES2.0 revision R Sricharan
2013-02-04 15:43   ` Tom Rini
2013-02-04 19:41   ` Nishanth Menon
2013-02-05 12:32     ` R Sricharan [this message]
2013-02-05 15:19       ` Nishanth Menon
2013-02-06  6:10         ` R Sricharan
2013-02-04 14:29 ` [U-Boot] [PATCH V2 2/5] ARM: OMAP5: clock: Add the prcm register changes required for ES2.0 R Sricharan
2013-02-04 15:43   ` Tom Rini
2013-02-04 14:29 ` [U-Boot] [PATCH V2 3/5] ARM: OMAP5: clocks: Add OPP settings required for OMAP543X ES2.0 soc R Sricharan
2013-02-04 15:44   ` Tom Rini
2013-02-04 20:16   ` Nishanth Menon
2013-02-05 12:02     ` R Sricharan
2013-02-05 15:29       ` Nishanth Menon
2013-02-06  7:12         ` R Sricharan
2013-02-04 14:29 ` [U-Boot] [PATCH V2 4/5] ARM: OMAP5: Add DDR changes required for OMAP543X ES2.0 SOCs R Sricharan
2013-02-04 15:44   ` Tom Rini
2013-02-04 14:29 ` [U-Boot] [PATCH V2 5/5] ARM: OMAP5: srcomp: enable slew rate compensation cells after powerup R Sricharan
2013-02-04 15:44   ` Tom Rini

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=5110FBCD.1020703@ti.com \
    --to=r.sricharan@ti.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