All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 29 Aug 2006 17:34:55 +0300	[thread overview]
Message-ID: <20060829143454.GI4204@atomide.com> (raw)
In-Reply-To: <200608151517.16378.david-b@pacbell.net>

* David Brownell <david-b@pacbell.net> [060816 01:17]:
> 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. :)

Sounds like it should be capable of waking up the system if 32KHz clock
is on and the wake-up events are configured properly.

Anyways, pushing today. Let's also plan on removing the old driver then.

Regards,

Tony

  parent reply	other threads:[~2006-08-29 14:34 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         ` Tony Lindgren [this message]
2006-08-29 19:51           ` [patch 2.6.17-rc4-omap-git] rtc-omap, rtc framework driver 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=20060829143454.GI4204@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.