From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARMv8 switching CPUs into EL1
Date: Tue, 11 Jun 2019 10:51:35 +0200 [thread overview]
Message-ID: <20190611105135.36539932@jawa> (raw)
In-Reply-To: <CALVHrLe4ksNoMYpGopPpGLYOmcEzG4gHDQvsyN37Y1oAGBPPRw@mail.gmail.com>
Hi Mels,
> L.S.!
>
> On a Xilinx ZynqMP-based platform with u-boot running in Aarch64 mode
> in EL2, after booting a Linux kernel in EL1 using
> CONFIG_ARMV8_SWITCH_TO_EL1, Linux throws a warning that the CPUs have
> started in inconsistent modes ("CPU: CPUs started in inconsistent
> modes"). Indeed, only the first core on which U-boot was running is
> switched to EL1 at this point.
>
> Is this a bug or a not completely supported feature in U-boot or can
> this warning actually be safely ignored under certain circumstances?
>
U-boot by design starts on Core0. Other cores are not touched and are
managed (started/configured) by Linux.
The other question is if you use the ARM Trusted Firmware [ATF]. If you
start/load it in U-Boot (or any earlier bootloader), then it also may
change / configure CPUs state.
> Kind regards,
>
> Mels
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190611/f4a35cea/attachment.sig>
next prev parent reply other threads:[~2019-06-11 8:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 13:15 [U-Boot] ARMv8 switching CPUs into EL1 Mels van Broekhoven
2019-06-11 8:51 ` Lukasz Majewski [this message]
2019-06-11 12:09 ` Michal Simek
2019-06-11 12:39 ` Mark Kettenis
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=20190611105135.36539932@jawa \
--to=lukma@denx.de \
--cc=u-boot@lists.denx.de \
/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