From: Richard Cochran <richardcochran@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-api@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Arnd Bergmann <arnd@arndb.de>, Christoph Lameter <cl@linux.com>,
John Stultz <johnstul@us.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH RFC 0/8] Dynamic clock devices
Date: Thu, 4 Nov 2010 20:26:34 +0100 [thread overview]
Message-ID: <cover.1288897198.git.richard.cochran@omicron.at> (raw)
Okay, here is a work in progress, not well tested, but I would like to
get some feedback whether the direction is good or not.
The first patch introduces clock devices which can appear and
disappear like usb devices (and, I suppose, hot plug PCI but I am not
too sure that what is offered here would really work in that case).
The subsequent patches convert the clock_ and timer_ system calls, one
by one.
The clock_ syscalls are moved into a new file and they call the older
posix functions when needed. The timer_ syscalls stay where they are,
in posix-timers.c, since I did not want to change the fairly involved
timer management code. Eventually, we could remove the posix clock_*
functions for the CLOCK_* ids from posix-timers.c and rework them
using the new dynamic clock api. That would leave just the timer code
in posix-timers.c, as the file name suggests.
I dropped the idea of having user space open a sysfs file in order to
get a reference to a clock, since there are no open/release hooks
within sysfs for drivers (coincidentally, there has been some talk
about this on the lkml recently, but previously Greg KH object to
abusing sysfs as a "clockfs").
Instead, since many clocks (hpet, rtc, ptp, ...) will want to offer a
custom chardev for special advanced functionality, the dynamic clock
layer registers a cdev for the driver, placing its own hooks into the
open/release methods. The driver thus needs to access its private data
via a standard access method (not just by using fp->private_data). If
a driver doesn't want any chardev functions, that is okay, too.
Well, please take a look and let me know what you think.
Thanks,
Richard
Richard Cochran (8):
Introduce dynamic clock devices
clock device: convert clock_gettime
clock device: convert clock_getres
clock device: convert clock_settime
clock device: convert timer_create
clock device: convert timer_delete
clock device: convert timer_gettime
clock device: convert timer_settime
include/linux/clockdevice.h | 117 +++++++++++++++
include/linux/posix-timers.h | 23 +++-
include/linux/time.h | 2 +
kernel/posix-timers.c | 51 +++++--
kernel/time/Makefile | 3 +-
kernel/time/clockdevice.c | 336 ++++++++++++++++++++++++++++++++++++++++++
6 files changed, 518 insertions(+), 14 deletions(-)
create mode 100644 include/linux/clockdevice.h
create mode 100644 kernel/time/clockdevice.c
next reply other threads:[~2010-11-04 19:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 19:26 Richard Cochran [this message]
2010-11-04 19:28 ` [PATCH RFC 1/8] Introduce dynamic " Richard Cochran
2010-11-08 6:38 ` Arnd Bergmann
2010-12-04 14:55 ` Richard Cochran
2010-12-06 14:14 ` Arnd Bergmann
2010-11-04 19:28 ` [PATCH RFC 2/8] clock device: convert clock_gettime Richard Cochran
2010-11-08 6:56 ` Arnd Bergmann
2010-11-09 10:26 ` Richard Cochran
2010-11-09 12:47 ` Arnd Bergmann
2010-11-09 21:37 ` john stultz
2010-11-10 10:16 ` Arnd Bergmann
2010-11-08 23:37 ` john stultz
2010-11-09 8:23 ` Richard Cochran
2010-11-09 21:10 ` john stultz
2010-11-15 9:41 ` Richard Cochran
2010-11-04 19:28 ` [PATCH RFC 3/8] clock device: convert clock_getres Richard Cochran
2010-11-04 19:29 ` [PATCH RFC 4/8] clock device: convert clock_settime Richard Cochran
2010-11-04 19:29 ` [PATCH RFC 5/8] clock device: convert timer_create Richard Cochran
2010-11-04 19:30 ` [PATCH RFC 6/8] clock device: convert timer_delete Richard Cochran
2010-11-04 19:30 ` [PATCH RFC 7/8] clock device: convert timer_gettime Richard Cochran
2010-11-04 19:30 ` [PATCH RFC 8/8] clock device: convert timer_settime Richard Cochran
2010-11-08 23:01 ` [PATCH RFC 0/8] Dynamic clock devices john stultz
2010-11-15 9:34 ` Richard Cochran
2010-11-15 10:01 ` Paul Mundt
2010-11-18 16:33 ` Richard Cochran
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=cover.1288897198.git.richard.cochran@omicron.at \
--to=richardcochran@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=cl@linux.com \
--cc=johnstul@us.ibm.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome