From: Jonathan Cameron <jic23@cam.ac.uk>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Paul Walmsley <paul@pwsan.com>,
"linux-omap@vger.kernel.org List" <linux-omap@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] omap3: beagle: Use GPTIMERi 1 for clockevents
Date: Mon, 27 Jun 2011 13:32:25 +0100 [thread overview]
Message-ID: <4E087859.5010901@cam.ac.uk> (raw)
In-Reply-To: <DE79F8F5-7D8A-46B8-8C8C-C2A7515E9117@dominion.thruhere.net>
On 06/25/11 21:10, Koen Kooi wrote:
>
> Op 25 jun 2011, om 20:51 heeft Premi, Sanjeev het volgende geschreven:
>
>>> -----Original Message-----
>>> From: linux-omap-owner@vger.kernel.org
>>> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Koen Kooi
>>> Sent: Saturday, June 25, 2011 1:47 PM
>>> To: linux-omap@vger.kernel.org List
>>> Cc: linux-arm-kernel; Paul Walmsley
>>> Subject: Re: [PATCH] omap3: beagle: Use GPTIMERi 1 for clockevents
>>>
>>>
>>> Op 24 jun 2011, om 18:23 heeft Sanjeev Premi het volgende geschreven:
>>>
>>>> The current selection of the GPTIMER on was result of
>>>> a hardware issue in early versions of the Beagleboards
>>>> (Ax and B1 thru B4). [1] [2]
>>>>
>>>> Its been long since the hardware issue has been fixed.
>>>> This patch uses GPTIMER 1 for all newer board revisions
>>>> incl. Beagleboard XM.
>>
>> [sp] I didn't include a reason - because the problem may not
>> be reproducible on the public trees.
>>
>> During tests performed in internal development trees, the
>> BogoMIPS calculations @ 1GHz wouldn't go beyond "830-850"
>> range. While there was no such inconsistency on OMAP3EVM.
>>
>> After few days of debug GPTIMER12 came to be only difference.
>> Tracing GPTIMER12 in the spec proved quite a challenge; the
>> as timer is not included in the TRM and corresponding interrupt
>> is marked reserved. Paul (in cc:) obviously had access to
>> documents that we don't.
>>
>> This patch is merely trying to bring parity in use of GPTIMER
>> across OMAP3 boards (AND use documented IP) - taking note of
>> many Beagleboards where current code is necessary.
>
> I get a value of 1010 ±10 bogoMIPS consistently with .39 + dvfs
> patches. Having said that, this patch does seem to be an improvement,
> but has it actually been tested on real beagleboard hardware with a
> recent kernel? Especially on the boards affected by the capacitor
> issue on the external clock.--
Hi Koen,
Probably obvious to anyone else here, but which dvfs patches?
I've only recently acquired an xm and hence wasn't following these threads.
Don't suppose you could point me to a tree with them in or the relevant
thread?
Cheers,
Jonathan
WARNING: multiple messages have this Message-ID (diff)
From: jic23@cam.ac.uk (Jonathan Cameron)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] omap3: beagle: Use GPTIMERi 1 for clockevents
Date: Mon, 27 Jun 2011 13:32:25 +0100 [thread overview]
Message-ID: <4E087859.5010901@cam.ac.uk> (raw)
In-Reply-To: <DE79F8F5-7D8A-46B8-8C8C-C2A7515E9117@dominion.thruhere.net>
On 06/25/11 21:10, Koen Kooi wrote:
>
> Op 25 jun 2011, om 20:51 heeft Premi, Sanjeev het volgende geschreven:
>
>>> -----Original Message-----
>>> From: linux-omap-owner at vger.kernel.org
>>> [mailto:linux-omap-owner at vger.kernel.org] On Behalf Of Koen Kooi
>>> Sent: Saturday, June 25, 2011 1:47 PM
>>> To: linux-omap at vger.kernel.org List
>>> Cc: linux-arm-kernel; Paul Walmsley
>>> Subject: Re: [PATCH] omap3: beagle: Use GPTIMERi 1 for clockevents
>>>
>>>
>>> Op 24 jun 2011, om 18:23 heeft Sanjeev Premi het volgende geschreven:
>>>
>>>> The current selection of the GPTIMER on was result of
>>>> a hardware issue in early versions of the Beagleboards
>>>> (Ax and B1 thru B4). [1] [2]
>>>>
>>>> Its been long since the hardware issue has been fixed.
>>>> This patch uses GPTIMER 1 for all newer board revisions
>>>> incl. Beagleboard XM.
>>
>> [sp] I didn't include a reason - because the problem may not
>> be reproducible on the public trees.
>>
>> During tests performed in internal development trees, the
>> BogoMIPS calculations @ 1GHz wouldn't go beyond "830-850"
>> range. While there was no such inconsistency on OMAP3EVM.
>>
>> After few days of debug GPTIMER12 came to be only difference.
>> Tracing GPTIMER12 in the spec proved quite a challenge; the
>> as timer is not included in the TRM and corresponding interrupt
>> is marked reserved. Paul (in cc:) obviously had access to
>> documents that we don't.
>>
>> This patch is merely trying to bring parity in use of GPTIMER
>> across OMAP3 boards (AND use documented IP) - taking note of
>> many Beagleboards where current code is necessary.
>
> I get a value of 1010 ?10 bogoMIPS consistently with .39 + dvfs
> patches. Having said that, this patch does seem to be an improvement,
> but has it actually been tested on real beagleboard hardware with a
> recent kernel? Especially on the boards affected by the capacitor
> issue on the external clock.--
Hi Koen,
Probably obvious to anyone else here, but which dvfs patches?
I've only recently acquired an xm and hence wasn't following these threads.
Don't suppose you could point me to a tree with them in or the relevant
thread?
Cheers,
Jonathan
next prev parent reply other threads:[~2011-06-27 12:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 16:23 [PATCH] omap3: beagle: Use GPTIMERi 1 for clockevents Sanjeev Premi
2011-06-24 16:23 ` Sanjeev Premi
2011-06-24 16:32 ` Premi, Sanjeev
2011-06-24 16:32 ` Premi, Sanjeev
2011-06-25 8:16 ` Koen Kooi
2011-06-25 8:16 ` Koen Kooi
2011-06-25 18:51 ` Premi, Sanjeev
2011-06-25 18:51 ` Premi, Sanjeev
2011-06-25 20:10 ` Koen Kooi
2011-06-25 20:10 ` Koen Kooi
2011-06-27 4:45 ` Premi, Sanjeev
2011-06-27 4:45 ` Premi, Sanjeev
2011-06-27 12:32 ` Jonathan Cameron [this message]
2011-06-27 12:32 ` Jonathan Cameron
2011-06-25 22:47 ` Paul Walmsley
2011-06-25 22:47 ` Paul Walmsley
2011-06-27 4:47 ` Premi, Sanjeev
2011-06-27 4:47 ` Premi, Sanjeev
2011-06-27 10:14 ` Tony Lindgren
2011-06-27 10:14 ` Tony Lindgren
2011-06-27 15:29 ` Paul Walmsley
2011-06-27 15:29 ` Paul Walmsley
2011-06-27 15:40 ` Premi, Sanjeev
2011-06-27 15:40 ` Premi, Sanjeev
2011-06-27 16:55 ` Paul Walmsley
2011-06-27 16:55 ` Paul Walmsley
2011-06-27 18:03 ` Tony Lindgren
2011-06-27 18:03 ` Tony Lindgren
2011-06-25 22:49 ` Paul Walmsley
2011-06-25 22:49 ` Paul Walmsley
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=4E087859.5010901@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=koen@dominion.thruhere.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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 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.