From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-pm] [RFC PATCH v4] ARM hibernation/suspend-to-disk support
Date: Thu, 09 Jun 2011 22:40:59 +0530 [thread overview]
Message-ID: <4DF0FEA3.5090406@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1106091803050.11513@localhost6.localdomain6>
On 6/9/2011 10:37 PM, Frank Hofmann wrote:
>
>
> On Thu, 9 Jun 2011, Santosh Shilimkar wrote:
>
>> On 6/9/2011 9:56 PM, Frank Hofmann wrote:
>>>
>>>
> [ ... ]
>>> a) What reasons if any are there why cpu_{v7_do_}suspend/resume are not
>>> ok to use (on OMAP) for snapshotting core state, for the purpose of
>>> hibernation ?
>>> If there are any such issues, then how could they be addresssed ?
>>>
>> Part of the answer is what Russell described. We think it's doable,
>> but it needs some work. First and fore most is this code should
>> be able to be executed from DDR. It's not the case today.
>
> Ah, I gather that's the _real_ critical point, i.e.
>
> _omap_sram_idle = omap_sram_push(omap34xx_cpu_suspend,
> omap34xx_cpu_suspend_sz);
>
> relies on this to be completely consecutive in mem, and relocatable,
> i.e. calling _outside_ that area isn't possible ?
>
> I.e. unless a way can be found to _embed_ cpu_suspend/resume here, it's
> pretty hard to use ?
>
> Would it be possible / acceptable to have it be relocatable code, and
> put it into a common .section ?
>
Surely acceptable :)
But other points about callback are also important o.w
you will use MMU with wrong CP15 configurations after
one sleep transition.
next prev parent reply other threads:[~2011-06-09 17:10 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 16:48 [RFC PATCH v4] ARM hibernation/suspend-to-disk support Frank Hofmann
2011-06-07 21:48 ` Rafael J. Wysocki
2011-06-07 21:48 ` [linux-pm] " Rafael J. Wysocki
2011-06-09 15:30 ` Frank Hofmann
2011-06-09 15:30 ` [linux-pm] " Frank Hofmann
2011-06-09 15:40 ` Russell King - ARM Linux
2011-06-09 16:26 ` Frank Hofmann
2011-06-09 16:26 ` [linux-pm] " Frank Hofmann
2011-06-09 16:35 ` Santosh Shilimkar
2011-06-09 16:35 ` [linux-pm] " Santosh Shilimkar
2011-06-09 17:07 ` Frank Hofmann
2011-06-09 17:10 ` Santosh Shilimkar [this message]
2011-06-09 17:10 ` Santosh Shilimkar
2011-06-09 17:14 ` Russell King - ARM Linux
2011-06-09 17:14 ` [linux-pm] " Russell King - ARM Linux
2011-06-09 17:07 ` Frank Hofmann
2011-06-09 16:27 ` [linux-pm] " Santosh Shilimkar
2011-06-09 16:40 ` Russell King - ARM Linux
2011-06-09 16:40 ` [linux-pm] " Russell King - ARM Linux
2011-06-09 16:53 ` Santosh Shilimkar
2011-06-09 16:53 ` [linux-pm] " Santosh Shilimkar
2011-06-09 17:12 ` Russell King - ARM Linux
2011-06-09 17:12 ` [linux-pm] " Russell King - ARM Linux
2011-06-09 17:21 ` Santosh Shilimkar
2011-06-09 17:21 ` Santosh Shilimkar
2011-06-09 17:53 ` [linux-pm] " Russell King - ARM Linux
2011-06-21 10:11 ` Russell King - ARM Linux
2011-06-21 10:11 ` [linux-pm] " Russell King - ARM Linux
2011-06-09 17:53 ` Russell King - ARM Linux
2011-06-10 12:22 ` [linux-pm] " Frank Hofmann
2011-06-10 13:43 ` Russell King - ARM Linux
2011-06-10 13:43 ` [linux-pm] " Russell King - ARM Linux
2011-06-10 13:47 ` Frank Hofmann
2011-06-10 13:47 ` [linux-pm] " Frank Hofmann
2011-06-10 14:02 ` Russell King - ARM Linux
2011-06-10 14:02 ` [linux-pm] " Russell King - ARM Linux
2011-06-10 14:54 ` Frank Hofmann
2011-06-10 14:54 ` Frank Hofmann
2011-06-10 12:22 ` Frank Hofmann
2011-06-09 16:44 ` Frank Hofmann
2011-06-09 16:44 ` [linux-pm] " Frank Hofmann
2011-06-09 16:56 ` Santosh Shilimkar
2011-06-09 16:56 ` Santosh Shilimkar
2011-06-09 16:27 ` Santosh Shilimkar
2011-06-09 15:40 ` Russell King - ARM Linux
2011-06-09 16:50 ` Russell King - ARM Linux
2011-06-09 16:53 ` Frank Hofmann
2011-06-09 16:53 ` Frank Hofmann
2011-06-09 16:50 ` Russell King - ARM Linux
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=4DF0FEA3.5090406@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-arm-kernel@lists.infradead.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.