From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: EL3 firmware init of cores ( was Re: [PATCH] arm64: Flush the process's mm context TLB entries when switching)
Date: Mon, 28 Jul 2014 19:46:04 +0100 [thread overview]
Message-ID: <20140728184604.GS15536@arm.com> (raw)
In-Reply-To: <CALRxmdCxnOmZdY=_CCYRT8YYBkVdS-ch6RRbkfZa2B-sF_FkKg@mail.gmail.com>
Hi Stuart,
On Mon, Jul 28, 2014 at 07:40:27PM +0100, Stuart Yoder wrote:
> On Tue, Apr 15, 2014 at 3:02 AM, Will Deacon <will.deacon@arm.com> wrote:
> > No, there's usually a CPU-specific register (called something like actlr or
> > ectlr) which contains bit(s) to enable TLB broadcasting in hardware. Which
> > CPU are you using?
>
> We ran into this same issue as well for an A57-based system. We are using
> u-boot and it seems that some early EL3 init was missing the setting of the
> SMPEN bit.
>
> I'm concerned now that there may be other bits we have missed as well. Is
> there any documentation you know of that details A57 initialization or do we
> just have to extract that from the reference manual?
>
> Also, for ARM development systems like the Versatile Express or fast model
> is there existing "EL3 firmware" source available that shows how to properly
> initialize an A57 that we can refer to? Any pointer to reference code doing
> this initialization would be really appreciated.
Sure, take a look at the ARM trusted firmware:
https://github.com/ARM-software/arm-trusted-firmware
That's actually the firmware that runs on Juno at EL3 and provides a bunch
of stuff as well as initialising the platform (PSCI etc). For example, the
SMP bit is set in lib/aarch64/cpu_helpers.S
Will
prev parent reply other threads:[~2014-07-28 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 18:40 EL3 firmware init of cores ( was Re: [PATCH] arm64: Flush the process's mm context TLB entries when switching) Stuart Yoder
2014-07-28 18:46 ` Will Deacon [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=20140728184604.GS15536@arm.com \
--to=will.deacon@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).