From: Kever Yang <kever.yang@rock-chips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] spl: atf: fix the plat_params
Date: Fri, 15 Dec 2017 11:27:17 +0800 [thread overview]
Message-ID: <1513308437-32162-1-git-send-email-kever.yang@rock-chips.com> (raw)
The latest upstream ATF still not support using a fdt base as plat_params,
I get error like this:
"ERROR: not expected type found 6410029648624618960"
The reason is the ATF source code parse the plat_param, and can not
decode the type in:
/* common header for all plat parameter type */
struct bl31_plat_param {
uint64_t type;
void *next;
};
void params_early_setup(void *plat_param_from_bl2)
plat/rockchip/common/params_setup.c
We can only use the fdt_addr as plat_params after upstream ATF able to
parse it.
BUGFIX to:
1d37909 spl: atf: introduce spl_invoke_atf and make bl31_entry private
Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
---
common/spl/spl_atf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/spl/spl_atf.c b/common/spl/spl_atf.c
index 63557c0..a65d603 100644
--- a/common/spl/spl_atf.c
+++ b/common/spl/spl_atf.c
@@ -96,7 +96,7 @@ static void bl31_entry(uintptr_t bl31_entry, uintptr_t bl33_entry,
raw_write_daif(SPSR_EXCEPTION_MASK);
dcache_disable();
- atf_entry((void *)bl31_params, (void *)fdt_addr);
+ atf_entry((void *)bl31_params, NULL);
}
static int spl_fit_images_find_uboot(void *blob)
--
1.9.1
next reply other threads:[~2017-12-15 3:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 3:27 Kever Yang [this message]
2017-12-15 9:07 ` [U-Boot] [PATCH] spl: atf: fix the plat_params Dr. Philipp Tomsich
2017-12-19 2:03 ` Kever Yang
2017-12-27 8:44 ` Kever Yang
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=1513308437-32162-1-git-send-email-kever.yang@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 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.