[U-Boot] [PATCH] ARMV7: OMAP3: BeagleBoard: add xM rev B to ID table

[Steve Sakoman]

On Sun, Nov 7, 2010 at 6:56 AM, Nishanth Menon <menon.nishanth at gmail.com> wrote:
> Premi, Sanjeev wrote, on 11/07/2010 03:16 AM:
>>>
>>> -----Original Message-----
>>> From: u-boot-bounces at lists.denx.de
>>> [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Steve Sakoman
>>> Sent: Saturday, November 06, 2010 8:35 AM
>>> To: Nishanth Menon
>>> Cc: u-boot at lists.denx.de; Koen Kooi
>>> Subject: Re: [U-Boot] [PATCH] ARMV7: OMAP3: BeagleBoard: add
>>> xM rev B to ID table
>>>
>> [snip]
>>
>>> Note that for 36xx my patch sets the max to 720 -- this is because
>>> mainline/linux-omap currently does not support 1000.  We can adjust
>>> that when kernel support for 1000 appears.
>>
>> [sp] 720MHz is not a valid frequency for 36x. It is the highest freq
>>      for OMAP35x - subject to associated bit set in the silicon.
>>      600MHz would be be safe for all OMAP35x family processors.
>>
>>      For 36xx, the freq should be 800MHz (if you don't want 1GHz).
>
> yep, Good catch :) , 720 is not valid either 800/1GHz :(

Thanks for pointing out that I can go up to 800 Mhz.

For the record, on my 3730 based system, using:

Linux version 2.6.36 (steve at build.sakoman.com) (gcc version 4.3.3
(GCC) ) #1 Thu  Nov 4 21:19:18 PDT 2010

The kernel reports the processor as:

OMAP3630 ES1.0 (l2cache iva sgx neon isp 192mhz_clk )

I tried mpurate settings of 720, 800, and 1000.

Though you say it is "not valid", an mpurate setting of 720 is
successful and yields:

Switched to new clocking rate (Crystal/Core/MPU): 26.0/720/359 MHz

An mpurate setting of 800 is successful and yields:

Switched to new clocking rate (Crystal/Core/MPU): 26.0/800/359 MHz

An mpurate setting of 1000 is not successful and yields:

WARNING: at arch/arm/mach-omap2/clock.c:440
omap2_clk_switch_mpurate_at_boot+0x80/0xb4()
clock: dpll1_ck: unable to set MPU rate to 1000: -22

I will resubmit the patch changing to 800 for 36XX/37XX.

Steve