From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] TPL/SPL: add separate CONFIG_TPL_FRAMEWORK for TPL
Date: Tue, 28 Aug 2018 08:49:39 -0400 [thread overview]
Message-ID: <20180828124939.GT26633@bill-the-cat> (raw)
In-Reply-To: <20180828085126.27562-1-kever.yang@rock-chips.com>
On Tue, Aug 28, 2018 at 04:51:26PM +0800, Kever Yang wrote:
> SPL_FRAMEWORK is a set of framework feature, we may not need the
> fromework for both TPL and SPL at the same time, so add a separate
> one for TPL.
>
> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> ---
>
> Makefile | 2 +-
> arch/arm/lib/Makefile | 4 ++--
> arch/arm/lib/crt0.S | 6 +++++-
> common/spl/Kconfig | 9 +++++++++
> common/spl/Makefile | 2 +-
> scripts/Makefile.spl | 4 ++++
> 6 files changed, 22 insertions(+), 5 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 4b3023b259..68b77d1e43 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -822,7 +822,7 @@ endif
> endif
> ALL-$(CONFIG_TPL) += tpl/u-boot-tpl.bin
> ALL-$(CONFIG_OF_SEPARATE) += u-boot.dtb
> -ifeq ($(CONFIG_SPL_FRAMEWORK),y)
> +ifeq ($(CONFIG_TPL_FRAMEWORK),y)
> ALL-$(CONFIG_OF_SEPARATE) += u-boot-dtb.img
> endif
> ALL-$(CONFIG_OF_HOSTFILE) += u-boot.dtb
We should be adding a new stanza here and not replacing the SPL one I
would think.
[snip]
> diff --git a/common/spl/Kconfig b/common/spl/Kconfig
> index db1915fe5c..1a2e10b892 100644
> --- a/common/spl/Kconfig
> +++ b/common/spl/Kconfig
> @@ -813,6 +813,15 @@ config TPL
> help
> If you want to build TPL as well as the normal image and SPL, say Y.
>
> +config TPL_FRAMEWORK
> + bool "Support TPL based upon the common TPL framework"
> + depends on TPL
> + default y
> + help
> + Enable the TPL framework under common/spl/. This framework
> + re-use the all the framework feature from SPL but enable separetely.
> + If unsure, say Y.
This shouldn't be default y, and the help shouldn't suggest that either
I think. My concern with this series is TPL wasn't intended to get too
featureful. Our initial constraints are enough that we need something
to init DDR and load SPL into that as we can't do enough with our
limited resources to load full U-Boot. In fact, looking at the follow
up rockchip specific patch that's more in line what my expectations. So
I think you should be able to get TPL to do what you want without
introducing TPL_FRAMEWORK. Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180828/a466498d/attachment.sig>
next prev parent reply other threads:[~2018-08-28 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 8:51 [U-Boot] [PATCH] TPL/SPL: add separate CONFIG_TPL_FRAMEWORK for TPL Kever Yang
2018-08-28 12:49 ` Tom Rini [this message]
2018-08-28 13:11 ` Kever Yang
2018-08-29 1:55 ` Tom Rini
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=20180828124939.GT26633@bill-the-cat \
--to=trini@konsulko.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