From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: cache-l2x0: add resume entry for l2 in secure mode
Date: Thu, 29 Sep 2011 13:50:26 +0100 [thread overview]
Message-ID: <20110929125026.GJ23944@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110929124419.GF19318@S2100-06.ap.freescale.net>
On Thu, Sep 29, 2011 at 08:44:20PM +0800, Shawn Guo wrote:
> Yeah, that's why I want to get imx6q stay away from this infrastructure
> right now. I do not see any simplicity and cleanup on imx6q current
> code by migrating to this infrastructure.
Why? If the data is already saved for you, then there's no reason not
to use it. The fact that some generic code doesn't give you _exactly_
everything you'd want is not a reason to avoid it.
The cleanup for imx6q is that it would no longer have to have its own
distinct code for saving the register values - and that's a danmed good
thing.
The idea here is that we consolidate what _can_ be consolidated (which
is the register saving.)
If you feel soo strongly that it's not worth doing, then let's stop
wasting time and review effort on this, and instead have _every_ SoC
implementing their own private L2 cache handling on resume.
next prev parent reply other threads:[~2011-09-29 12:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 3:26 [PATCH v2] ARM: cache-l2x0: add resume entry for l2 in secure mode Barry Song
2011-09-29 5:35 ` Santosh Shilimkar
2011-09-29 5:49 ` Shawn Guo
2011-09-29 5:59 ` Barry Song
2011-09-29 10:22 ` Lorenzo Pieralisi
2011-09-29 10:36 ` Santosh Shilimkar
2011-09-29 9:28 ` Shawn Guo
2011-09-29 9:24 ` Russell King - ARM Linux
2011-09-29 12:44 ` Shawn Guo
2011-09-29 12:50 ` Russell King - ARM Linux [this message]
2011-09-29 13:12 ` Shawn Guo
2011-09-29 13:26 ` Russell King - ARM Linux
2011-09-29 13:50 ` Shawn Guo
2011-09-29 9:44 ` Barry Song
2011-09-29 13:57 ` Shawn Guo
2011-09-29 14:55 ` Barry Song
2011-09-29 15:07 ` Shawn Guo
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=20110929125026.GJ23944@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).