From: Kever Yang <kever.yang@rock-chips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] rk3399: reseve space for trust
Date: Mon, 25 Jul 2016 10:00:21 +0800 [thread overview]
Message-ID: <579572B5.7080705@rock-chips.com> (raw)
In-Reply-To: <CAPnjgZ1d+Z53TDCqfcagbebvsU-zOd4C65axvfZuMv9FedVZmw@mail.gmail.com>
Hi Simon,
On 07/23/2016 11:03 AM, Simon Glass wrote:
> Hi again,
>
> On 22 July 2016 at 20:57, Simon Glass <sjg@chromium.org> wrote:
>> Hi Kever,
>>
>> On 22 July 2016 at 03:34, Kever Yang <kever.yang@rock-chips.com> wrote:
>>
>> For the commit message, you have "rk3399: reseve space for trust".
>>
>> I think it should be "rk3399: Reseve space for ARM Trusted Firmware"
>> or perhaps ATF
> Ooops I mean 'Reserve' !
I though the memory is used by ATF BL31 and BL32 which is not including
in ATF,
this reserve memory only use for ATF BL31 in fact, so I will send
Version 2 with all
you comments applied.
Thanks,
- Kever
>
>>
>>> rk3399 need reserve 0x200000 at the begining of DRAM, for ATF usage.
>> needs
>> beginning
>> s/usage/use/
>>
>>> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
>>> ---
>>>
>>> board/rockchip/evb_rk3399/evb-rk3399.c | 3 ++-
>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/board/rockchip/evb_rk3399/evb-rk3399.c b/board/rockchip/evb_rk3399/evb-rk3399.c
>>> index dffacd0..37d3851 100644
>>> --- a/board/rockchip/evb_rk3399/evb-rk3399.c
>>> +++ b/board/rockchip/evb_rk3399/evb-rk3399.c
>>> @@ -21,6 +21,7 @@ int dram_init(void)
>>>
>>> void dram_init_banksize(void)
>>> {
>>> - gd->bd->bi_dram[0].start = 0;
>>> + /* Reserve 0x200000 for trust word */
>> What does 'trust word' mean? Do you mean space for ATF, or a single
>> word of memory?
>>
>>> + gd->bd->bi_dram[0].start = 0x200000;
>>> gd->bd->bi_dram[0].size = 0x80000000;
>>> }
>>> --
>>> 1.9.1
>>>
>>>
>> Regards,
>> Simon
>
> Regards,
> Simon
>
prev parent reply other threads:[~2016-07-25 2:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 9:34 [U-Boot] [PATCH] rk3399: reseve space for trust Kever Yang
2016-07-23 2:57 ` Simon Glass
2016-07-23 3:03 ` Simon Glass
2016-07-25 2:00 ` Kever Yang [this message]
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=579572B5.7080705@rock-chips.com \
--to=kever.yang@rock-chips.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