public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: tony@atomide.com
To: David Brownell <david-b@pacbell.net>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [patch 2.6.19-rc6-omap1] MPUIO wake updates
Date: Thu, 30 Nov 2006 15:14:17 -0800	[thread overview]
Message-ID: <20061130231417.GI9605@atomide.com> (raw)
In-Reply-To: <20061128073226.0816C1E1937@adsl-69-226-248-13.dsl.pltn13.pacbell.net>

* David Brownell <david-b@pacbell.net> [061127 23:40]:
> GPIO and MPUIO wake updates:
> 
>  - Hook MPUIOs into the irq wakeup framework too.  This uses a platform
>    device to update irq enables during system sleep states, instead of
>    a sys_device, since the latter is no longer needed for such things.
> 
>  - Also forward enable/disable irq wake requests to the relevant GPIO
>    controller, so the top level IRQ dispatcher can (eventually) handle
>    these wakeup events automatically if more than one GPIO pin needs to
>    be a wakeup event source.
> 
>  - Minor tweak to the 24xx non-wakeup gpio stuff: no need to check such
>    read-only data under the spinlock.
> 
> This assumes (maybe wrongly?) that only 16xx can do GPIO wakeup; without
> a 15xx I can't test such stuff.
> 
> Also this expects the top level IRQ dispatcher to properly handle requests
> to enable/disable irq wake, which is currently known to be wrong:  omap1
> saves the flags but ignores them, omap2 doesn't even save it.  (Wakeup
> events are, wrongly, hardwired in the relevant mach-omapX/pm.c file ...)
> So MPUIO irqs won't yet trigger system wakeup.

Pushing today.

Tony

      reply	other threads:[~2006-11-30 23:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-28  7:32 [patch 2.6.19-rc6-omap1] MPUIO wake updates David Brownell
2006-11-30 23:14 ` tony [this message]

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=20061130231417.GI9605@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