From: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
To: Rob Herring <robh@kernel.org>,
Russell King <linux@arm.linux.org.uk>,
Tony Lindgren <tony@atomide.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Subject: [PATCH 0/2 v2] Fix boot on Calxeda highbank
Date: Tue, 12 May 2015 09:39:13 +0200 [thread overview]
Message-ID: <1431416355-7693-1-git-send-email-sjoerd.simons@collabora.co.uk> (raw)
When upgrading our trusted Calxeda server to Debian Jessie recently the machine
wedged during booting the installer. Upon further investigation, this happens
due to the transition to the generic L2C infrastructure introduced in 3.16. The
generic l2x0 code unlocks the cache during setup, however the Caldexa SMC
interface doesn't seem to allow the kernel to enable enable non-secure access
to the lock registers.. Queue Imprecise aborts and a fairly unhappy machine.
First patch in this series adds detection to the l2x0 code to check if
unlocking is possible. Second patch adds a (empty) configure callback for the
highbank l2c, reflecting the fact that there seemingly isn't anything to
configured via an SMC on these maches.
Changes since v1:
- Auto-detect when unlocking the cache is unsafe rather then requiring a
explicit flag to be set in the machine-specific code
Sjoerd Simons (2):
ARM: cache-l2c: Detect whether it's safe to unlock
ARM: l2c: highbank: Add dummy configure function
arch/arm/mach-highbank/highbank.c | 8 ++++++++
arch/arm/mm/cache-l2x0.c | 20 ++++++++++++++++++++
2 files changed, 28 insertions(+)
--
2.1.4
next reply other threads:[~2015-05-12 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 7:39 Sjoerd Simons [this message]
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
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=1431416355-7693-1-git-send-email-sjoerd.simons@collabora.co.uk \
--to=sjoerd.simons@collabora.co.uk \
--cc=javier.martinez@collabora.co.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=robh@kernel.org \
--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®