From: Bin Meng <bmeng.cn@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH 7/7] bdinfo: Change to use bdinfo_print_num_ll() where the number could be 64-bit
Date: Thu, 21 Jan 2021 23:00:15 +0800 [thread overview]
Message-ID: <20210121150015.25558-8-bmeng.cn@gmail.com> (raw)
In-Reply-To: <20210121150015.25558-1-bmeng.cn@gmail.com>
From: Bin Meng <bin.meng@windriver.com>
There are some calls to bdinfo_print_num_l() with parameters that
could be a 64-bit value on a 32-bit system. Change those calls to
use bdinfo_print_num_ll() instead.
Signed-off-by: Bin Meng <bin.meng@windriver.com>
---
arch/arm/lib/bdinfo.c | 8 ++++----
cmd/bdinfo.c | 4 ++--
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/arch/arm/lib/bdinfo.c b/arch/arm/lib/bdinfo.c
index 4a98cb7ef5..c905783bdc 100644
--- a/arch/arm/lib/bdinfo.c
+++ b/arch/arm/lib/bdinfo.c
@@ -18,14 +18,14 @@ void arch_print_bdinfo(void)
bdinfo_print_num_l("arch_number", bd->bi_arch_number);
#ifdef CONFIG_SYS_MEM_RESERVE_SECURE
if (gd->arch.secure_ram & MEM_RESERVE_SECURE_SECURED) {
- bdinfo_print_num_l("Secure ram",
- gd->arch.secure_ram &
- MEM_RESERVE_SECURE_ADDR_MASK);
+ bdinfo_print_num_ll("Secure ram",
+ gd->arch.secure_ram &
+ MEM_RESERVE_SECURE_ADDR_MASK);
}
#endif
#ifdef CONFIG_RESV_RAM
if (gd->arch.resv_ram)
- bdinfo_print_num_l("Reserved ram", gd->arch.resv_ram);
+ bdinfo_print_num_ll("Reserved ram", gd->arch.resv_ram);
#endif
#if !(CONFIG_IS_ENABLED(SYS_ICACHE_OFF) && CONFIG_IS_ENABLED(SYS_DCACHE_OFF))
bdinfo_print_num_l("TLB addr", gd->arch.tlb_addr);
diff --git a/cmd/bdinfo.c b/cmd/bdinfo.c
index 996546faf3..dfd50ae849 100644
--- a/cmd/bdinfo.c
+++ b/cmd/bdinfo.c
@@ -55,8 +55,8 @@ static void print_bi_dram(const struct bd_info *bd)
for (i = 0; i < CONFIG_NR_DRAM_BANKS; ++i) {
if (bd->bi_dram[i].size) {
bdinfo_print_num_l("DRAM bank", i);
- bdinfo_print_num_l("-> start", bd->bi_dram[i].start);
- bdinfo_print_num_l("-> size", bd->bi_dram[i].size);
+ bdinfo_print_num_ll("-> start", bd->bi_dram[i].start);
+ bdinfo_print_num_ll("-> size", bd->bi_dram[i].size);
}
}
}
--
2.25.1
prev parent reply other threads:[~2021-01-21 15:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 15:00 [PATCH 0/7] Allow booting a 32-bit system with a top memory address beyond 4 GiB Bin Meng
2021-01-21 15:00 ` [PATCH 1/7] riscv: Adjust board_get_usable_ram_top() for 32-bit Bin Meng
2021-01-21 15:00 ` [PATCH 2/7] global_data.h: Change ram_top type to phys_addr_t Bin Meng
2021-01-24 2:03 ` Simon Glass
2021-01-29 17:47 ` Simon Glass
2021-01-30 10:13 ` Bin Meng
2021-01-30 16:24 ` Simon Glass
2021-01-31 3:40 ` Bin Meng
2021-01-31 3:44 ` Simon Glass
2021-01-31 8:35 ` Bin Meng
2021-01-21 15:00 ` [PATCH 3/7] serial: sifive: Cast dev_read_addr() with uintptr_t Bin Meng
2021-01-21 15:00 ` [PATCH 4/7] fdtdec: Cast prior_stage_fdt_address " Bin Meng
2021-01-24 2:03 ` Simon Glass
2021-01-21 15:00 ` [PATCH 5/7] riscv: Change phys_addr_t and phys_size_t to 64-bit Bin Meng
2021-01-21 15:00 ` [PATCH 6/7] bdinfo: Rename function names to be clearer Bin Meng
2021-01-21 15:00 ` Bin Meng [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=20210121150015.25558-8-bmeng.cn@gmail.com \
--to=bmeng.cn@gmail.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.