From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Warren <swarren@wwwdotorg.org>
Date: Thu, 15 Jan 2015 16:49:40 -0700
Subject: [U-Boot] [PATCH v1 2/4] virt-dt: Allow reservation of the
 secure region when it is in a RAM carveout.
In-Reply-To: <1421178360-23778-2-git-send-email-ijc@hellion.org.uk>
References: <1421178290.11796.159.camel@hellion.org.uk>
	<1421178360-23778-2-git-send-email-ijc@hellion.org.uk>
Message-ID: <54B85214.1010300@wwwdotorg.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 01/13/2015 12:45 PM, Ian Campbell wrote:
> In this case the secure code lives in RAM, and hence needs to be reserved, but
> it has been relocated, so the reservation of __secure_start does not apply.
>
> Add support for setting CONFIG_ARMV7_SECURE_RESERVE_SIZE to reserve such a
> region.
>
> This will be used in a subsequent patch for Jetson-TK1

It's rather hard to review this without any documentation in the README, 
of the new symbol, or any of the existing:

CONFIG_ARMV7_NONSEC
CONFIG_ARMV7_VIRT
CONFIG_ARMV7_PSCI

It'd be nice to have a description of what those do exactly, and how 
they interact or conflict.