From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: move firmware_ops to drivers/firmware
Date: Tue, 19 Nov 2013 11:02:16 +0000 [thread overview]
Message-ID: <20131119110216.GD26487@arm.com> (raw)
In-Reply-To: <528A64D2.4020107@codeaurora.org>
On Mon, Nov 18, 2013 at 07:04:50PM +0000, Christopher Covington wrote:
> On 11/18/2013 12:30 PM, Catalin Marinas wrote:
> [...]
> > You can't run legacy AArch32 code at EL3 and have lower levels in AArch64
> > mode (architectural constraint).
>
> What prevents AArch32 code from running at EL3 and then requesting a reset to
> AArch64 by writing to the Reset Management Register before sliding down to
> lower exception levels?
You can do this for some initial code but the firmware still needs to
switch to AArch64 before dropping to lower exception levels. What this
thread is about is run-time calls to firmware for booting secondary
CPUs, idle, l2x0. At this point, the code at EL3 must run in AArch64
mode. There is no way you can bounce between AArch32 and AArch64 modes
using reset just to handle some SMCs.
--
Catalin
next prev parent reply other threads:[~2013-11-19 11:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 8:49 [PATCH] ARM: move firmware_ops to drivers/firmware Alexandre Courbot
2013-11-17 15:59 ` Catalin Marinas
2013-11-18 3:05 ` Alex Courbot
2013-11-18 11:58 ` Catalin Marinas
2013-11-18 17:03 ` Stephen Warren
2013-11-18 17:10 ` Russell King - ARM Linux
2013-11-18 17:18 ` Stephen Warren
2013-11-18 17:30 ` Catalin Marinas
2013-11-18 17:52 ` Stephen Warren
2013-11-19 11:38 ` Catalin Marinas
2013-11-18 19:04 ` Christopher Covington
2013-11-19 11:02 ` Catalin Marinas [this message]
2013-11-19 2:46 ` Alex Courbot
2013-11-19 12:26 ` Catalin Marinas
2013-11-19 14:29 ` Alexandre Courbot
2013-11-19 15:07 ` Catalin Marinas
2013-11-19 15:17 ` Alexandre Courbot
2013-11-18 17:00 ` Stephen Warren
2013-11-18 17:23 ` Catalin Marinas
2013-11-18 17:14 ` Russell King - ARM Linux
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=20131119110216.GD26487@arm.com \
--to=catalin.marinas@arm.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).