From: David Brownell <david-b@pacbell.net>
To: Philippe De Muyter <phdm@macqel.be>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Alessandro Zummo <alessandro.zummo@towertech.it>
Subject: Re: RTC subsystem and fractions of seconds
Date: Sun, 7 Jan 2007 18:10:30 -0800 [thread overview]
Message-ID: <200701071810.30310.david-b@pacbell.net> (raw)
In-Reply-To: <20070107101449.GA24163@ingate.macqel.be>
On Sunday 07 January 2007 2:14 am, Philippe De Muyter wrote:
> On Fri, Jan 05, 2007 at 07:49:00PM -0800, David Brownell wrote:
> > > Those rtc's actually have a 1/100th of second
> > > register. Should the generic rtc interface not support that?
> >
> > Are you implying a new userspace API, or just an in-kernel update?
> >
> > Either way, that raises the question of what other features should
> > be included. What sub-second precision? Multiple alarms? Ways
> > to manage output clocks? Sub-HZ periodic alarms?
>
> One usefull addition for my needs and with a m41t81 is the support of
> the calibration of the rtc. However this can perhaps be hidden in the
> .set_mmss function.
Doesn't seem like an set_mmss() mechanism at all. Some drivers give
sysfs access to an oscillator "trim" mechanism. What tools do you
have which track how far off that crystal is?
- Dave
next prev parent reply other threads:[~2007-01-08 2:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 3:49 RTC subsystem and fractions of seconds David Brownell
2007-01-06 23:26 ` Philippe De Muyter
2007-01-06 23:52 ` David Brownell
2007-01-07 1:11 ` Hugh Dickins
2007-01-07 2:54 ` David Brownell
2007-01-07 9:43 ` Hugh Dickins
2007-01-07 10:02 ` Philippe De Muyter
2007-01-07 10:14 ` Philippe De Muyter
2007-01-08 2:10 ` David Brownell [this message]
2007-01-08 10:25 ` Philippe De Muyter
-- strict thread matches above, loose matches on Subject: below --
2007-01-07 22:31 Philippe De Muyter
2007-01-06 2:29 Philippe De Muyter
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=200701071810.30310.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=alessandro.zummo@towertech.it \
--cc=linux-kernel@vger.kernel.org \
--cc=phdm@macqel.be \
/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.