From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/5] ARM: pm: add generic CPU suspend/resume support
Date: Sat, 12 Feb 2011 20:39:57 +0530 [thread overview]
Message-ID: <3f574626437da8db9f7844d5bb031046@mail.gmail.com> (raw)
In-Reply-To: <20110212145010.GK15616@n2100.arm.linux.org.uk>
> -----Original Message-----
> From: Russell King - ARM Linux [mailto:linux at arm.linux.org.uk]
> Sent: Saturday, February 12, 2011 8:20 PM
> To: Santosh Shilimkar
> Cc: Colin Cross; Kukjin Kim; saeed bishara; linux-arm-
> kernel at lists.infradead.org
> Subject: Re: [PATCH v3 2/5] ARM: pm: add generic CPU suspend/resume
> support
>
> On Fri, Feb 11, 2011 at 05:37:04PM +0530, Santosh Shilimkar wrote:
> > There is a Monitor secure API, needs to be called from non-secure
> > software to set this diagnostic registers in resume path.
>
> It would be an idea to get the OMAP sleep code up to date so that I
> can
> look at OMAPs requirements for this to be useful.
>
> As the current code stands, I don't see any reason why the sleep34xx
> code
> can't use this infrastructure, but I'm loathed to start modifying
> that if there's outstanding code changes in that area.
Yep. There are few issues out there with sleep34xx code.
- Secure APIs
- Current code needs to be cleaned up to remove
unwanted registers save restore
- Some part of the code on OMAP3 must be run from
SRAM. It can't run from DDR
- AUXCTLR, Diagnostic registers aren't accessible
in secure mode.
- L2 cache needs to be handled with secure APIs.
- Code sequence needs to handle errata's handling
which accesses OMAP PM registers.
Few of the above are getting addressed for this merge window.
So my plan was to take a look at generic suspend after the
merge window. By that time your generic stuff and omap
cleanup would have got merged hopefully.
Regards,
Santosh
next prev parent reply other threads:[~2011-02-12 15:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 19:11 [RFC] Generic CPU save/restore PM support Russell King - ARM Linux
2011-02-06 19:12 ` [PATCH 1/5] ARM: move cache/processor/fault glue to separate include files Russell King - ARM Linux
2011-02-06 19:12 ` [PATCH 2/5] ARM: pm: add generic CPU suspend/resume support Russell King - ARM Linux
2011-02-07 12:01 ` [PATCH v2 " Russell King - ARM Linux
2011-02-07 12:10 ` [PATCH v3 " Russell King - ARM Linux
2011-02-07 13:21 ` saeed bishara
2011-02-07 13:34 ` Russell King - ARM Linux
2011-02-07 14:04 ` saeed bishara
2011-02-07 14:17 ` Russell King - ARM Linux
2011-02-07 14:27 ` saeed bishara
2011-02-07 14:33 ` Russell King - ARM Linux
2011-02-07 14:58 ` saeed bishara
2011-02-07 15:02 ` Russell King - ARM Linux
2011-02-08 10:21 ` Lorenzo Pieralisi
2011-02-08 11:23 ` Russell King - ARM Linux
2011-02-08 12:33 ` Russell King - ARM Linux
2011-02-08 14:25 ` Lorenzo Pieralisi
2011-02-08 8:08 ` Colin Cross
2011-02-10 3:15 ` Colin Cross
2011-02-11 11:58 ` Russell King - ARM Linux
2011-02-11 12:07 ` Santosh Shilimkar
2011-02-12 14:50 ` Russell King - ARM Linux
2011-02-12 15:09 ` Santosh Shilimkar [this message]
2011-02-28 18:17 ` Santosh Shilimkar
2011-02-28 18:21 ` Jean Pihet
2011-02-14 0:27 ` Kukjin Kim
2011-02-06 19:13 ` [PATCH 3/5] ARM: pm: convert PXA to generic " Russell King - ARM Linux
2011-02-06 19:13 ` [PATCH 4/5] ARM: pm: convert sa11x0 " Russell King - ARM Linux
2011-02-07 18:11 ` Russell King - ARM Linux
2011-02-06 19:13 ` [PATCH 5/5] ARM: pm: convert samsung platforms " Russell King - ARM Linux
2011-02-07 5:42 ` [RFC] Generic CPU save/restore PM support Kukjin Kim
2011-02-07 10:44 ` Russell King - ARM Linux
[not found] <mailman.11856.1297088273.1534.linux-arm-kernel@lists.infradead.org>
2011-02-07 15:41 ` [PATCH v3 2/5] ARM: pm: add generic CPU suspend/resume support Frank Hofmann
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=3f574626437da8db9f7844d5bb031046@mail.gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).