Hello,
OMAP3530 has now two skus. OMAP3530DCBB and OMAP3530DCBB72. The first one is the old one was marketed at 600Mhz and can be overclocked at 720Mhz. The new one is marketed at 720Mhz. But both seems to provide same information at u-boot (ES3.1, and device speed=600Mhz). Especially, the OMAP3530DCBB72 doesn't show the 720Mhz speed but still shows the 600Mhz. I'm referring to this patch in u-boot:
http://gitorious.org/angstrom/openembedded/blobs/org.openembedded.dev/recipes/u-boot/u-boot-git/beagleboard/0005-OMAP3-add-entry-for-rev-3.1.2-check-and-display-max-.patch
#define SKUID_CLK_MASK 0xf
#define SKUID_CLK_600MHZ 0x0
#define SKUID_CLK_720MHZ 0x8
u32 get_sku_id(void)
{
struct ctrl_id *id_base = (struct ctrl_id *)OMAP34XX_ID_L4_IO_BASE;
return (readl(&id_base->sku_id) & SKUID_CLK_MASK);
}
So my question are:
- why doesn't OMAP3530DCBB72 show a speed increase from OMAP3530DCBB? Is it just marketing bulls... to say that one can safely overclock it to 720Mhz and BTW price has been increased?
- If OMAP3530DCBB can be overclocked to 720Mhz in kernel, until which speed can OMAP3530DCBB72 be overclocked?
Thanks in advance for any answer,
Grégoire