From: Kevin Hilman <khilman@ti.com>
To: Tero.Kristo@nokia.com
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] OMAP3: PM: fix save secure RAM to restore MPU power state
Date: Wed, 26 Jan 2011 12:48:44 -0800 [thread overview]
Message-ID: <87bp33xufn.fsf@ti.com> (raw)
In-Reply-To: <854C6400F5AA6644BA6FE7953F3E769B0376F954@008-AM1MPN1-012.mgdnok.nokia.com> (Tero Kristo's message of "Wed, 26 Jan 2011 09:27:03 +0000")
Hi Tero,
<Tero.Kristo@nokia.com> writes:
>>Currently, on HS/EMU devices, MPU power state forced to on during PM
>>init by the save secure RAM code. Rather than forcing the state of
>>MPU powerdomain to on, simply read the current value and restore it
>>after the ROM code has run.
>>
>>This only affects the !CPUidle case since when CPUidle is enabled, the
>>MPU power state is dynamically changed by CPUidle. In the !CPUidle
>>case, MPU power state is initialized once at init and never touched.
>>
>>Cc: Tero Kristo <tero.kristo@nokia.com>
>>Signed-off-by: Kevin Hilman <khilman@ti.com>
>>---
>>If no objectsions, will be queued in my pm-fixes branch for 2.6.38-rc.
>
> Looks good to me. Ack, if you need one.
>
Thanks, I was looking for your ack.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] OMAP3: PM: fix save secure RAM to restore MPU power state
Date: Wed, 26 Jan 2011 12:48:44 -0800 [thread overview]
Message-ID: <87bp33xufn.fsf@ti.com> (raw)
In-Reply-To: <854C6400F5AA6644BA6FE7953F3E769B0376F954@008-AM1MPN1-012.mgdnok.nokia.com> (Tero Kristo's message of "Wed, 26 Jan 2011 09:27:03 +0000")
Hi Tero,
<Tero.Kristo@nokia.com> writes:
>>Currently, on HS/EMU devices, MPU power state forced to on during PM
>>init by the save secure RAM code. Rather than forcing the state of
>>MPU powerdomain to on, simply read the current value and restore it
>>after the ROM code has run.
>>
>>This only affects the !CPUidle case since when CPUidle is enabled, the
>>MPU power state is dynamically changed by CPUidle. In the !CPUidle
>>case, MPU power state is initialized once at init and never touched.
>>
>>Cc: Tero Kristo <tero.kristo@nokia.com>
>>Signed-off-by: Kevin Hilman <khilman@ti.com>
>>---
>>If no objectsions, will be queued in my pm-fixes branch for 2.6.38-rc.
>
> Looks good to me. Ack, if you need one.
>
Thanks, I was looking for your ack.
Kevin
next prev parent reply other threads:[~2011-01-26 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 0:50 [PATCH] OMAP3: PM: fix save secure RAM to restore MPU power state Kevin Hilman
2011-01-26 0:50 ` Kevin Hilman
2011-01-26 9:27 ` Tero.Kristo
2011-01-26 9:27 ` Tero.Kristo at nokia.com
2011-01-26 20:48 ` Kevin Hilman [this message]
2011-01-26 20:48 ` 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=87bp33xufn.fsf@ti.com \
--to=khilman@ti.com \
--cc=Tero.Kristo@nokia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
/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.