From: Ley Foon Tan <ley.foon.tan@intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] ARM: rmobile: Switch CPU to non-secure HYP mode for r8a7790 based boards
Date: Wed, 13 Mar 2019 19:42:41 +0800 [thread overview]
Message-ID: <1552477361.5582.18.camel@intel.com> (raw)
In-Reply-To: <32d3d083-7e91-d12a-70b0-a677ac1d2e6f@gmail.com>
On Thu, 2019-03-14 at 01:16 +0100, Marek Vasut wrote:
> On 2/12/19 8:52 PM, Oleksandr wrote:
>
> Hi,
>
> [...]
>
> I was thinking about this whole PSCI situation and how it's all
> implemented today. Basically what we do is generate a separate
> reduced
> shred of U-Boot, which will remain resident in memory and which could
> be
> called by some other software. That shred is a piece of U-Boot
> proper,
> but a lot of stuff is just torn away at runtime, so it's not the
> whole
> binary, just tattered remnants of it.
>
> I really do not like this approach to the whole U-Boot PSCI in the
> first
> place, it seems really fragile and dangerous.
>
> But look, U-Boot already has support for U-Boot SPL/TPL, which is
> small,
> can contain a full driver model, drivers and all the necessary
> support
> functionality. It is built from the same sources, at the same time,
> but
> it is not a shred of U-Boot proper but rather a separate entity.
>
> So I wonder, can't we use this U-Boot SPL/TPL as the piece of code
> which
> would remain resident in memory and handle the PSCI calls instead ? I
> think U-Boot can load such a code or it could be somehow bundled with
> U-Boot proper (using a fitImage maybe ?). This way you won't have to
> re-implement all the drivers in arch/arm/, the DM/DT remains in place
> and the whole PSCI handler would be self-contained, so no need to
> fiddle
> with linker sections of U-Boot itself.
>
> I am CCing other people who use this PSCI stuff in U-Boot, maybe they
> have some thoughts on this approach.
>
> And I apologize again for taking this long to reply.
>
> [...]
>
Adding Chin Liang and Jeremy.
Regards
Ley Foon
next prev parent reply other threads:[~2019-03-13 11:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 17:38 [U-Boot] [PATCH 0/3] PSCI support for r8a7790 SoC (Lager/Stout boards) Oleksandr Tyshchenko
2019-01-31 17:38 ` [U-Boot] [PATCH 1/3] ARM: rmobile: Switch CPU to non-secure HYP mode for r8a7790 based boards Oleksandr Tyshchenko
2019-02-05 18:48 ` Marek Vasut
2019-02-07 15:28 ` Oleksandr
2019-02-07 15:49 ` Marek Vasut
2019-02-07 17:19 ` Oleksandr
2019-02-08 11:40 ` Oleksandr
2019-02-09 16:37 ` Marek Vasut
2019-02-12 21:20 ` Oleksandr
2019-02-26 18:37 ` Oleksandr
2019-02-27 20:50 ` Marek Vasut
2019-02-09 16:35 ` Marek Vasut
2019-02-12 19:52 ` Oleksandr
2019-03-14 0:16 ` Marek Vasut
2019-03-13 11:42 ` Ley Foon Tan [this message]
2019-03-14 11:37 ` Oleksandr
2019-03-18 10:45 ` Patrick DELAUNAY
2019-01-31 17:38 ` [U-Boot] [PATCH 2/3] ARM: rmobile: Add basic PSCI support for r8a7790 SoC Oleksandr Tyshchenko
2019-02-05 18:55 ` Marek Vasut
2019-02-08 10:52 ` Oleksandr
2019-02-09 16:32 ` Marek Vasut
2019-02-11 20:10 ` Oleksandr
2019-02-11 20:40 ` Marek Vasut
2019-02-12 19:26 ` Oleksandr
2019-02-26 19:37 ` Oleksandr
2019-02-27 20:53 ` Marek Vasut
2019-02-27 21:16 ` Oleksandr Tyshchenko
2019-01-31 17:38 ` [U-Boot] [PATCH 3/3] ARM: rmobile: Add possibility to debug main PSCI commands Oleksandr Tyshchenko
2019-02-05 18:56 ` Marek Vasut
2019-02-08 12:47 ` Oleksandr
2019-02-09 16:24 ` Marek Vasut
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=1552477361.5582.18.camel@intel.com \
--to=ley.foon.tan@intel.com \
--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