From: Tony Lindgren <tony@atomide.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [patch 2.6.17-rc4-omap-git] rtc-omap, rtc framework driver
Date: Wed, 30 Aug 2006 10:57:34 +0300 [thread overview]
Message-ID: <20060830075733.GH27668@atomide.com> (raw)
In-Reply-To: <200608291251.57807.david-b@pacbell.net>
* David Brownell <david-b@pacbell.net> [060829 22:52]:
> On Tuesday 29 August 2006 7:34 am, Tony Lindgren wrote:
> >
> > Sounds like it should be capable of waking up the system if 32KHz clock
> > is on and the wake-up events are configured properly.
>
> Yes. I had more of a look at things, and have a patch (yet to be tested)
> that should let many more things be wakeup event sources. MPUIO irqs,
> GPIOs not in the first bank, non-MPUI/GPIO irqs (like RTC), etc.
Cool.
> > Anyways, pushing today. Let's also plan on removing the old driver then.
>
> Let's get the wakeup thing fixed, then I'll forward rtc-omap upstream if
> nobody reports any significant problems.
OK
> Might as well leave the old version in the OMAP tree until the new one
> gets pulled down.
OK
Tony
next prev parent reply other threads:[~2006-08-30 7:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 17:03 [patch 2.6.17-rc4-omap-git] rtc-omap, rtc framework driver David Brownell
2006-08-15 17:25 ` Johnson, Steve-OMAP
2006-08-15 22:01 ` David Brownell
2006-08-15 22:03 ` Johnson, Steve-OMAP
2006-08-15 22:17 ` David Brownell
2006-08-16 3:12 ` Interrupts on Omap5912 OJ Ravadilla
2006-08-16 6:13 ` Arnold
2006-08-29 14:34 ` [patch 2.6.17-rc4-omap-git] rtc-omap, rtc framework driver Tony Lindgren
2006-08-29 19:51 ` David Brownell
2006-08-30 7:57 ` Tony Lindgren [this message]
2006-08-30 8:22 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2006-08-15 17:58 Woodruff, Richard
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=20060830075733.GH27668@atomide.com \
--to=tony@atomide.com \
--cc=david-b@pacbell.net \
--cc=linux-omap-open-source@linux.omap.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