OMAP3: id: use explicit omap_revision codes for 3505/3517 ES levels

Use explicit revision codes for OMAP/AM 3505/3517 ES levels, as the rest
of the OMAP2+ SoCs do in mach-omap2/cpu.c.

Signed-off-by: Paul Walmsley <paul@pwsan.com>
Cc: Sanjeev Premi <premi@ti.com>
Tested-by: Igor Grinberg <grinberg@compulab.co.il>
Tested-by: Abhilash Koyamangalath <abhilash.kv@ti.com>
This commit is contained in:
Paul Walmsley
2011-09-13 19:52:14 -06:00
parent 91d92d6cc8
commit 9ed2ba7aa7
2 changed files with 11 additions and 2 deletions

View File

@ -312,7 +312,15 @@ static void __init omap3_check_revision(void)
*
* REVISIT: AM3505/AM3517 should have their own CHIP_IS
*/
omap_revision = OMAP3517_REV(rev);
switch (rev) {
case 0:
omap_revision = OMAP3517_REV_ES1_0;
break;
case 1:
/* FALLTHROUGH */
default:
omap_revision = OMAP3517_REV_ES1_1;
}
omap_chip.oc |= CHIP_IS_OMAP3430ES3_1;
break;
case 0xb891: