From: David Brownell <david-b@pacbell.net>
To: Woody Suwalski <woodys@xandros.com>
Cc: Alessandro Zummo <alessandro.zummo@towertech.it>,
rtc-linux@googlegroups.com,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Russell King <rmk@arm.linux.org.uk>
Subject: Re: [patch 2.6.20-rc3 1/3] rtc-cmos driver
Date: Sat, 6 Jan 2007 13:17:25 -0800 [thread overview]
Message-ID: <200701061317.25567.david-b@pacbell.net> (raw)
In-Reply-To: <459FD993.3070909@xandros.com>
On Saturday 06 January 2007 9:17 am, Woody Suwalski wrote:
> >> There are PPC, M68K, SPARC, and other boards that could also
> >> use this; ARMs tend to integrate some other RTC on-chip. ...
>
> > Let me put that differently. That should be done as a separate
> > patch, adding (a) that platform_device, and maybe platform_data
> > if it's got additional alarm registers, and (b) Kconfig support
> > to let that work. I'd call it a "patch #4 of 3". ;)
> > ...
>
> I will try to play with the new code on Monday on ARM...
Thanks. Could you describe your ARM board? None of mine have an
RTC using this register API. Does it support system sleep states
(/sys/power/state) with a wakeup-capable (enable_irq_wake) RTC irq?
- Dave
next prev parent reply other threads:[~2007-01-06 23:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 18:01 [patch 2.6.20-rc3 1/3] rtc-cmos driver David Brownell
2007-01-05 20:45 ` Alessandro Zummo
2007-01-06 3:10 ` David Brownell
2007-01-06 3:33 ` David Brownell
2007-01-06 17:17 ` Woody Suwalski
2007-01-06 21:17 ` David Brownell [this message]
2007-01-07 9:02 ` Russell King
2007-01-09 16:37 ` Woody Suwalski
2007-01-10 0:01 ` David Brownell
2007-01-10 5:27 ` David Brownell
2007-05-28 18:35 ` Matthew Garrett
2007-05-28 21:07 ` David Brownell
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=200701061317.25567.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@osdl.org \
--cc=alessandro.zummo@towertech.it \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=rtc-linux@googlegroups.com \
--cc=woodys@xandros.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).