From: David Woodhouse <dwmw2@infradead.org>
To: Alessandro Zummo <a.zummo@towertech.it>
Cc: David Brownell <david-b@pacbell.net>,
linuxppc-dev@ozlabs.org, Paul Mundt <lethal@linux-sh.org>,
rtc-linux@googlegroups.com
Subject: Re: [RFC PATCH] rtc: add rtc_systohc for ntp use
Date: Tue, 11 Nov 2008 14:10:39 +0000 [thread overview]
Message-ID: <1226412639.4367.256.camel@macbook.infradead.org> (raw)
In-Reply-To: <20081110154026.21405.47457.stgit@i1501.lan.towertech.it>
On Mon, 2008-11-10 at 16:40 +0100, Alessandro Zummo wrote:
> Adds in-kernel hctosys functionality that can
> be used by ntp sync code.
>
> This is an RFC and has not been tested, I just want
> to check if something similar could solve the problems
> of those who want the NTP sync mode.
You might do better to open the device once and keep it open, rather
than taking the mutex and opening it again _during_ each call? You're
going to be perturbing the timing by doing that.
I believe you were also concerned that some device wouldn't want the
behaviour given by the existing sync_cmos_clock() function and workqueue
stuff in kernel/ntp.c, where we update the clock precisely half-way
through the second?
We should probably rip that code out of ntp.c (or just disable it ifdef
CONFIG_RTC_CLASS), and provide our own version of notify_cmos_timer().
The workqueue stuff to trigger at half-past the second could be kept as
a library function which most RTC devices would use, but they'd have the
option to use their own instead.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2008-11-11 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 15:40 [RFC PATCH] rtc: add rtc_systohc for ntp use Alessandro Zummo
2008-11-10 22:57 ` David Brownell
2008-11-10 23:05 ` Alessandro Zummo
2008-11-11 14:10 ` David Woodhouse [this message]
2008-11-11 17:17 ` Gabriel Paubert
2008-11-11 18:11 ` [rtc-linux] " Alessandro Zummo
2008-11-11 20:58 ` David Brownell
2008-11-12 8:05 ` Gabriel Paubert
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=1226412639.4367.256.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=a.zummo@towertech.it \
--cc=david-b@pacbell.net \
--cc=lethal@linux-sh.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rtc-linux@googlegroups.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;
as well as URLs for NNTP newsgroup(s).