RE: [RFC][PATCH] OMAP3: introduce OMAP3630

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




>-----Original Message-----
>From: Shilimkar, Santosh
>>
>> diff --git a/arch/arm/plat-omap/include/mach/cpu.h b/arch/arm/plat-
>> omap/include/mach/cpu.h
>> index 431fec4..af1080f 100644
>> --- a/arch/arm/plat-omap/include/mach/cpu.h
>> +++ b/arch/arm/plat-omap/include/mach/cpu.h
>> @@ -383,6 +383,12 @@ IS_OMAP_TYPE(3430, 0x3430)
>>  #define OMAP3430_REV_ES2_1	0x34302034
>>  #define OMAP3430_REV_ES3_0	0x34303034
>>  #define OMAP3430_REV_ES3_1	0x34304034
>> +/* NOTE: Add 36xx series below
>> + * If additional 34xx series are added, OMAP3430_REV_ESXXXX can be
>> + * added above the 3630 defines and series renumbered to ensure
>> + * rev() > checks to work
>> + */
>> +#define OMAP3630_REV_ES1_0	0x34305034
>>
>>  #define OMAP443X_CLASS		0x44300034
>Was expecting that this patch will add "cpu_is_omap36xx()" in cpu.h
>apart from above. Is this handled in another patch ?

Idea is to re-use all 34xx code for 36xx, as per the mail thread on list, and given in reference.
Hence at run time, the check could be:

if (omap_rev() == OMAP3630_REV_ES1_0)
	xxxxx

cpu_is_omap34xx() will be true for 36xx as well.

>
>
>Regards,
>Santosh
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux