From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Cc: Rob Herring <robh@kernel.org>, Tony Lindgren <tony@atomide.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Subject: Re: [PATCH 1/2] ARM: cache-l2c: Detect whether it's safe to unlock
Date: Fri, 15 May 2015 12:34:48 +0100 [thread overview]
Message-ID: <20150515113448.GI2067@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1431416355-7693-2-git-send-email-sjoerd.simons@collabora.co.uk>
On Tue, May 12, 2015 at 09:39:14AM +0200, Sjoerd Simons wrote:
> The L2C cache should only be unlocked when the cache is setup to allow
> that. In the common case the l2x0 driver sets up the cache for that to
> be the case (e.g. setting L310_AUX_CTRL_NS_LOCKDOWN on L2C-310), making
> unlock safe. However when a secure firmware is in use, it may not be
> possible for the L2c to be configured that way making unlocking unsafe.
>
> To handle that, for caches where special configuration is needed to allow
> unlocking, check whether this has been setup before unlocking.
I've come up with a different solution to this, which of course I prefer.
I'll post the patches later today, thanks.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-05-15 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 7:39 [PATCH 0/2 v2] Fix boot on Calxeda highbank Sjoerd Simons
2015-05-12 7:39 ` [PATCH 1/2] ARM: cache-l2c: Detect whether it's safe to unlock Sjoerd Simons
2015-05-15 11:34 ` Russell King - ARM Linux [this message]
2015-05-27 13:00 ` Sjoerd Simons
2015-05-27 17:41 ` Russell King - ARM Linux
2015-05-12 7:39 ` [PATCH 2/2] ARM: l2c: highbank: Add dummy configure function Sjoerd Simons
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=20150515113448.GI2067@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=javier.martinez@collabora.co.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sjoerd.simons@collabora.co.uk \
--cc=tony@atomide.com \
/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
all inboxes | Powered by JetHome®