From: Luciano Coelho <coelho@ti.com>
To: Kevin Hilman <khilman@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>,
linux-omap@vger.kernel.org, santosh.shilimkar@ti.com,
linux-arm-kernel@lists.infradead.org, rnayak@ti.com,
ido@wizery.com
Subject: Re: [PATCH 0/2] ARM: OMAP2+: PM: code consolidation for 3.4
Date: Fri, 09 Mar 2012 08:15:02 +0200 [thread overview]
Message-ID: <1331273702.18015.92.camel@cumari> (raw)
In-Reply-To: <87d38mbxfu.fsf@ti.com>
Hi Kevin,
On Thu, 2012-03-08 at 13:21 -0800, Kevin Hilman wrote:
> Luciano Coelho <coelho@ti.com> writes:
>
> [...]
>
> > Thanks, Paul! I was just chatting with Kevin about this on IRC. With
> > your patch and no_console_suspend, it works. :)
>
> Just FYI... I've queued this patch from Paul and it's now queued by Tony
> for v3.4 in his cleanup-pm branch.
Great, thanks for the info!
BTW, you and Paul said that it was not recommended to use
no_console_suspend, but Ido (on CC) said that it can be useful for us,
because we need to see if our own (wireless) stuff goes into suspend
correctly.
Are there any real problems with no_console_suspend besides power
consumption? Is it safe for us to simply apply Paul's patch when we need
it?
--
Cheers,
Luca.
WARNING: multiple messages have this Message-ID (diff)
From: coelho@ti.com (Luciano Coelho)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: OMAP2+: PM: code consolidation for 3.4
Date: Fri, 09 Mar 2012 08:15:02 +0200 [thread overview]
Message-ID: <1331273702.18015.92.camel@cumari> (raw)
In-Reply-To: <87d38mbxfu.fsf@ti.com>
Hi Kevin,
On Thu, 2012-03-08 at 13:21 -0800, Kevin Hilman wrote:
> Luciano Coelho <coelho@ti.com> writes:
>
> [...]
>
> > Thanks, Paul! I was just chatting with Kevin about this on IRC. With
> > your patch and no_console_suspend, it works. :)
>
> Just FYI... I've queued this patch from Paul and it's now queued by Tony
> for v3.4 in his cleanup-pm branch.
Great, thanks for the info!
BTW, you and Paul said that it was not recommended to use
no_console_suspend, but Ido (on CC) said that it can be useful for us,
because we need to see if our own (wireless) stuff goes into suspend
correctly.
Are there any real problems with no_console_suspend besides power
consumption? Is it safe for us to simply apply Paul's patch when we need
it?
--
Cheers,
Luca.
next prev parent reply other threads:[~2012-03-09 6:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 9:38 [PATCH 0/2] ARM: OMAP2+: PM: code consolidation for 3.4 Paul Walmsley
2012-02-02 9:38 ` Paul Walmsley
2012-02-02 9:38 ` [PATCH 1/2] ARM: OMAP2+: PM: share clkdms_setup() across OMAP2, 3, 4 Paul Walmsley
2012-02-02 9:38 ` Paul Walmsley
2012-02-02 9:38 ` [PATCH 2/2] ARM: OMAP2+: PM: share some suspend-related functions " Paul Walmsley
2012-02-02 9:38 ` Paul Walmsley
2012-02-02 11:25 ` [PATCH 0/2] ARM: OMAP2+: PM: code consolidation for 3.4 Shilimkar, Santosh
2012-02-02 11:25 ` Shilimkar, Santosh
2012-02-02 18:38 ` Kevin Hilman
2012-02-02 18:38 ` Kevin Hilman
2012-02-02 18:40 ` Paul Walmsley
2012-02-02 18:40 ` Paul Walmsley
2012-02-02 20:29 ` Paul Walmsley
2012-02-02 20:29 ` Paul Walmsley
2012-03-08 12:21 ` Coelho, Luciano
2012-03-08 12:21 ` Coelho, Luciano
2012-03-08 18:18 ` Paul Walmsley
2012-03-08 18:18 ` Paul Walmsley
2012-03-08 18:27 ` Kevin Hilman
2012-03-08 18:27 ` Kevin Hilman
2012-03-08 18:47 ` Luciano Coelho
2012-03-08 18:47 ` Luciano Coelho
2012-03-08 18:55 ` Paul Walmsley
2012-03-08 18:55 ` Paul Walmsley
2012-03-08 19:05 ` Luciano Coelho
2012-03-08 19:05 ` Luciano Coelho
2012-03-08 21:21 ` Kevin Hilman
2012-03-08 21:21 ` Kevin Hilman
2012-03-09 6:15 ` Luciano Coelho [this message]
2012-03-09 6:15 ` Luciano Coelho
2012-03-09 15:23 ` Kevin Hilman
2012-03-09 15:23 ` Kevin Hilman
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=1331273702.18015.92.camel@cumari \
--to=coelho@ti.com \
--cc=ido@wizery.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@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 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.