From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: cpu_suspend does not flush the L2 cache
Date: Mon, 25 Jul 2011 21:08:20 +0100 [thread overview]
Message-ID: <20110725200820.GE14955@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <74C67D49A66F0848B6F4548360B2EDB58DED35BC42@HQMAIL04.nvidia.com>
On Mon, Jul 25, 2011 at 11:49:43AM -0700, Scott Williams wrote:
> In 2.6.39, CPU suspend/resumes crashes if an outer cache controller
> (like a PL310) is configured and enabled. cpu_suspend only flushes
> the L1 cache.
Correct. cpu_suspend is been a _consolidation_ effort across the various
implementations. Only one implementation deals with the L2 cache issues
at present.
A bunch of patches have gone in during this merge window to continue
that consolidation effort and improve the cpu_suspend interfaces.
Eventually the L2 cache issues will be dealt with in core code.
So at the moment, platforms are expected to deal with this in their own
suspend finisher code.
FYI, I have no platforms at present with L2 cache and are capable of
suspend. I'm still waiting on TI for some prototype code for OMAP4
suspend support... until that time, I am unable to progress it further
unless I try to address these issues blind.
next prev parent reply other threads:[~2011-07-25 20:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 18:49 cpu_suspend does not flush the L2 cache Scott Williams
2011-07-25 20:08 ` Russell King - ARM Linux [this message]
2011-07-25 21:31 ` Will Deacon
2011-07-28 8:15 ` Barry Song
2011-07-28 9:57 ` Santosh Shilimkar
2011-07-28 17:14 ` Scott Williams
2011-07-28 18:10 ` Lorenzo Pieralisi
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=20110725200820.GE14955@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).