All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jagan Teki <jagan@amarulasolutions.com>
To: Jonas Karlman <jonas@kwiboo.se>
Cc: Simon Glass <sjg@chromium.org>,
	Philipp Tomsich <philipp.tomsich@vrull.eu>,
	Kever Yang <kever.yang@rock-chips.com>,
	Joseph Chen <chenjh@rock-chips.com>,
	 Alper Nebi Yasak <alpernebiyasak@gmail.com>,
	 Quentin Schulz <quentin.schulz@theobroma-systems.com>,
	Jagan Teki <jagan@edgeble.ai>,
	 Heinrich Schuchardt <xypron.glpk@gmx.de>,
	u-boot@lists.denx.de
Subject: Re: [PATCH v2 2/6] rockchip: Use an external TPL binary on RK3568
Date: Thu, 16 Feb 2023 14:36:50 +0530	[thread overview]
Message-ID: <CAMty3ZAp6MGRLdjXMi0ORAPof3T=Pv+CdFubHJq36UC0Gr0cMA@mail.gmail.com> (raw)
In-Reply-To: <20230214103300.690542-3-jonas@kwiboo.se>

On Tue, Feb 14, 2023 at 4:03 PM Jonas Karlman <jonas@kwiboo.se> wrote:
>
> Rockchip SoCs typically use U-Boot TPL to initialize DRAM, then jumps
> back to BootRom to load next stage, U-Boot SPL, into DRAM. BootRom then
> jumps to U-Boot SPL to continue the normal boot flow.
>
> However, there is no support to initialize DRAM on RK35xx SoCs using
> U-Boot TPL and instead an external TPL binary must be used to generate a
> bootable u-boot-rockchip.bin image.
>
> Add CONFIG_ROCKCHIP_EXTERNAL_TPL to indicate that an external TPL should
> be used. Build U-Boot with ROCKCHIP_TPL=/path/to/ddr.bin to generate a
> bootable u-boot-rockchip.bin image for RK3568.

Please add documentation in doc/board/rockchip/rockchip.rst and take
an example of a real DDR bin from rkbin.

Jagan.

  parent reply	other threads:[~2023-02-16  9:07 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-05 20:21 [PATCH 0/3] rockchip: Use external TPL binary to create a working firmware image Jonas Karlman
2023-02-05 20:21 ` [PATCH 1/3] binman: Add support for an external-tpl entry Jonas Karlman
2023-02-07  4:02   ` Simon Glass
2023-02-05 20:21 ` [PATCH 2/3] rockchip: Require an external TPL binary when TPL is missing Jonas Karlman
2023-02-05 20:28   ` Jagan Teki
2023-02-05 20:34     ` Jonas Karlman
2023-02-06 11:26   ` Quentin Schulz
2023-02-06 12:51     ` Jonas Karlman
2023-02-14  3:45       ` Kever Yang
2023-02-14 10:52         ` Jonas Karlman
2023-02-08 15:41     ` Kever Yang
2023-02-08 16:06       ` Quentin Schulz
2023-02-14  3:42         ` Kever Yang
2023-02-07  4:02   ` Simon Glass
2023-02-05 20:21 ` [PATCH 3/3] Revert "board: rockchip: Fix binman_init failure on EVB-RK3568" Jonas Karlman
2023-02-07  4:02   ` Simon Glass
2023-02-07  4:02 ` [PATCH 0/3] rockchip: Use external TPL binary to create a working firmware image Simon Glass
2023-02-08 14:53   ` Jonas Karlman
2023-02-14 10:33 ` [PATCH v2 0/5] " Jonas Karlman
2023-02-14 10:33   ` [PATCH v2 1/6] binman: Add support for a rockchip-tpl entry Jonas Karlman
2023-02-14 19:48     ` Simon Glass
2023-02-14 20:35       ` Jonas Karlman
2023-02-16  7:50     ` Kever Yang
2023-02-16 11:26     ` Eugen Hristev
2023-02-16 14:02       ` Jonas Karlman
2023-02-14 10:33   ` [PATCH v2 2/6] rockchip: Use an external TPL binary on RK3568 Jonas Karlman
2023-02-14 19:48     ` Simon Glass
2023-02-15  9:54       ` Jonas Karlman
2023-02-16  7:51     ` Kever Yang
2023-02-16  9:06     ` Jagan Teki [this message]
2023-02-14 10:33   ` [PATCH v2 3/6] Revert "board: rockchip: Fix binman_init failure on EVB-RK3568" Jonas Karlman
2023-02-16  7:51     ` Kever Yang
2023-02-14 10:33   ` [PATCH v2 4/6] rockchip: mkimage: Update init size limit Jonas Karlman
2023-02-16  7:59     ` Kever Yang
2023-02-16 14:36       ` Jonas Karlman
2023-02-14 10:33   ` [PATCH v2 5/6] rockchip: evb-rk3568: Update defconfig Jonas Karlman
2023-02-14 10:34   ` [PATCH v2 6/6] RFC: binman: Improve allow missing for mkimage entry Jonas Karlman
2023-02-14 19:48     ` Simon Glass
2023-02-15 18:25       ` Jonas Karlman
2023-02-17  2:55         ` Simon Glass
2023-02-17 14:42           ` Jonas Karlman

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='CAMty3ZAp6MGRLdjXMi0ORAPof3T=Pv+CdFubHJq36UC0Gr0cMA@mail.gmail.com' \
    --to=jagan@amarulasolutions.com \
    --cc=alpernebiyasak@gmail.com \
    --cc=chenjh@rock-chips.com \
    --cc=jagan@edgeble.ai \
    --cc=jonas@kwiboo.se \
    --cc=kever.yang@rock-chips.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=quentin.schulz@theobroma-systems.com \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.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.