From: Kevin Hilman <khilman@deeprootsystems.com>
To: Mike Chan <mike@android.com>
Cc: linux-omap@vger.kernel.org, r-woodruff2@ti.com, tony@atomide.com
Subject: Re: [PATCH v2 1/2] omap: pm34xx: Enable IO / IO-CHAIN wakeups for PER
Date: Tue, 04 May 2010 12:06:37 -0700 [thread overview]
Message-ID: <87eihrh4g2.fsf@deeprootsystems.com> (raw)
In-Reply-To: <p2q8bb80c381005031648o43f3a724k56feba4780ed06cc@mail.gmail.com> (Mike Chan's message of "Mon\, 3 May 2010 16\:48\:21 -0700")
Mike Chan <mike@android.com> writes:
> On Mon, May 3, 2010 at 4:35 PM, Kevin Hilman
> <khilman@deeprootsystems.com> wrote:
>> Mike Chan <mike@android.com> writes:
>>
>>> IO events can also come from GPIO modules, which reside in the PER domain.
>>> It is possible for the PER to enter RET while CORE is still in ON.
>>> If GPIO 2-6 are enabled for IO-pad wakeups, the PER domain will not
>>> wakeup in this case, unless we enable it.
>>>
>>> Signed-off-by: Mike Chan <mike@android.com>
>>
>> Thanks, adding both patches to PM branch (pm-fixes branch) and will
>> queue for 2.6.35.
>>
>
> Thanks, with this patch looking good, I was hoping for some feedback
> from people on the 2nd patch in the series. It makes sense to me since
> PER will be woken up now, not just CORE, but I wanted to double check.
It makes sense to me too, I've applied both to the pm-fixes branch.
Kevin
prev parent reply other threads:[~2010-05-04 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 23:04 [PATCH v2 1/2] omap: pm34xx: Enable IO / IO-CHAIN wakeups for PER Mike Chan
2010-05-03 23:04 ` [PATCH v2 2/2] omap: pm34xx: Remove PER wakeup dependency on CORE Mike Chan
2010-05-03 23:35 ` [PATCH v2 1/2] omap: pm34xx: Enable IO / IO-CHAIN wakeups for PER Kevin Hilman
2010-05-03 23:48 ` Mike Chan
2010-05-04 19:06 ` Kevin Hilman [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=87eihrh4g2.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=mike@android.com \
--cc=r-woodruff2@ti.com \
--cc=tony@atomide.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.