From: Scott Wood <oss@buserror.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHv2 2/3] ARMv8/layerscape: Add FSL PPA support
Date: Fri, 22 Jan 2016 14:09:17 -0600 [thread overview]
Message-ID: <1453493357.19133.93.camel@buserror.net> (raw)
In-Reply-To: <AM4PR0401MB1732A70624692854A931E91E9AC40@AM4PR0401MB1732.eurprd04.prod.outlook.com>
On Fri, 2016-01-22 at 20:05 +0000, york sun wrote:
> On 01/21/2016 01:53 AM, Zhiqiang Hou wrote:
> > From: Hou Zhiqiang <Zhiqiang.Hou@freescale.com>
> >
> > The FSL Primary Protected Application (PPA) is a software component
> > loaded during boot which runs in TrustZone and remains resident
> > after boot.
> >
> > Signed-off-by: Hou Zhiqiang <Zhiqiang.Hou@freescale.com>
> > ---
> > Tested on LS1043A RDB board
> >
>
> I presume PSCI is implemented in PPA. How does the SMP boot flow change with
> PPA? U-boot has to remain functional in the absence of PPA, right?
>
> Would it be possible to write a readme for PPA?
Also, how does the devicetree get updated to indicate the presence of PSCI?
-Scott
next prev parent reply other threads:[~2016-01-22 20:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 9:44 [U-Boot] [PATCHv2 1/3] armv8: fsl-layerscape: add i/d-cache enable function to enable_caches Zhiqiang Hou
2016-01-21 9:44 ` [U-Boot] [PATCHv2 2/3] ARMv8/layerscape: Add FSL PPA support Zhiqiang Hou
2016-01-22 20:05 ` york sun
2016-01-22 20:09 ` Scott Wood [this message]
2016-01-22 20:14 ` Bhupesh Sharma
2016-01-22 20:17 ` Scott Wood
2016-01-22 20:26 ` Bhupesh Sharma
2016-01-25 3:11 ` Zhiqiang Hou
2016-01-22 20:18 ` york sun
2016-01-22 20:21 ` Scott Wood
2016-01-22 20:27 ` Bhupesh Sharma
2016-01-22 20:30 ` york sun
2016-01-25 3:22 ` Zhiqiang Hou
2016-03-17 21:09 ` york sun
2016-03-23 3:17 ` Zhiqiang Hou
2016-01-22 20:32 ` Scott Wood
2016-01-25 3:15 ` Zhiqiang Hou
2016-01-25 3:16 ` Zhiqiang Hou
2016-01-25 3:09 ` Zhiqiang Hou
2016-01-25 3:02 ` Zhiqiang Hou
2016-01-21 9:44 ` [U-Boot] [PATCHv2 3/3] ARMv8/ls1043ardb: Integrate FSL PPA Zhiqiang Hou
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=1453493357.19133.93.camel@buserror.net \
--to=oss@buserror.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.