From: Tom Rini <trini@kernel.crashing.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
Richard Zidlicky
<Richard.Zidlicky@stud.informatik.uni-erlangen.de>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH][RESEND] A generic RTC driver [0/3]
Date: Mon, 29 Jul 2002 08:24:07 -0700 [thread overview]
Message-ID: <20020729152407.GG11206@opus.bloom.county> (raw)
This is essentially the same driver I've sent 3 time previously in a
single patch, and unchanged since the last time I sent it in 3 smaller
chunks.
Patch 1 is the current version of the driver (switched to C99-style
initializers, done in the current m68k CVS tree) and needed changes to
select/compile it in general. I had previously asked the m68k community
if anyone objected to this being submitted by me, and I got Richard
Zidlicky's (who's at the top of the file) approval, as well as Geert
Uytterhoeven's approval.
Patch 2 is the PPC portion of the patch, which creates
include/asm-ppc/rtc.h. This has been in the PPC bitkeeper tree for over
a month now. I can have Paul Mackerras send this to you instead, if you
prefer.
Patch 3 is my own slight bit of work. This changes set_rtc_time(struct
*rtc_time) to return an int instead of void. This was done so that the
arch-specific code here could do additional checks on the time and
return an error if needed. This then introduces
include/asm-generic/rtc.h, include/asm-i386/rtc.h and
include/asm-alpha/rtc.h. include/asm-generic/rtc.h contains the
get_rtc_time and set_rtc_time logic that is in drivers/char/rtc.c and
has been tested on SMP i386. This also modifies include/asm-ppc/rtc.h
to return -ENODEV if no rtc hardware is present.
And now onto the history of this driver.
This has been in the m68k tree for a number of years now, so the general
code behind it is quite sound. This has also been abstracted to the
point where it works on other archs (mainly due to m68k/PPC hybrid
machines). This is quite useful since a number of archs cannot use
drivers/char/rtc.c because they have very different hardware, or other
issues.
This should also be useful on MIPS, who at one point in the past were
about to copy the PPC rtc driver (drivers/macintosh/rtc.c) and quite
probably useful on other archs as well.
Based on some private feedback, the parisc-linux people have been using
the 2.4 version of this driver for a while, so getting it to work on 2.5
for them should be a trivial matter (it's currently in their tree,
untested as other issues need to be resolved first). I believe with
some additional enhancements, ia64 will make use of this as well. And
if the MIPS community ever did make an rtc driver similar to
drivers/macintosh/rtc.c, they should be able to use this one rather
trivially.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
next reply other threads:[~2002-07-29 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 15:24 Tom Rini [this message]
2002-08-02 16:36 Tom Rini
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=20020729152407.GG11206@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=Richard.Zidlicky@stud.informatik.uni-erlangen.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®