From: David Brownell <david-b@pacbell.net>
To: "Johnson, Steve-OMAP" <stevej@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [patch 2.6.17-rc4-omap-git] rtc-omap, rtc framework driver
Date: Tue, 15 Aug 2006 15:17:15 -0700 [thread overview]
Message-ID: <200608151517.16378.david-b@pacbell.net> (raw)
In-Reply-To: <8C5B35906ACE4C48ACB3E1FAC65DB5B6231F5B@dlee08.ent.ti.com>
On Tuesday 15 August 2006 3:03 pm, Johnson, Steve-OMAP wrote:
> David,
>
> Thanks. I'll let marketing know and ask them to fix the graphic.
Good, so issue #2 is resolved ... this _is_ OMAP1-only, the Kconfig is right.
How about #1? Likely it's too late to resolve that doc ambiguity, but it'd
be good to know the answer anyway. :)
- Dave
> > > > Could someone confirm that this RTC can't actually do
> > > > system wakeups
> > > > without external hardware support? My documentation isn't at all
> > > > clear on that issue. There's certainly an external wakeup signal
> > > > available, but text also says that the alarm irq should work the
> > > > normal way ... but I don't see that happening. It could
> > > > easily be just a bug in
> > > > enable_irq_wakeup(INT_RTC_ALARM) handling, which ISTR
> > > > looked like a
> > > > big NOP last I checked (for almost all IRQs).
next prev parent reply other threads:[~2006-08-15 22:17 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 [this message]
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
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=200608151517.16378.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap-open-source@linux.omap.com \
--cc=stevej@ti.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