* OMAP3505 revisions?
@ 2011-09-13 18:03 Paul Walmsley
2011-09-14 9:49 ` Premi, Sanjeev
2011-09-14 11:29 ` Premi, Sanjeev
0 siblings, 2 replies; 9+ messages in thread
From: Paul Walmsley @ 2011-09-13 18:03 UTC (permalink / raw)
To: Sanjeev Premi; +Cc: notasas, tony, linux-omap
Hi Sanjeev
Am looking at your commit 4cac6018, which touches
arch/arm/mach-omap2/id.c. That commit implements SoC detection for the
3505 in a different way than the implementations for other OMAP2+ devices:
it doesn't enumerate the possible TAP revisions for OMAP3505. The TRM
doesn't seem to list those, either. And unfortunately that is blocking
some of the omap_chip removal work.
Could you send me a list of the possible revision values for the
3505/3517, along with mappings to ES levels, please?
thanks
- Paul
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: OMAP3505 revisions?
2011-09-13 18:03 OMAP3505 revisions? Paul Walmsley
@ 2011-09-14 9:49 ` Premi, Sanjeev
2011-09-14 11:40 ` Paul Walmsley
2011-09-14 11:29 ` Premi, Sanjeev
1 sibling, 1 reply; 9+ messages in thread
From: Premi, Sanjeev @ 2011-09-14 9:49 UTC (permalink / raw)
To: Paul Walmsley; +Cc: notasas, tony, linux-omap
Paul,
Looks like I was unsubscribed from linux-omap sometime last week.
Why? no idea!
Anyways, I just looked at your mails. Will be responding with
details in next hour. Will also attempt to re-subscribe in meantime.
~sanjeev
> -----Original Message-----
> From: Paul Walmsley [mailto:paul@pwsan.com]
> Sent: Tuesday, September 13, 2011 11:33 PM
> To: Premi, Sanjeev
> Cc: notasas@gmail.com; tony@atomide.com; linux-omap@vger.kernel.org
> Subject: OMAP3505 revisions?
>
>
> Hi Sanjeev
>
> Am looking at your commit 4cac6018, which touches
> arch/arm/mach-omap2/id.c. That commit implements SoC
> detection for the
> 3505 in a different way than the implementations for other
> OMAP2+ devices:
> it doesn't enumerate the possible TAP revisions for OMAP3505.
> The TRM
> doesn't seem to list those, either. And unfortunately that
> is blocking
> some of the omap_chip removal work.
>
> Could you send me a list of the possible revision values for the
> 3505/3517, along with mappings to ES levels, please?
>
> thanks
>
> - Paul
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: OMAP3505 revisions?
2011-09-13 18:03 OMAP3505 revisions? Paul Walmsley
2011-09-14 9:49 ` Premi, Sanjeev
@ 2011-09-14 11:29 ` Premi, Sanjeev
2011-09-14 11:46 ` Paul Walmsley
1 sibling, 1 reply; 9+ messages in thread
From: Premi, Sanjeev @ 2011-09-14 11:29 UTC (permalink / raw)
To: Paul Walmsley; +Cc: notasas, tony, linux-omap
> -----Original Message-----
> From: Paul Walmsley [mailto:paul@pwsan.com]
> Sent: Tuesday, September 13, 2011 11:33 PM
> To: Premi, Sanjeev
> Cc: notasas@gmail.com; tony@atomide.com; linux-omap@vger.kernel.org
> Subject: OMAP3505 revisions?
>
>
> Hi Sanjeev
>
> Am looking at your commit 4cac6018, which touches
> arch/arm/mach-omap2/id.c. That commit implements SoC
> detection for the
> 3505 in a different way than the implementations for other
> OMAP2+ devices:
> it doesn't enumerate the possible TAP revisions for OMAP3505.
> The TRM
Paul,
In the function omap3_check_revision(), the revision is being
extracted from the TAP register for AM3505/AM3517 devices thru
same code used for OMAP34xx registers.
OR, Am I missing something?
~sanjeev
> doesn't seem to list those, either. And unfortunately that
> is blocking
> some of the omap_chip removal work.
>
> Could you send me a list of the possible revision values for the
> 3505/3517, along with mappings to ES levels, please?
>
> thanks
>
> - Paul
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: OMAP3505 revisions?
2011-09-14 9:49 ` Premi, Sanjeev
@ 2011-09-14 11:40 ` Paul Walmsley
2011-09-14 11:57 ` Premi, Sanjeev
0 siblings, 1 reply; 9+ messages in thread
From: Paul Walmsley @ 2011-09-14 11:40 UTC (permalink / raw)
To: Premi, Sanjeev; +Cc: notasas, tony, linux-omap
On Wed, 14 Sep 2011, Premi, Sanjeev wrote:
> Looks like I was unsubscribed from linux-omap sometime last week.
> Why? no idea!
Bummer.
> Anyways, I just looked at your mails. Will be responding with
> details in next hour. Will also attempt to re-subscribe in meantime.
Thanks. Could you try a test boot of the 'id_3517_cleanup_3.2' branch of
git://git.pwsan.com/linux-2.6 on an AM3517/3505, or ask someone to try
that out?
thanks,
- Paul
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: OMAP3505 revisions?
2011-09-14 11:29 ` Premi, Sanjeev
@ 2011-09-14 11:46 ` Paul Walmsley
0 siblings, 0 replies; 9+ messages in thread
From: Paul Walmsley @ 2011-09-14 11:46 UTC (permalink / raw)
To: Premi, Sanjeev; +Cc: notasas, tony, linux-omap
Hi Sanjeev,
On Wed, 14 Sep 2011, Premi, Sanjeev wrote:
> > -----Original Message-----
> > From: Paul Walmsley [mailto:paul@pwsan.com]
> >
> > Am looking at your commit 4cac6018, which touches
> > arch/arm/mach-omap2/id.c. That commit implements SoC
> > detection for the
> > 3505 in a different way than the implementations for other
> > OMAP2+ devices:
> > it doesn't enumerate the possible TAP revisions for OMAP3505.
> > The TRM
>
> In the function omap3_check_revision(), the revision is being
> extracted from the TAP register for AM3505/AM3517 devices thru
> same code used for OMAP34xx registers.
>
> OR, Am I missing something?
Sorry, my original message was not clear. In omap3_check_revision(), it
does this for 3517/3505:
omap_revision = OMAP3505_REV(rev);
but for other chips, it does something like this:
omap_revision = OMAP3430_REV_ES3_1_2;
The main point being that, with the latter, all of the possible values for
omap_revision for OMAP3430 are known.
But after I sent that message, I realized that some of the duplicate
testing code in omap3_cpuinfo() did enumerate revisions for 3517/3505:
ES1.0 and ES1.1. So I've used that instead in the patch series that I
sent. If there are others beyond those two, please let us know...
Thanks for the quick response.
- Paul
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: OMAP3505 revisions?
2011-09-14 11:40 ` Paul Walmsley
@ 2011-09-14 11:57 ` Premi, Sanjeev
2011-09-14 13:49 ` Paul Walmsley
0 siblings, 1 reply; 9+ messages in thread
From: Premi, Sanjeev @ 2011-09-14 11:57 UTC (permalink / raw)
To: Paul Walmsley; +Cc: notasas, tony, linux-omap
> -----Original Message-----
> From: Paul Walmsley [mailto:paul@pwsan.com]
> Sent: Wednesday, September 14, 2011 5:11 PM
> To: Premi, Sanjeev
> Cc: notasas@gmail.com; tony@atomide.com; linux-omap@vger.kernel.org
> Subject: RE: OMAP3505 revisions?
>
> On Wed, 14 Sep 2011, Premi, Sanjeev wrote:
>
> > Looks like I was unsubscribed from linux-omap sometime last week.
> > Why? no idea!
>
> Bummer.
>
> > Anyways, I just looked at your mails. Will be responding with
> > details in next hour. Will also attempt to re-subscribe in meantime.
>
> Thanks. Could you try a test boot of the
> 'id_3517_cleanup_3.2' branch of
> git://git.pwsan.com/linux-2.6 on an AM3517/3505, or ask
> someone to try
> that out?
Sure I will get this tested.
~sanjeev
>
> thanks,
>
> - Paul
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: OMAP3505 revisions?
2011-09-14 11:57 ` Premi, Sanjeev
@ 2011-09-14 13:49 ` Paul Walmsley
2011-09-14 13:51 ` Premi, Sanjeev
0 siblings, 1 reply; 9+ messages in thread
From: Paul Walmsley @ 2011-09-14 13:49 UTC (permalink / raw)
To: Premi, Sanjeev; +Cc: notasas, tony, Igor Grinberg, linux-omap
On Wed, 14 Sep 2011, Premi, Sanjeev wrote:
> > -----Original Message-----
> > From: Paul Walmsley [mailto:paul@pwsan.com]
> > Sent: Wednesday, September 14, 2011 5:11 PM
> > To: Premi, Sanjeev
> > Cc: notasas@gmail.com; tony@atomide.com; linux-omap@vger.kernel.org
> > Subject: RE: OMAP3505 revisions?
> >
> > Thanks. Could you try a test boot of the 'id_3517_cleanup_3.2' branch
> > of git://git.pwsan.com/linux-2.6 on an AM3517/3505, or ask someone to
> > try that out?
>
> Sure I will get this tested.
I just repushed this branch with changes to fix a bug that Igor found.
If you've pulled it already, could you re-pull? I'm particularly
interested in a test on a 3505 board.
- Paul
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: OMAP3505 revisions?
2011-09-14 13:49 ` Paul Walmsley
@ 2011-09-14 13:51 ` Premi, Sanjeev
2011-09-14 16:34 ` Koyamangalath, Abhilash
0 siblings, 1 reply; 9+ messages in thread
From: Premi, Sanjeev @ 2011-09-14 13:51 UTC (permalink / raw)
To: Paul Walmsley; +Cc: notasas, tony, Igor Grinberg, linux-omap
> -----Original Message-----
> From: Paul Walmsley [mailto:paul@pwsan.com]
> Sent: Wednesday, September 14, 2011 7:19 PM
> To: Premi, Sanjeev
> Cc: notasas@gmail.com; tony@atomide.com; Igor Grinberg;
> linux-omap@vger.kernel.org
> Subject: RE: OMAP3505 revisions?
>
> On Wed, 14 Sep 2011, Premi, Sanjeev wrote:
>
> > > -----Original Message-----
> > > From: Paul Walmsley [mailto:paul@pwsan.com]
> > > Sent: Wednesday, September 14, 2011 5:11 PM
> > > To: Premi, Sanjeev
> > > Cc: notasas@gmail.com; tony@atomide.com;
> linux-omap@vger.kernel.org
> > > Subject: RE: OMAP3505 revisions?
> > >
> > > Thanks. Could you try a test boot of the
> 'id_3517_cleanup_3.2' branch
> > > of git://git.pwsan.com/linux-2.6 on an AM3517/3505, or
> ask someone to
> > > try that out?
> >
> > Sure I will get this tested.
>
> I just repushed this branch with changes to fix a bug that
> Igor found.
> If you've pulled it already, could you re-pull? I'm particularly
> interested in a test on a 3505 board.
[sp] The pull is in progress (... bit slow).
Not sure if we have a AM3505 board, but it can be simulated.
~sanjeev
>
>
> - Paul
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: OMAP3505 revisions?
2011-09-14 13:51 ` Premi, Sanjeev
@ 2011-09-14 16:34 ` Koyamangalath, Abhilash
0 siblings, 0 replies; 9+ messages in thread
From: Koyamangalath, Abhilash @ 2011-09-14 16:34 UTC (permalink / raw)
To: Premi, Sanjeev, Paul Walmsley; +Cc: notasas, tony, Igor Grinberg, linux-omap
Hi Paul
On Wed, Sep 14, 2011 at 7:21 PM, Premi, Sanjeev wrote:
>
> ________________________________________
>> -----Original Message-----
>> From: Paul Walmsley [mailto:paul@pwsan.com]
>> Sent: Wednesday, September 14, 2011 7:19 PM
>> To: Premi, Sanjeev
>> Cc: notasas@gmail.com; tony@atomide.com; Igor Grinberg;
>> linux-omap@vger.kernel.org
>> Subject: RE: OMAP3505 revisions?
>>
>> On Wed, 14 Sep 2011, Premi, Sanjeev wrote:
>>
>> > > -----Original Message-----
>> > > From: Paul Walmsley [mailto:paul@pwsan.com]
>> > > Sent: Wednesday, September 14, 2011 5:11 PM
>> > > To: Premi, Sanjeev
>> > > Cc: notasas@gmail.com; tony@atomide.com;
>> linux-omap@vger.kernel.org
>> > > Subject: RE: OMAP3505 revisions?
>> > >
>> > > Thanks. Could you try a test boot of the
>> 'id_3517_cleanup_3.2' branch
>> > > of git://git.pwsan.com/linux-2.6 on an AM3517/3505, or
>> ask someone to
>> > > try that out?
>> >
>> > Sure I will get this tested.
[Abhilash K V] I just tried this branch on a AM3517 and it boots after
applying this patch-set:
http://marc.info/?l=linux-omap&m=131410578024030&w=2
- Abhilash
>>
>> I just repushed this branch with changes to fix a bug that
>> Igor found.
>> If you've pulled it already, could you re-pull? I'm particularly
>> interested in a test on a 3505 board.
>
> [sp] The pull is in progress (... bit slow).
> Not sure if we have a AM3505 board, but it can be simulated.
>
> ~sanjeev
>
>>
>>
>> - Paul
>> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2011-09-14 16:36 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-09-13 18:03 OMAP3505 revisions? Paul Walmsley
2011-09-14 9:49 ` Premi, Sanjeev
2011-09-14 11:40 ` Paul Walmsley
2011-09-14 11:57 ` Premi, Sanjeev
2011-09-14 13:49 ` Paul Walmsley
2011-09-14 13:51 ` Premi, Sanjeev
2011-09-14 16:34 ` Koyamangalath, Abhilash
2011-09-14 11:29 ` Premi, Sanjeev
2011-09-14 11:46 ` Paul Walmsley
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.