Hi,
On Wed, Feb 8, 2012 at 1:21 PM, Dmitry Antipov
wrote:
> On 02/07/2012 02:43 PM, Andrew Richardson wrote:
>
>> I'm experiencing what appears to be a minimum clock resolution issue
>> in using clock_gettime() on a PandaBoard ES running ubuntu.
>
>
> Do you have CONFIG_OMAP_32K_TIMER enabled in
linaro.org
[mailto:linaro-dev-boun...@lists.linaro.org] On Behalf Of John Stultz
Sent: Wednesday, February 08, 2012 6:09 PM
To: Andrew Richardson
Cc: linux-o...@vger.kernel.org; linaro-dev@lists.linaro.org
Subject: Re: Minimum timing resolution in Ubuntu/Linaro on the PandaBoard ES
On Wed, 2012-02-08 at 0
On Wed, 2012-02-08 at 04:32 -0500, Andrew Richardson wrote:
> Ah, very interesting.
> > dmesg | grep clock
> [0.00] OMAP clockevent source: GPTIMER1 at 32768 Hz
> [0.00] sched_clock: 32 bits at 32kHz, resolution
> 30517ns, wraps every 131071999ms
Hr
On Wed, 2012-02-08 at 04:32 -0500, Andrew Richardson wrote:
> Ah, very interesting.
> > dmesg | grep clock
> [0.00] OMAP clockevent source: GPTIMER1 at 32768 Hz
> [0.00] sched_clock: 32 bits at 32kHz, resolution
> 30517ns, wraps every 131071999ms
Hr
On Tue, 2012-02-07 at 21:21 -0800, Dmitry Antipov wrote:
> BTW, I have no ideas why clock_getres(CLOCK_REALTIME,...) returns {0, 1}
> regardless of underlying clock source. I expect {0, 30517} for 32K timer
> and {0, 26} for MPU timer.
Yea. I had proposed to export the underlying clocksource's res
Ah, very interesting.
> dmesg | grep clock
[0.00] OMAP clockevent source: GPTIMER1 at 32768 Hz
[0.00] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every
131071999ms
[0.309448] omap_hwmod: l4_div_ck: missing clockdomain for l4_div_ck.
[0.716979] Skipping twl int
On Feb 8, 2012, at 8:55 AM, Dmitry Antipov wrote:
> On 02/08/2012 01:32 AM, Andrew Richardson wrote:
>
>> Do you recommend using "Get linaro image tools: method 2 (source code)"
>> ( http://releases.linaro.org/12.01/ubuntu/leb-panda/ ) and building the
>> kernel myself?
>
> Unfortunately this i
On Feb 8, 2012, at 8:55 AM, Dmitry Antipov wrote:
> On 02/08/2012 01:32 AM, Andrew Richardson wrote:
>
>> Do you recommend using "Get linaro image tools: method 2 (source code)"
>> ( http://releases.linaro.org/12.01/ubuntu/leb-panda/ ) and building the
>> kernel myself?
>
> Unfortunately this i
On 02/07/2012 02:43 PM, Somebody in the thread at some point said:
Hi -
> I'm experiencing what appears to be a minimum clock resolution issue in
> using clock_gettime() on a PandaBoard ES running ubuntu.
Actually this is a known problem
https://bugs.launchpad.net/linaro-landing-team-ti/+bug/87
On 02/08/2012 01:32 AM, Andrew Richardson wrote:
Do you recommend using "Get linaro image tools: method 2 (source code)"
( http://releases.linaro.org/12.01/ubuntu/leb-panda/ ) and building the
kernel myself?
Unfortunately this is the only way. In theory, there are clocksource=
boot option, and
On Feb 7, 2012, at 7:30 PM, John Stultz wrote:
> On Wed, 2012-02-08 at 00:16 +0100, Zygmunt Krynicki wrote:
>> On 02/07/2012 11:43 PM, Andrew Richardson wrote:
>>
>> Which clock_t were you using? I think CLOCK_MONOTONIC makes sense for
>> what you are trying to do and perhaps it has different res
On 02/07/2012 02:43 PM, Andrew Richardson wrote:
I'm experiencing what appears to be a minimum clock resolution issue
in using clock_gettime() on a PandaBoard ES running ubuntu.
Do you have CONFIG_OMAP_32K_TIMER enabled in your kernel?
Look at 'dmesg | grep clock' and check for the following:
On Tue, 2012-02-07 at 20:21 -0500, Andrew Richardson wrote:
> On Feb 7, 2012, at 7:30 PM, John Stultz wrote:
> > On Wed, 2012-02-08 at 00:16 +0100, Zygmunt Krynicki wrote:
> > Hrm. No, that shouldn't be the case. CLOCK_MONOTONIC and
> > CLOCK_REALTIME
> > are driven by the same accumulation, and ar
On Wed, 2012-02-08 at 00:16 +0100, Zygmunt Krynicki wrote:
> On 02/07/2012 11:43 PM, Andrew Richardson wrote:
> > Greetings,
> >
> > I'm experiencing what appears to be a minimum clock resolution issue in
> > using clock_gettime() on a PandaBoard ES running ubuntu.
> >
> > *> uname -r*
> >
I was using CLOCK_MONOTONIC_RAW before. I just tried CLOCK_MONOTONIC and
CLOCK_REALTIME and did not see any improvement when timing 2-3ms events.
Andrew
On 12-02-07 06:16 PM, Zygmunt Krynicki wrote:
On 02/07/2012 11:43 PM, Andrew Richardson wrote:
Greetings,
I'm experiencing what appears t
On 02/07/2012 11:43 PM, Andrew Richardson wrote:
Greetings,
I'm experiencing what appears to be a minimum clock resolution issue in
using clock_gettime() on a PandaBoard ES running ubuntu.
*> uname -r*
3.1.1-8-linaro-lt-omap
*> cat /proc/version*
Linux version 3.1.1-8-linaro-lt
16 matches
Mail list logo
