linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: Get rid of custom OMAP_32K_TIMER_HZ
Date: Fri, 1 Feb 2013 14:52:02 -0800	[thread overview]
Message-ID: <20130201225202.GI22517@atomide.com> (raw)
In-Reply-To: <1524396.4DaQLsSWOZ@wuerfel>

* Arnd Bergmann <arnd@arndb.de> [130131 07:41]:
> On Thursday 31 January 2013 21:02:00 Santosh Shilimkar wrote:
> > The timekeeping doesn't depend on HZ value in presence of fine grained
> > clocksource and hence there should not be any time drift because of HZ
> > value which was chosen to be divisor of 32768.
> > 
> > OMAP has been using HZ = 128 value to avoid any time drift issues
> > because of 32768 HZ clock. But with various measurements performed
> > with HZ = 100, no time drift is observed and it also proves the
> > point about HZ not having impact on time keeping on OMAP.
> > 
> > Very informative thread on this topic is here:
> >         https://lkml.org/lkml/2013/1/29/435
> > 
> > Special thanks to John Stulz, Arnd Bergmann and Russell King for their
> > valuable suggestions.
> > 
> > Cc: Arnd Bergmann <arnd@arndb.de>
> > Cc: Russell King <linux@arm.linux.org.uk>
> > Cc: John Stultz <john.stultz@linaro.org>
> > Cc: Tony Lindgren <tony@atomide.com>
> 
> Acked-by: Arnd Bergmann <arnd@arndb.de>
> 
> Thanks so much for looking into this!

Great thanks for checking it Santosh! Applying into
omap-for-v3.9/soc.

Tony

  reply	other threads:[~2013-02-01 22:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 15:32 [PATCH] ARM: OMAP2+: Get rid of custom OMAP_32K_TIMER_HZ Santosh Shilimkar
2013-01-31 15:37 ` Arnd Bergmann
2013-02-01 22:52   ` Tony Lindgren [this message]
2013-02-03 12:50 ` Igor Grinberg

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=20130201225202.GI22517@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).