From: Paul Walmsley <paul@pwsan.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Rajendra Nayak <rnayak@ti.com>,
t-kristo@ti.com, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
khilman@deeprootsystems.com
Subject: Re: OMAP4 PM bootloader dependency problems
Date: Thu, 31 Jan 2013 16:56:54 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.00.1301311656230.32145@utopia.booyaka.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1301311630090.32145@utopia.booyaka.com>
On Thu, 31 Jan 2013, Paul Walmsley wrote:
> Right. I don't have any problem with adding a message to the suspend path
> also. But I'd like to see a boot-time message added even if
> CONFIG_CPU_IDLE=n, since it's still possible to enter full-chip retention
> idle with dynamic idle. In other words, not everyone might use 'echo mem
> > /sys/power/state'.
(and re-reading my original E-mail to Rajendra, I can see that it was
nuclear, so I'm sorry about that.)
- Paul
WARNING: multiple messages have this Message-ID (diff)
From: paul@pwsan.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP4 PM bootloader dependency problems
Date: Thu, 31 Jan 2013 16:56:54 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.00.1301311656230.32145@utopia.booyaka.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1301311630090.32145@utopia.booyaka.com>
On Thu, 31 Jan 2013, Paul Walmsley wrote:
> Right. I don't have any problem with adding a message to the suspend path
> also. But I'd like to see a boot-time message added even if
> CONFIG_CPU_IDLE=n, since it's still possible to enter full-chip retention
> idle with dynamic idle. In other words, not everyone might use 'echo mem
> > /sys/power/state'.
(and re-reading my original E-mail to Rajendra, I can see that it was
nuclear, so I'm sorry about that.)
- Paul
next prev parent reply other threads:[~2013-01-31 16:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 2:42 OMAP4 PM bootloader dependency problems Paul Walmsley
2013-01-22 2:42 ` Paul Walmsley
2013-01-30 17:15 ` Paul Walmsley
2013-01-30 17:15 ` Paul Walmsley
2013-01-31 9:00 ` Tero Kristo
2013-01-31 9:00 ` Tero Kristo
2013-01-31 11:26 ` Rajendra Nayak
2013-01-31 11:26 ` Rajendra Nayak
2013-01-31 15:40 ` Paul Walmsley
2013-01-31 15:40 ` Paul Walmsley
2013-01-31 16:29 ` Santosh Shilimkar
2013-01-31 16:29 ` Santosh Shilimkar
2013-01-31 16:32 ` Paul Walmsley
2013-01-31 16:32 ` Paul Walmsley
2013-01-31 16:56 ` Paul Walmsley [this message]
2013-01-31 16:56 ` Paul Walmsley
2013-01-31 16:57 ` Paul Walmsley
2013-01-31 16:57 ` Paul Walmsley
2013-01-31 15:21 ` Paul Walmsley
2013-01-31 15:21 ` Paul Walmsley
2013-02-05 19:45 ` Jon Hunter
2013-02-05 19:45 ` Jon Hunter
2013-03-11 0:41 ` Paul Walmsley
2013-03-11 0:41 ` Paul Walmsley
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=alpine.DEB.2.00.1301311656230.32145@utopia.booyaka.com \
--to=paul@pwsan.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=t-kristo@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.