From: tony@atomide.com
To: imre.deak@solidboot.com
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] ARM: OMAP: timer32k: fix tick count calculation when reprogramming
Date: Wed, 5 Jul 2006 01:51:04 -0700 [thread overview]
Message-ID: <20060705085059.GC4546@atomide.com> (raw)
In-Reply-To: <20060703155155.GA29815@localdomain>
* imre.deak@solidboot.com <imre.deak@solidboot.com> [060703 08:51]:
> Reprogramming takes places before putting the CPU into idle mode if
> the dynamic tick option is enabled. The timer is then set to expire
> at the next pending timer event. Because some time has already passed
> since the last reported jiffy we have to wait less than the time
> specified in jiffies.
Looks good to me. This patch seems to need an update though.
Did you do this to fix some specific problem, or just to improve timer
accuracy?
> Also make sure we don't set a load value of 0 whose outcome is
> unspecified according to the TRM.
OK
Tony
next prev parent reply other threads:[~2006-07-05 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 15:51 [PATCH] ARM: OMAP: timer32k: fix tick count calculation when reprogramming imre.deak
2006-07-05 8:51 ` tony [this message]
2006-07-05 15:58 ` imre.deak
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=20060705085059.GC4546@atomide.com \
--to=tony@atomide.com \
--cc=imre.deak@solidboot.com \
--cc=linux-omap-open-source@linux.omap.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.