u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
To: Kever Yang <kever.yang@rock-chips.com>, u-boot@lists.denx.de
Cc: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>,
	Philipp Tomsich <philipp.tomsich@vrull.eu>,
	Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH] rockchip: Only call binman when TPL available
Date: Mon, 2 Jan 2023 12:23:39 +0100	[thread overview]
Message-ID: <9dab61dc-c266-c799-12df-b83b192979ca@theobroma-systems.com> (raw)
In-Reply-To: <20221218205013.1.I2299f1eddce5aa7d5fb1a3fb4d8aeaa995b397fa@changeid>

Hi Kever,

On 12/18/22 13:50, Kever Yang wrote:
> Rockchip platform use TPL to do the DRAM initialize for all the SoCs,
> if TPL is not available, means no available DRAM init program, and the

Why would the TPL not be available?

Are you thinking about the TPL being provided externally as a blob?

Also, we literally had less than 24h to review this patch before it was 
merged (without review) in rc3....

Can you please explain what's the issue so we know what we have to deal 
with in the future? Because the commit log is not precise enough for me 
to understand the corner case you hit.

Cheers,
Quentin

> u-boot-rockchip.bin is not functionable.
> 
> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> ---
> 
>   arch/arm/dts/rockchip-u-boot.dtsi | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arm/dts/rockchip-u-boot.dtsi b/arch/arm/dts/rockchip-u-boot.dtsi
> index 584f21eb5bf..e2b0f389711 100644
> --- a/arch/arm/dts/rockchip-u-boot.dtsi
> +++ b/arch/arm/dts/rockchip-u-boot.dtsi
> @@ -11,7 +11,7 @@
>   	};
>   };
>   
> -#ifdef CONFIG_SPL
> +#ifdef CONFIG_TPL_BUILD
>   &binman {
>   	simple-bin {
>   		filename = "u-boot-rockchip.bin";

      parent reply	other threads:[~2023-01-02 11:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-18 12:50 [PATCH] rockchip: Only call binman when TPL available Kever Yang
2022-12-19 19:20 ` Simon Glass
2023-01-02 11:23 ` Quentin Schulz [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=9dab61dc-c266-c799-12df-b83b192979ca@theobroma-systems.com \
    --to=quentin.schulz@theobroma-systems.com \
    --cc=kever.yang@rock-chips.com \
    --cc=philipp.tomsich@theobroma-systems.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=sjg@chromium.org \
    --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;
as well as URLs for NNTP newsgroup(s).