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 3/3] ARM: l2c: highbank: Add dummy configure function
Date: Tue, 12 May 2015 00:17:31 +0200 [thread overview]
Message-ID: <1431382651-15894-4-git-send-email-sjoerd.simons@collabora.co.uk> (raw)
In-Reply-To: <1431382651-15894-1-git-send-email-sjoerd.simons@collabora.co.uk>
Add empty configure function for the highbank l2c to reflect that the
cache can't be configured through a SMC. This prevent a useless
WARN_ONCE during early boot.
Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
---
arch/arm/mach-highbank/highbank.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm/mach-highbank/highbank.c b/arch/arm/mach-highbank/highbank.c
index 8e4846d..cee18db 100644
--- a/arch/arm/mach-highbank/highbank.c
+++ b/arch/arm/mach-highbank/highbank.c
@@ -60,6 +60,10 @@ static void highbank_l2c310_write_sec(unsigned long val, unsigned reg)
reg);
}
+static void highbank_l2c310_configure(const struct l2x0_regs *regs)
+{
+}
+
static void __init highbank_init_irq(void)
{
irqchip_init();
@@ -68,6 +72,7 @@ static void __init highbank_init_irq(void)
highbank_scu_map_io();
if (IS_ENABLED(CONFIG_CACHE_L2X0)) {
+ outer_cache.configure = highbank_l2c310_configure;
outer_cache.skip_unlock = true;
}
}
--
2.1.4
prev parent reply other threads:[~2015-05-11 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 22:17 [PATCH 0/3] Fix boot on Calxeda highbank Sjoerd Simons
2015-05-11 22:17 ` [PATCH 1/3] ARM: cache-l2c: Add flag to skip cache unlocking Sjoerd Simons
2015-05-11 22:29 ` Russell King - ARM Linux
2015-05-12 5:13 ` Sjoerd Simons
2015-05-11 22:17 ` [PATCH 2/3] ARM: l2c: highbank: Skip l2c unlocking Sjoerd Simons
2015-05-11 22:17 ` Sjoerd Simons [this message]
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=1431382651-15894-4-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®