From: acourbot@nvidia.com (Alexandre Courbot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v11 6/7] ARM: tegra: set CPU reset handler using firmware
Date: Sun, 24 Nov 2013 15:30:51 +0900 [thread overview]
Message-ID: <1385274652-16415-7-git-send-email-acourbot@nvidia.com> (raw)
In-Reply-To: <1385274652-16415-1-git-send-email-acourbot@nvidia.com>
Use a firmware operation to set the CPU reset handler and only resort to
doing it ourselves if there is none defined.
This supports the booting of secondary CPUs on devices using a TrustZone
secure monitor.
Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
Reviewed-by: Tomasz Figa <t.figa@samsung.com>
Reviewed-by: Stephen Warren <swarren@nvidia.com>
---
arch/arm/mach-tegra/reset.c | 17 ++++++++++++++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-tegra/reset.c b/arch/arm/mach-tegra/reset.c
index 17c4b6d..146fe8e 100644
--- a/arch/arm/mach-tegra/reset.c
+++ b/arch/arm/mach-tegra/reset.c
@@ -21,6 +21,7 @@
#include <asm/cacheflush.h>
#include <asm/hardware/cache-l2x0.h>
+#include <asm/firmware.h>
#include "iomap.h"
#include "irammap.h"
@@ -65,6 +66,7 @@ static void __init tegra_cpu_reset_handler_enable(void)
void __iomem *iram_base = IO_ADDRESS(TEGRA_IRAM_RESET_BASE);
const u32 reset_address = TEGRA_IRAM_RESET_BASE +
tegra_cpu_reset_handler_offset;
+ int err;
BUG_ON(is_enabled);
BUG_ON(tegra_cpu_reset_handler_size > TEGRA_IRAM_RESET_HANDLER_SIZE);
@@ -72,9 +74,18 @@ static void __init tegra_cpu_reset_handler_enable(void)
memcpy(iram_base, (void *)__tegra_cpu_reset_handler_start,
tegra_cpu_reset_handler_size);
- tegra_cpu_reset_handler_set(reset_address);
-
- is_enabled = true;
+ err = call_firmware_op(set_cpu_boot_addr, 0, reset_address);
+ switch (err) {
+ case -ENOSYS:
+ tegra_cpu_reset_handler_set(reset_address);
+ /* pass-through */
+ case 0:
+ is_enabled = true;
+ break;
+ default:
+ pr_crit("Cannot set CPU reset handler: %d\n", err);
+ BUG();
+ }
}
void __init tegra_cpu_reset_handler_init(void)
--
1.8.4.2
next prev parent reply other threads:[~2013-11-24 6:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-24 6:30 [PATCH v11 0/7] ARM: support for the Trusted Foundations secure monitor Alexandre Courbot
2013-11-24 6:30 ` [PATCH v11 1/7] ARM: add basic support for Trusted Foundations Alexandre Courbot
2013-11-24 6:30 ` [PATCH v11 2/7] of: add vendor prefix for Trusted Logic Mobility Alexandre Courbot
2013-11-24 6:30 ` [PATCH v11 3/7] of: add Trusted Foundations bindings documentation Alexandre Courbot
2013-11-24 6:30 ` [PATCH v11 4/7] ARM: tegra: add support for Trusted Foundations Alexandre Courbot
2013-11-24 6:30 ` [PATCH v11 5/7] ARM: tegra: split setting of CPU reset handler Alexandre Courbot
2013-11-24 6:30 ` Alexandre Courbot [this message]
2013-11-24 6:30 ` [PATCH v11 7/7] ARM: tegra: support Trusted Foundations by default Alexandre Courbot
2013-11-26 0:06 ` Olof Johansson
2013-11-26 1:35 ` Alexandre Courbot
2013-11-26 16:47 ` Dave Martin
2013-11-28 6:02 ` Alexandre Courbot
2013-11-28 16:58 ` Stephen Warren
2013-11-28 19:47 ` Dave Martin
2013-11-29 1:07 ` Alex Courbot
2013-11-26 0:10 ` [PATCH v11 0/7] ARM: support for the Trusted Foundations secure monitor Olof Johansson
2013-12-03 0:48 ` Alexandre Courbot
2013-12-09 17:21 ` Stephen Warren
2013-12-13 19:57 ` Stephen Warren
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=1385274652-16415-7-git-send-email-acourbot@nvidia.com \
--to=acourbot@nvidia.com \
--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).