From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH v2 1/2] Reserve secure memory
Date: Thu, 12 Nov 2015 08:42:46 -0800 [thread overview]
Message-ID: <5644C186.6020300@freescale.com> (raw)
In-Reply-To: <1447309701.2262.245.camel@freescale.com>
On 11/11/2015 10:28 PM, Scott Wood wrote:
> On Wed, 2015-11-11 at 19:34 -0800, York Sun wrote:
>>
>> On 11/11/2015 06:17 PM, Thomas Chou wrote:
>>> Hi York,
>>>
>>> On 2015?11?12? 06:50, York Sun wrote:
>>>> diff --git a/include/asm-generic/global_data.h b/include/asm
>>>> -generic/global_data.h
>>>> index d0383f3..336f3a0 100644
>>>> --- a/include/asm-generic/global_data.h
>>>> +++ b/include/asm-generic/global_data.h
>>>> @@ -58,6 +58,7 @@ typedef struct global_data {
>>>>
>>>> unsigned long relocaddr; /* Start address of U-Boot in
>>>> RAM */
>>>> phys_size_t ram_size; /* RAM size */
>>>> + phys_addr_t secure_ram; /* Secure memory addr */
>>>
>>> Shouldn't this be included only if CONFIG_SYS_MEM_RESERVE_SECURE ?
>>
>> It can be. It will require checking CONFIG_SYS_MEM_RESERVE_SECURE every time
>> this variable is used. I will add it in next version.
>
> Why would that be better than leaving it unifdeffed?
Save a few bytes? I prefer not to use ifdef if possible, but I understand some
platforms don't want to spare a few bytes.
York
next prev parent reply other threads:[~2015-11-12 16:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 22:50 [U-Boot] [RFC PATCH v2 0/2] Make most DDR non-secure in MMU while keep a small block secure York Sun
2015-11-11 22:50 ` [U-Boot] [RFC PATCH v2 1/2] Reserve secure memory York Sun
2015-11-12 2:17 ` Thomas Chou
2015-11-12 3:34 ` York Sun
2015-11-12 6:28 ` Scott Wood
2015-11-12 16:42 ` York Sun [this message]
2015-11-11 22:50 ` [U-Boot] [RFC PATCH v2 2/2] armv8: fsl-layerscape: Make DDR non secure in MMU tables York Sun
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=5644C186.6020300@freescale.com \
--to=yorksun@freescale.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