From: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Alessandro Rubini <rubini@unipv.it>,
Bryan Huntsman <bryanh@codeaurora.org>,
Daniel Walker <dwalker@codeaurora.org>,
David Brown <davidb@codeaurora.org>,
Eric Miao <eric.y.miao@gmail.com>,
"Hans J. Koch" <hjk@linutronix.de>,
Imre Kaloz <kaloz@openwrt.org>,
Kevin Hilman <khilman@deeprootsystems.com>,
Krzysztof Halasa <khc@pm.waw.pl>,
Kukjin Kim <kgene.kim@samsung.com>,
Lennert Buytenhek <kernel@wantstofly.org>,
Leo Chen <leochen@broadcom.com>,
Linus Walleij <linus.walleij@stericsson.com>,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-omap@vger.kernel.org,
linux-samsung-soc@vger.kernel.org,
Nicolas Pitre <nico@fluxnic.net>,
Sascha Hauer <kernel@pengutronix.de>,
Scott Branden <sbranden@broadcom.com>,
STEricsson <STEricsson_nomadik_linux@list.st.com>,
Tony Lindgren <tony@atomide.com>,
Viresh Kumar <viresh.kumar@st.com>, Wan ZongShun <mcuo>
Subject: [PATCH 0/24] Update clocksource registration
Date: Mon, 13 Dec 2010 19:14:37 +0000 [thread overview]
Message-ID: <20101213191437.GN8665@n2100.arm.linux.org.uk> (raw)
John Stultz notes in his commit:
clocksource: Add clocksource_register_hz/khz interface
How to pick good mult/shift pairs has always been difficult to
describe to folks writing clocksource drivers, since it requires
careful tradeoffs in adjustment accuracy vs overflow limits.
Now, with the clocks_calc_mult_shift function, its much
easier. However, not many clocksources have converted to using that
function, and there is still the issue of the max interval length
assumption being made by each clocksource driver independently.
So this patch simplifies the registration process by having
clocksources be registered with a hz/khz value and the registration
function taking care of setting mult/shift.
This should take most of the confusion out of writing a clocksource
driver.
Additionally it also keeps the shift size tradeoff (more accuracy vs
longer possible nohz times) centralized so the timekeeping core can
keep track of the assumptions being made.
This patch series updates all ARM platforms clocksource registration
to use the new clocksource_register_hz()/clocksource_register_khz()
functions, simplifying the selection of the multiply/shift constants.
next reply other threads:[~2010-12-13 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 19:14 Russell King - ARM Linux [this message]
2010-12-13 19:19 ` [PATCH 13/24] ARM: s5pv310: update clock source registration Russell King - ARM Linux
2010-12-17 4:49 ` Kukjin Kim
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=20101213191437.GN8665@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=STEricsson_nomadik_linux@list.st.com \
--cc=bryanh@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=dwalker@codeaurora.org \
--cc=eric.y.miao@gmail.com \
--cc=hjk@linutronix.de \
--cc=kaloz@openwrt.org \
--cc=kernel@pengutronix.de \
--cc=kernel@wantstofly.org \
--cc=kgene.kim@samsung.com \
--cc=khc@pm.waw.pl \
--cc=khilman@deeprootsystems.com \
--cc=leochen@broadcom.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=rubini@unipv.it \
--cc=sbranden@broadcom.com \
--cc=tony@atomide.com \
--cc=viresh.kumar@st.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