From: Nishanth Menon <nm@ti.com>
To: "Premi, Sanjeev" <premi@ti.com>
Cc: "Pandita, Vikram" <vikram.pandita@ti.com>,
"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
linux-omap <linux-omap@vger.kernel.org>,
"Chikkature Rajashekar, Madhusudhan" <madhu.cr@ti.com>,
"Pais, Allen" <allen.pais@ti.com>,
"Gadiyar, Anand" <gadiyar@ti.com>,
"Cousson, Benoit" <b-cousson@ti.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
"Aguirre Rodriguez, Sergio Alberto" <saaguirre@ti.com>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [RFC][PATCH] OMAP3: introduce OMAP3630
Date: Thu, 8 Oct 2009 09:40:35 -0500 [thread overview]
Message-ID: <4ACDF9E3.4010701@ti.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59301DDD75DAE@dbde02.ent.ti.com>
Premi, Sanjeev had written, on 10/08/2009 09:23 AM, the following:
>> -----Original Message-----
>> From: Pandita, Vikram
>> Sent: Thursday, October 08, 2009 7:01 PM
>> To: Shilimkar, Santosh; Menon, Nishanth; linux-omap
>> Cc: Chikkature Rajashekar, Madhusudhan; Pais, Allen; Gadiyar,
>> Anand; Cousson, Benoit; Kevin Hilman; Premi, Sanjeev; Aguirre
>> Rodriguez, Sergio Alberto; Tony Lindgren
>> Subject: RE: [RFC][PATCH] OMAP3: introduce OMAP3630
>>
>>
>>
>>> -----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.
>
> [sp] This case seems quite similar to the OMAP35x.
> Can you look at this thread:
>
> http://marc.info/?l=linux-omap&m=125372581804902&w=2
>
> It applies equally well here as well...
> I will be submitting updated patch tomorrow.
yes, any specifics should be feature based IMHO. we will need to extend
the feature list.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2009-10-08 14:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PATCH][RFC] OMAP3630: Create architecture macros and config>
2009-10-08 4:47 ` [RFC][PATCH] OMAP3: introduce OMAP3630 Nishanth Menon
2009-10-08 6:17 ` Felipe Balbi
2009-10-08 10:13 ` Shilimkar, Santosh
2009-10-08 13:31 ` Pandita, Vikram
2009-10-08 14:23 ` Premi, Sanjeev
2009-10-08 14:40 ` Nishanth Menon [this message]
2009-10-08 15:04 ` Pais, Allen
2009-10-08 15:13 ` Menon, Nishanth
2009-10-09 4:29 ` Shilimkar, Santosh
2009-10-09 14:09 ` Nishanth Menon
2009-10-09 14:40 ` Shilimkar, Santosh
2009-10-08 14:31 ` Aguirre Rodriguez, Sergio Alberto
2009-10-08 16:08 ` Menon, Nishanth
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=4ACDF9E3.4010701@ti.com \
--to=nm@ti.com \
--cc=allen.pais@ti.com \
--cc=b-cousson@ti.com \
--cc=gadiyar@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=madhu.cr@ti.com \
--cc=premi@ti.com \
--cc=saaguirre@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.com \
--cc=vikram.pandita@ti.com \
/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