From: Paul Kocialkowski <paulk@sys-base.io>
To: u-boot@lists.denx.de
Cc: Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Kever Yang <kever.yang@rock-chips.com>,
Quentin Schulz <quentin.schulz@cherry.de>,
Jonas Karlman <jonas@kwiboo.se>,
Chris Morgan <macromorgan@hotmail.com>,
Tim Lunn <tim@feathertop.org>,
Paul Kocialkowski <contact@paulk.fr>
Subject: [PATCH 3/4] rockchip: rk3399-rockpro64: Disable bootstage instrumentation config
Date: Thu, 26 Sep 2024 20:31:10 +0200 [thread overview]
Message-ID: <20240926183111.1324284-3-paulk@sys-base.io> (raw)
In-Reply-To: <20240926183111.1324284-1-paulk@sys-base.io>
From: Paul Kocialkowski <contact@paulk.fr>
The boot timing and reporting (bootstage) infrastructure is useful for
performance analysis and debug but adds overhead and console noise when
using the device normally. Remove it from the device config.
Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
---
configs/rockpro64-rk3399_defconfig | 3 ---
1 file changed, 3 deletions(-)
diff --git a/configs/rockpro64-rk3399_defconfig b/configs/rockpro64-rk3399_defconfig
index fc0804a0b80d..095d27ffaa04 100644
--- a/configs/rockpro64-rk3399_defconfig
+++ b/configs/rockpro64-rk3399_defconfig
@@ -19,8 +19,6 @@ CONFIG_SPL_SPI=y
CONFIG_SYS_LOAD_ADDR=0x800800
CONFIG_PCI=y
CONFIG_DEBUG_UART=y
-CONFIG_BOOTSTAGE=y
-CONFIG_BOOTSTAGE_REPORT=y
CONFIG_DEFAULT_FDT_FILE="rockchip/rk3399-rockpro64.dtb"
CONFIG_DISPLAY_BOARDINFO_LATE=y
CONFIG_SPL_MAX_SIZE=0x40000
@@ -38,7 +36,6 @@ CONFIG_CMD_POWEROFF=y
CONFIG_CMD_USB=y
# CONFIG_CMD_SETEXPR is not set
CONFIG_CMD_TIME=y
-CONFIG_CMD_BOOTSTAGE=y
CONFIG_SPL_OF_CONTROL=y
CONFIG_OF_SPL_REMOVE_PROPS="clock-names interrupt-parent assigned-clocks assigned-clock-rates assigned-clock-parents"
CONFIG_ENV_IS_IN_SPI_FLASH=y
--
2.46.2
next prev parent reply other threads:[~2024-09-26 18:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 18:31 [PATCH 1/4] rockchip: rk3399-roc-pc: Hook sysreset gpio to enable full reset Paul Kocialkowski
2024-09-26 18:31 ` [PATCH 2/4] rockchip: rk3399-rockpro64: " Paul Kocialkowski
2024-09-27 9:28 ` Quentin Schulz
2024-11-05 15:38 ` Quentin Schulz
2024-11-05 18:46 ` Paul Kocialkowski
2024-09-26 18:31 ` Paul Kocialkowski [this message]
2024-09-30 9:01 ` [PATCH 3/4] rockchip: rk3399-rockpro64: Disable bootstage instrumentation config Peter Robinson
2024-09-30 18:52 ` Simon Glass
2024-09-30 19:07 ` Paul Kocialkowski
2024-10-01 11:19 ` Simon Glass
2024-09-26 18:31 ` [PATCH 4/4] rockchip: Disable DRAM debug by default Paul Kocialkowski
2024-09-26 20:17 ` Dragan Simic
2024-09-26 20:51 ` Paul Kocialkowski
2024-09-26 21:04 ` Dragan Simic
2024-09-26 21:16 ` Paul Kocialkowski
2024-09-26 21:24 ` Dragan Simic
2024-09-26 21:39 ` Paul Kocialkowski
2024-09-26 21:50 ` Dragan Simic
2024-09-27 9:25 ` [PATCH 1/4] rockchip: rk3399-roc-pc: Hook sysreset gpio to enable full reset Quentin Schulz
2024-09-27 9:53 ` Paul Kocialkowski
2024-09-27 10:07 ` Quentin Schulz
2024-09-27 12:25 ` Paul Kocialkowski
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=20240926183111.1324284-3-paulk@sys-base.io \
--to=paulk@sys-base.io \
--cc=contact@paulk.fr \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--cc=macromorgan@hotmail.com \
--cc=philipp.tomsich@vrull.eu \
--cc=quentin.schulz@cherry.de \
--cc=sjg@chromium.org \
--cc=tim@feathertop.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