From: Thierry Reding <treding@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/4] ARM: tegra210: gpu: configure WPR region
Date: Mon, 9 Nov 2015 16:48:27 +0100 [thread overview]
Message-ID: <20151109154742.GE11362@ulmo.nvidia.com> (raw)
In-Reply-To: <5640B994.7050307@wwwdotorg.org>
On Mon, Nov 09, 2015 at 08:19:48AM -0700, Stephen Warren wrote:
> On 11/09/2015 07:36 AM, Thierry Reding wrote:
> >On Wed, Oct 28, 2015 at 11:59:04AM -0600, Stephen Warren wrote:
> >>On 10/18/2015 10:57 PM, Alexandre Courbot wrote:
> >>>T210's GPU secure firmware loading requires a write-protected region
> >>>to be set up.
> >>>
> >>>This patch reserves the upper 256KB of RAM as the WPR region and locks
> >>>it so the kernel can initiate secure firmware loading.
> >>
> >>On T210, it's the responsibility of nvtboot (which runs before U-Boot) to
> >>set up any and all carve-outs. This code should not be necessary, and indeed
> >>I expect the registers it touches can't actually be programmed from U-Boot,
> >>which runs in non-secure mode after WPR is already locked.
> >
> >Can we document this assumption somewhere? It's entirely possible that
> >someone might want to run U-Boot without nvtboot
>
> That's not currently a supported use-case.
Isn't the whole point of open-source for people to be able to do all the
things that aren't supported?
> >, in which case nvtboot
> >would still need to be responsible for setting this up.
>
> I assume s/nvtboot/whatever other bootloader is in use/?
Right, I was going to write U-Boot here, but that's obviously only true
if U-Boot is still running in secure mode. Otherwise, yes, it'd be what-
ever is the other bootloader being used.
> >Or if it isn't
> >we could still point at some location where the interactions between a
> >first stage bootloader and U-Boot are documented.
> >
> >Do we have a document of this kind already?
>
> The L4T U-Boot source code:-)
There's a bunch of things that even the L4T U-Boot doesn't document. The
fact that it doesn't initialize the SMMU or WPR doesn't indicate that it
is something that a first stage bootloader needs to do.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151109/a549d793/attachment.sig>
next prev parent reply other threads:[~2015-11-09 15:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 4:57 [U-Boot] [PATCH 0/4] ARM: tegra: GPU WPR region support Alexandre Courbot
2015-10-19 4:57 ` [U-Boot] [PATCH 1/4] ARM: tegra: remove vpr_configured() function Alexandre Courbot
2015-10-19 4:57 ` [U-Boot] [PATCH 2/4] ARM: tegra: simplify GPU setup Alexandre Courbot
2015-10-19 4:57 ` [U-Boot] [PATCH 3/4] ARM: tegra: rename GPU functions Alexandre Courbot
2015-10-28 17:57 ` Stephen Warren
2015-10-19 4:57 ` [U-Boot] [PATCH 4/4] ARM: tegra210: gpu: configure WPR region Alexandre Courbot
2015-10-28 17:59 ` Stephen Warren
2015-10-28 23:55 ` Alexandre Courbot
2015-10-29 3:47 ` Stephen Warren
2015-11-09 14:36 ` Thierry Reding
2015-11-09 15:19 ` Stephen Warren
2015-11-09 15:48 ` Thierry Reding [this message]
2015-11-09 16:18 ` Stephen Warren
2015-10-26 5:50 ` [U-Boot] [PATCH 0/4] ARM: tegra: GPU WPR region support Alexandre Courbot
2015-10-27 15:57 ` Tom Warren
2015-10-28 9:13 ` Alexandre Courbot
2015-10-28 15:44 ` Tom Warren
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=20151109154742.GE11362@ulmo.nvidia.com \
--to=treding@nvidia.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