All of lore.kernel.org
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Paul Walmsley <paul@pwsan.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 21:59:47 +0530	[thread overview]
Message-ID: <510A9BFB.5070802@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1301311537530.23099@utopia.booyaka.com>

On Thursday 31 January 2013 09:10 PM, Paul Walmsley wrote:
> Hi,
>
> On Thu, 31 Jan 2013, Rajendra Nayak wrote:
>
>> Throw a pr_warn() at boot only when CONFIG_CPU_IDLE is enabled. Note
>> that it isn't enabled by default in omap2plus_defconfig. Also
>> throw one when a suspend fails, saying bootloader *could be* a possible
>> cause specifying the right version to be used.
>
> In my view, these steps aren't sufficient, for the reasons described in
>
> http://marc.info/?l=linux-omap&m=135964568904053&w=2
>
> Even with CONFIG_CPU_IDLE=n, it's still possible to attempt to enter
> full-chip retention idle on OMAP4 via 'echo mem > /sys/power/state', so it
> doesn't seem right to restrict a solution to that case.
>

I think rajendra also mentioned adding one in suspend path too
when it fails.
" Also throw one when a suspend fails, saying bootloader
*could be* a possible cause specifying the right version to be used."

I find Rajendra's suggestion reasonable because some one might
just miss the boot message but getting the message on failure
case cant' be missed.

Regards
Santosh

WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP4 PM bootloader dependency problems
Date: Thu, 31 Jan 2013 21:59:47 +0530	[thread overview]
Message-ID: <510A9BFB.5070802@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1301311537530.23099@utopia.booyaka.com>

On Thursday 31 January 2013 09:10 PM, Paul Walmsley wrote:
> Hi,
>
> On Thu, 31 Jan 2013, Rajendra Nayak wrote:
>
>> Throw a pr_warn() at boot only when CONFIG_CPU_IDLE is enabled. Note
>> that it isn't enabled by default in omap2plus_defconfig. Also
>> throw one when a suspend fails, saying bootloader *could be* a possible
>> cause specifying the right version to be used.
>
> In my view, these steps aren't sufficient, for the reasons described in
>
> http://marc.info/?l=linux-omap&m=135964568904053&w=2
>
> Even with CONFIG_CPU_IDLE=n, it's still possible to attempt to enter
> full-chip retention idle on OMAP4 via 'echo mem > /sys/power/state', so it
> doesn't seem right to restrict a solution to that case.
>

I think rajendra also mentioned adding one in suspend path too
when it fails.
" Also throw one when a suspend fails, saying bootloader
*could be* a possible cause specifying the right version to be used."

I find Rajendra's suggestion reasonable because some one might
just miss the boot message but getting the message on failure
case cant' be missed.

Regards
Santosh

  reply	other threads:[~2013-01-31 16:28 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 [this message]
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
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=510A9BFB.5070802@ti.com \
    --to=santosh.shilimkar@ti.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=rnayak@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.