From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm:ls1021a: Reserve secure code into RAM instead of OCRAM
Date: Thu, 16 Apr 2015 13:02:35 -0700 [thread overview]
Message-ID: <5530155B.5060509@freescale.com> (raw)
In-Reply-To: <1427189257-18214-1-git-send-email-Zhuoyu.Zhang@freescale.com>
On 03/24/2015 02:27 AM, Zhuoyu Zhang wrote:
> For ls1021a, Reserve secure code in to memory in case OCRAM
> is needed by other usage.
>
> Signed-off-by: Zhuoyu Zhang <Zhuoyu.Zhang@freescale.com>
> ---
> include/configs/ls1021aqds.h | 1 -
> include/configs/ls1021atwr.h | 1 -
> 2 files changed, 2 deletions(-)
>
> diff --git a/include/configs/ls1021aqds.h b/include/configs/ls1021aqds.h
> index 3dc4da3..42439a4 100644
> --- a/include/configs/ls1021aqds.h
> +++ b/include/configs/ls1021aqds.h
> @@ -554,7 +554,6 @@ unsigned long get_board_ddr_clk(void);
> #define CONFIG_LS102XA_NS_ACCESS
> #define CONFIG_SMP_PEN_ADDR 0x01ee0200
> #define CONFIG_TIMER_CLK_FREQ 12500000
> -#define CONFIG_ARMV7_SECURE_BASE OCRAM_BASE_S_ADDR
>
> #define CONFIG_HWCONFIG
> #define HWCONFIG_BUFFER_SIZE 128
> diff --git a/include/configs/ls1021atwr.h b/include/configs/ls1021atwr.h
> index a13876b..dccc661 100644
> --- a/include/configs/ls1021atwr.h
> +++ b/include/configs/ls1021atwr.h
> @@ -347,7 +347,6 @@
> #define CONFIG_LS102XA_NS_ACCESS
> #define CONFIG_SMP_PEN_ADDR 0x01ee0200
> #define CONFIG_TIMER_CLK_FREQ 12500000
> -#define CONFIG_ARMV7_SECURE_BASE OCRAM_BASE_S_ADDR
>
> #define CONFIG_HWCONFIG
> #define HWCONFIG_BUFFER_SIZE 128
>
Zhuoyu,
I don't see how the secure code is reserved in RAM. You only remove
CONFIG_ARMV7_SECURE_BASE. Did I miss something?
York
next prev parent reply other threads:[~2015-04-16 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 9:27 [U-Boot] [PATCH] arm:ls1021a: Reserve secure code into RAM instead of OCRAM Zhuoyu Zhang
2015-04-16 20:02 ` York Sun [this message]
2015-07-29 2:25 ` Zhang Z.Y.
2015-07-31 6:02 ` Zhang Z.Y.
2015-08-03 2:29 ` Huan Wang
2015-08-04 15:43 ` 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=5530155B.5060509@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 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.