From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 7/8] rockchip: rk3399: tpl: Mark printascii into debug
Date: Wed, 8 May 2019 13:39:03 +0530 [thread overview]
Message-ID: <20190508080904.1567-8-jagan@amarulasolutions.com> (raw)
In-Reply-To: <20190508080904.1567-1-jagan@amarulasolutions.com>
Now, we have spl_board_init which has TPL banner prints.
So mark the 'U-Boot TPL board init' print into debug.
Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
---
arch/arm/mach-rockchip/rk3399-board-tpl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-rockchip/rk3399-board-tpl.c b/arch/arm/mach-rockchip/rk3399-board-tpl.c
index 72d0dd914e..4a301249b4 100644
--- a/arch/arm/mach-rockchip/rk3399-board-tpl.c
+++ b/arch/arm/mach-rockchip/rk3399-board-tpl.c
@@ -47,7 +47,7 @@ void board_init_f(ulong dummy)
* printhex8(0x1234);
* printascii("string");
*/
- printascii("U-Boot TPL board init\n");
+ debug("U-Boot TPL board init\n");
#endif
ret = spl_early_init();
if (ret) {
--
2.18.0.321.gffc6fa0e3
next prev parent reply other threads:[~2019-05-08 8:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 8:08 [U-Boot] [PATCH 0/8] rockchip: rk3399: Use spl_board_init in SPL, TPL Jagan Teki
2019-05-08 8:08 ` [U-Boot] [PATCH 1/8] board: rk3399: Drop explicit uart enablement in spl_board_init Jagan Teki
2019-05-08 8:08 ` [U-Boot] [PATCH 2/8] rockchip: rk3399: Support common spl_board_init Jagan Teki
2019-05-08 8:08 ` [U-Boot] [PATCH 3/8] rockchip: rk3399: spl: Mark printascii into debug Jagan Teki
2019-05-08 8:09 ` [U-Boot] [PATCH 4/8] rockchip: rk3399: Move u-boot, dm-pre-reloc of uart0, uart2 Jagan Teki
2019-05-08 8:09 ` [U-Boot] [PATCH 5/8] rockchip: rk3399: Enable SPL_BOARD_INIT Jagan Teki
2019-05-08 8:09 ` [U-Boot] [PATCH 6/8] rockchip: rk3399: tpl: Add spl_board_init Jagan Teki
2019-05-08 8:09 ` Jagan Teki [this message]
2019-05-08 8:09 ` [U-Boot] [PATCH 8/8] rockchip: rk3399: Enable TPL_BOARD_INIT Jagan Teki
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=20190508080904.1567-8-jagan@amarulasolutions.com \
--to=jagan@amarulasolutions.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