From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Jeffy Chen <jeffy.chen@rock-chips.com>,
Kever Yang <kever.yang@rock-chips.com>,
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>,
huang lin <hl@rock-chips.com>
Subject: Re: [PATCH v2 13/14] rockchip: Enable bootstage on rockpro64
Date: Sun, 8 Jan 2023 08:48:51 -0700 [thread overview]
Message-ID: <CAPnjgZ3UvEPC_QCwJT=DCPsy_cW+wEuvMCLpfwt0136bHvje9Q@mail.gmail.com> (raw)
In-Reply-To: <20230107215731.484317-14-sjg@chromium.org>
On Sat, 7 Jan 2023 at 14:57, Simon Glass <sjg@chromium.org> wrote:
>
> This board is useful for benchmarking overall U-Boot performance. Enable
> the bootstage feature so we get a report.
>
> Since this returns to the boot rom before finishing executing
> board_init_r() in SPL, add a few bootstage calls so that we can collect
> timing from TPL.
>
> For the stash region, use a portion of SRAM, 64KB below the stack top.
> This allows the TPL image to be up to nearly 120KB (it is typically about
> 64KB). SPL normally runs from SDRAM at 0, so can use the same stash
> region.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> Changes in v2:
> - Drop unwanted debugging
>
> arch/arm/mach-rockchip/tpl.c | 16 +++++++++++++---
> configs/rockpro64-rk3399_defconfig | 8 ++++++++
> 2 files changed, 21 insertions(+), 3 deletions(-)
>
Applied to u-boot-dm/next
next prev parent reply other threads:[~2023-01-08 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 21:57 [PATCH v2 03/14] tpm: Add a proper Kconfig option for crc8 in SPL Simon Glass
2023-01-07 21:57 ` [PATCH v2 13/14] rockchip: Enable bootstage on rockpro64 Simon Glass
2023-01-08 15:48 ` Simon Glass [this message]
2023-02-11 23:29 ` Andrew Abbott
2023-02-14 0:01 ` Simon Glass
2023-01-08 2:40 ` [PATCH v2 03/14] tpm: Add a proper Kconfig option for crc8 in SPL Simon Glass
-- strict thread matches above, loose matches on Subject: below --
2022-12-22 21:14 [PATCH v2 13/14] rockchip: Enable bootstage on rockpro64 Simon Glass
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='CAPnjgZ3UvEPC_QCwJT=DCPsy_cW+wEuvMCLpfwt0136bHvje9Q@mail.gmail.com' \
--to=sjg@chromium.org \
--cc=hl@rock-chips.com \
--cc=jeffy.chen@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=philipp.tomsich@theobroma-systems.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.