From: victor.kamensky@linaro.org (Victor Kamensky)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: mcpm: fix big endian issue in mcpm startup code
Date: Mon, 7 Oct 2013 21:37:19 -0700 [thread overview]
Message-ID: <1381207040-1623-2-git-send-email-victor.kamensky@linaro.org> (raw)
In-Reply-To: <1381207040-1623-1-git-send-email-victor.kamensky@linaro.org>
In big endian mode mcpm_entry_point is first function
that called on secondaries CPU. First it should switch
CPU into big endian code.
Signed-off-by: Victor Kamensky <victor.kamensky@linaro.org>
---
arch/arm/common/mcpm_head.S | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/common/mcpm_head.S b/arch/arm/common/mcpm_head.S
index 39c96df..4f88f5e 100644
--- a/arch/arm/common/mcpm_head.S
+++ b/arch/arm/common/mcpm_head.S
@@ -15,6 +15,7 @@
#include <linux/linkage.h>
#include <asm/mcpm.h>
+#include <asm/assembler.h>
#include "vlock.h"
@@ -47,6 +48,7 @@
ENTRY(mcpm_entry_point)
+ ARM_BE8(setend be)
THUMB( adr r12, BSYM(1f) )
THUMB( bx r12 )
THUMB( .thumb )
--
1.8.1.4
next prev parent reply other threads:[~2013-10-08 4:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 4:37 [PATCH 0/2] additional vexpress-tc2 big endian fixes Victor Kamensky
2013-10-08 4:37 ` Victor Kamensky [this message]
2013-10-08 4:37 ` [PATCH 2/2] ARM: cci: driver need big endian fixes in asm code Victor Kamensky
2013-10-08 17:51 ` Dave Martin
2013-10-08 17:57 ` Nicolas Pitre
2013-10-08 18:03 ` Dave Martin
2013-10-08 18:14 ` Victor Kamensky
2013-10-08 18:26 ` Nicolas Pitre
2013-10-08 7:27 ` [PATCH 0/2] additional vexpress-tc2 big endian fixes Ben Dooks
[not found] <20131008175553.GB3866@localhost.localdomain>
2013-10-08 18:28 ` [PATCH 1/2] ARM: mcpm: fix big endian issue in mcpm startup code Nicolas Pitre
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=1381207040-1623-2-git-send-email-victor.kamensky@linaro.org \
--to=victor.kamensky@linaro.org \
--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).