From: azummo-lists@towertech.it (Alessandro Zummo)
To: Simon Richter <Simon.Richter@hogyros.de>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org,
lm-sensors@lm-sensors.org,
linux-arm-kernel@lists.arm.linux.org.uk,
nslu2-developers@yahoogroups.com
Subject: [lm-sensors] [RFC] RTC subsystem
Date: Wed, 21 Dec 2005 15:07:12 +0000 [thread overview]
Message-ID: <20051221160712.2d322f42@inspiron> (raw)
In-Reply-To: <43A94811.4010704@hogyros.de>
On Wed, 21 Dec 2005 13:18:25 +0100
Simon Richter <Simon.Richter at hogyros.de> wrote:
> > I've posted a proposal for a new RTC subsystem
> > on lkml ( http://lkml.org/lkml/2005/12/20/220 ) .
>
> I agree that there is room for improvement. Do you have a specific
> structure in mind? Specifically,
Hi Simon,
the proposal actually had a fully-working patch attached :)
> - which functions do you believe to be generic,
> - how should multiple RTCs be handled,
In my code, the first rtc that register is bound
to /proc/driver/rtc and /dev/rtc (if those interfaces
are compiled in, as they are all selectable).
The other RTCs are available thru /sys/class/rtc/rtcX
(again, if compiled in).
> - are read-only (radio controlled) RTCs taken care of?
You have full control of which functions you will provide
to the upper layer. Obivously if you try to set the
time on a read-only rtc, you will get an error.
> At present, I don't have time to help the cause, but I can provide
> hosting for a git tree if desired.
Thanks, I'll consider it if the need arises.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Turin, Italy
http://www.towertech.it
WARNING: multiple messages have this Message-ID (diff)
From: Alessandro Zummo <azummo-lists@towertech.it>
To: Simon Richter <Simon.Richter@hogyros.de>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org,
lm-sensors@lm-sensors.org,
linux-arm-kernel@lists.arm.linux.org.uk,
nslu2-developers@yahoogroups.com
Subject: Re: [RFC] RTC subsystem
Date: Wed, 21 Dec 2005 16:07:12 +0100 [thread overview]
Message-ID: <20051221160712.2d322f42@inspiron> (raw)
In-Reply-To: <43A94811.4010704@hogyros.de>
On Wed, 21 Dec 2005 13:18:25 +0100
Simon Richter <Simon.Richter@hogyros.de> wrote:
> > I've posted a proposal for a new RTC subsystem
> > on lkml ( http://lkml.org/lkml/2005/12/20/220 ) .
>
> I agree that there is room for improvement. Do you have a specific
> structure in mind? Specifically,
Hi Simon,
the proposal actually had a fully-working patch attached :)
> - which functions do you believe to be generic,
> - how should multiple RTCs be handled,
In my code, the first rtc that register is bound
to /proc/driver/rtc and /dev/rtc (if those interfaces
are compiled in, as they are all selectable).
The other RTCs are available thru /sys/class/rtc/rtcX
(again, if compiled in).
> - are read-only (radio controlled) RTCs taken care of?
You have full control of which functions you will provide
to the upper layer. Obivously if you try to set the
time on a read-only rtc, you will get an error.
> At present, I don't have time to help the cause, but I can provide
> hosting for a git tree if desired.
Thanks, I'll consider it if the need arises.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Turin, Italy
http://www.towertech.it
next prev parent reply other threads:[~2005-12-21 15:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 21:00 [lm-sensors] [RFC] RTC subsystem Alessandro Zummo
2005-12-20 21:00 ` Alessandro Zummo
2005-12-21 12:18 ` Simon Richter
2005-12-21 15:07 ` Alessandro Zummo [this message]
2005-12-21 15:07 ` Alessandro Zummo
2005-12-21 16:02 ` Simon Richter
2005-12-21 17:41 ` [lm-sensors] " Alessandro Zummo
2005-12-21 17:41 ` Alessandro Zummo
2005-12-21 17:41 ` Alessandro Zummo
2005-12-21 23:18 ` Simon Richter
2005-12-21 23:18 ` Simon Richter
2005-12-22 6:48 ` [lm-sensors] " Alessandro Zummo
2005-12-22 6:48 ` Alessandro Zummo
2005-12-22 6:48 ` Alessandro Zummo
2005-12-26 19:22 ` [lm-sensors] " Alessandro Zummo
2005-12-26 19:22 ` Alessandro Zummo
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=20051221160712.2d322f42@inspiron \
--to=azummo-lists@towertech.it \
--cc=Simon.Richter@hogyros.de \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=lm-sensors@lm-sensors.org \
--cc=nslu2-developers@yahoogroups.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.