u-boot.git/cmd/bdinfo.c, branch v2020.10

cmd: bdinfo: Move sram info prints to generic code

2020-08-06T18:26:35+00:00

bi_sramstart and bi_sramsize are generic members of the bd_info structure,
so move the m68k/powerpc-specific prints to generic code. Also, print them
only if SRAM support is enabled via CONFIG_SYS_HAS_SRAM.

Reviewed-by: Simon Glass 
Signed-off-by: Ovidiu Panait

cmd: bdinfo: cleanup phys_addr_t output

2020-08-05T12:18:34+00:00

We currently print the memory size with at least 8 hexadecimal digits.
This creates a ragged output on 64 bit boards, e.g. on a Kendryte K210:

DRAM bank   = 0x0000000000000002
-> start    = 0x0000000080600000
-> size     = 0x0000000000200000
memstart    = 0x0000000000000000
memsize     = 0x00000000
flashstart  = 0x0000000000000000
flashsize   = 0x0000000000000000
flashoffset = 0x0000000000000000

All other numbers are printed with the number of digits needed for the type
ulong. So use this value as minimum number of digits (precision) for
printing physical addresses.

Signed-off-by: Heinrich Schuchardt 
Reviewed-by: Heiko Schocher 
Reviewed-by: Stefan Roese 
Reviewed-by: Simon Glass

lmb/bdinfo: dump lmb info via bdinfo

2020-08-05T03:30:02+00:00

Dump lmb status from the bdinfo command. This is useful for seeing the
reserved memory regions from the u-boot cmdline.

Signed-off-by: Tero Kristo

treewide: convert bd_t to struct bd_info by coccinelle

2020-07-17T13:30:13+00:00

The Linux coding style guide (Documentation/process/coding-style.rst)
clearly says:

  It's a **mistake** to use typedef for structures and pointers.

Besides, using typedef for structures is annoying when you try to make
headers self-contained.

Let's say you have the following function declaration in a header:

  void foo(bd_t *bd);

This is not self-contained since bd_t is not defined.

To tell the compiler what 'bd_t' is, you need to include 

  #include 
  void foo(bd_t *bd);

Then, the include direcective pulls in more bloat needlessly.

If you use 'struct bd_info' instead, it is enough to put a forward
declaration as follows:

  struct bd_info;
  void foo(struct bd_info *bd);

Right, typedef'ing bd_t is a mistake.

I used coccinelle to generate this commit.

The semantic patch that makes this change is as follows:

  
  @@
  typedef bd_t;
  @@
  -bd_t
  +struct bd_info
  

Signed-off-by: Masahiro Yamada

bdinfo: Update the file comments

2020-06-25T17:24:13+00:00

Update the comment at the top of the file to indicate what this file does.
Also drop the line at the bottom and an unnecessary header include.

Signed-off-by: Simon Glass 
Reviewed-by: Bin Meng

bdinfo: m68k: ppc: Move arch-specific code from bdinfo

2020-06-25T17:24:13+00:00

We don't have an easy way to share these three lines of code with two
architectures. We also want to make it clear that this code is actually
arch-specific.

So just duplicate it in each arch-specific file.

Signed-off-by: Simon Glass 
Reviewed-by: Bin Meng 
Reviewed-by: Stefan Roese

bdinfo: m68k: Move m68k-specific info into its own file

2020-06-25T17:24:12+00:00

We don't really want to have m68k-specific code in a generic file. Create
a new arch-specific function to hold it, and move it into that.

Make the function weak so that any arch can implement it.

Signed-off-by: Simon Glass 
Reviewed-by: Bin Meng 
Tested-by: Angelo Dureghello 
Tested-by: Angelo Dureghello

bdinfo: ppc: Move PPC-specific info into its own file

2020-06-25T17:24:12+00:00

We don't really want to have PPC-specific code in a generic file. Create
a new arch-specific function to hold it, and move it into that.

Make the function weak so that any arch can implement it.

Signed-off-by: Simon Glass 
Reviewed-by: Bin Meng 
Reviewed-by: Stefan Roese

bdinfo: arm: Move ARM-specific info into its own file

2020-06-25T17:24:12+00:00

We don't really want to have ARM-specific code in a generic file. Create
a new arch-specific function to hold it, and move it into that.

Make the function weak so that any arch can implement it.

Signed-off-by: Simon Glass 
Reviewed-by: Bin Meng

bdinfo: Export some basic printing functions

2020-06-25T17:24:12+00:00

At present the functions to print a number and a frequency are static. We
want to move some of the code in here to an arch-specific file. For
consistency that code should use these same functions. So export them with
an appropriate name.

Signed-off-by: Simon Glass 
Reviewed-by: Bin Meng