From: Michael Jones <michael.jones@matrix-vision.de>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: timing in driver function
Date: Fri, 05 Aug 2011 14:06:36 +0200 [thread overview]
Message-ID: <4E3BDCCC.3090009@matrix-vision.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1108011931151.28427@utopia.booyaka.com>
Hi Paul,
On 08/02/2011 03:41 AM, Paul Walmsley wrote:
>
> Hi,
>
> On Mon, 1 Aug 2011, Michael Jones wrote:
>
>> I have a function in a driver which takes ~50ms to execute, which I've
>> measured by reading jiffies at the beginning and end. But jiffies only
>> counts at 128Hz on my system, so this was a very coarse measurement. Now
>> I would like to find out more exactly where the time is going inside
>> this function. So my basic question is, what is the best way to measure
>> lapsed time with reasonable resolution on an OMAP?
>>
>> As I had done with the jiffies measurement, what I imagined was
>> inserting lines into my function, sampling the value of some counter at
>> various points within it. This approach is crude but simple and would
>> suffice for my case.
>>
>> Since it must be a very common task, I thought I'd ask here what the
>> recommended approach is. I see a few directions...
>>
>> 1. Using the OMAP's 32kHz timer, which is provided as a "struct
>> clocksource". It seems like what I would want is to call
>> clocksource_32k.read(), but I don't know how to retrieve clocksource_32k.
>
> Consider getnstimeofday(). It's not OMAP-specific; there are several
> examples in the Linux codebase[1]; and if you use a higher-resolution
> clocksource, the resolution should also increase (try disabling
> CONFIG_OMAP_32K_TIMER).
>
>
> 1. http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Ftorvalds%2Flinux-2.6.git&a=search&h=HEAD&st=grep&s=getnstimeofday
>
>
> - Paul
Thanks, I took your suggestion and it served my purpose just fine.
-Michael
MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner, Erhard Meier
prev parent reply other threads:[~2011-08-05 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 15:15 timing in driver function Michael Jones
2011-08-01 15:34 ` Gadiyar, Anand
2011-08-01 16:55 ` C.A, Subramaniam
2011-08-02 1:41 ` Paul Walmsley
2011-08-05 12:06 ` Michael Jones [this message]
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=4E3BDCCC.3090009@matrix-vision.de \
--to=michael.jones@matrix-vision.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox