28 May, 2015
1 commit
-
Added a trimmed down instance of boot_get_() to satisfy the
minimum requierments of the added feature. The function follows the
normal patterns set by other boot_get's, which should make it a
bit easier to combine them all together into one boot_get_image()
function in a later refactor.Documentation for the new function can be found in source:
include/image.hSigned-off-by: Karl Apsite
Reviewed-by: Simon Glass
15 May, 2015
1 commit
-
We maintain an accumulator for time spent reading from SPI flash, since
this can be significant on some platforms. Also add one for decompression
time.Signed-off-by: Simon Glass
Reviewed-by: Joe Hershberger
Reviewed-by: Jagan Teki
19 Apr, 2015
1 commit
-
Move CONFIG_BOOT_STAGE and its associated options to Kconfig. Adjust
existing users and code.Signed-off-by: Simon Glass
07 Feb, 2015
2 commits
-
There are two typos in the comment block in bootstage.h, fix them.
Signed-off-by: Bin Meng
Acked-by: Simon Glass -
On some hardware this time can be significant. Add bootstage support for
measuring this. The result can be obtained using 'bootstage report' or
passed on to the Linux via the device tree.Signed-off-by: Simon Glass
Reviewed-by: Bin Meng
22 Oct, 2014
1 commit
-
Add a new setup@ section to the FIT which can be used to provide a setup
binary for booting Linux on x86. This makes it possible to boot x86 from
a FIT.Signed-off-by: Simon Glass
16 Aug, 2013
1 commit
-
In case CONFIG_BOOTSTAGE is not defined, call from bootstage_mark_name()
show_boot_progress(), so get more BOOTSTAGE_ID* ids in show_boot_progress()
if CONFIG_BOOTSTAGE is not defined.Signed-off-by: Heiko Schocher
Cc: Simon Glass
Cc: Tom Rini
Cc: Albert Aribaud
Acked-by: Simon Glass
24 Jul, 2013
1 commit
-
Signed-off-by: Wolfgang Denk
[trini: Fixup common/cmd_io.c]
Signed-off-by: Tom Rini
05 Jun, 2013
2 commits
-
Now that the code for loading these three images from a FIT is common, we
don't need individual boostage IDs for each of them.Note: there are some minor changes in the bootstage numbering, particuarly
for kernel loading. I don't believe this matters.Signed-off-by: Simon Glass
-
Loading a ramdisk, kernel or FDT goes through similar stages. Create
a block of IDs for each task, and define a consistent numbering within
the block. This will allow use of common code for image loading.Signed-off-by: Simon Glass
15 May, 2013
1 commit
-
We don't measure boot timing on the host, or with SPL, so use both
conditions in the bootstage header. This allows us to avoid using
conditional compilation around bootstage_...() calls. (#ifdef)Signed-off-by: Simon Glass
14 May, 2013
3 commits
-
Add a function which allows a (file, function, line number) to be marked
in bootstage.Signed-off-by: Simon Glass
Reviewed-by: Che-Liang Chiou -
Any pointers to name strings that were passed to bootstage_mark_name()
pre-relocation should be copied post-relocation so that they don't get
trashed as the original location of U-Boot is re-used for other
purposes.This change introduces a new API call that should be called from
board_init_r() after malloc has been initted on any board that uses
bootstage.Signed-off-by: Doug Anderson
Signed-off-by: Simon Glass
Reviewed-by: Simon Glass -
Some functions don't have a stub for when CONFIG_BOOTSTAGE is not defined.
Add one to avoid #ifdefs in the code when this is used in U-Boot.Signed-off-by: Simon Glass
Reviewed-by: Che-Liang Chiou
Reviewed-by: Tom Wai-Hong Tam
16 Oct, 2012
1 commit
03 Oct, 2012
5 commits
-
Add bootstage IDs for board init and LCD.
Signed-off-by: Simon Glass
-
It is useful to be able to write the bootstage information to memory for
use by a later utility, or the Linux kernel. Provide a function to do
this as well as a function to read bootstage information back and incorporate
it into the current table.This also makes it possible for U-Boot to chain to another U-Boot and pass
on its bootstage information.Signed-off-by: Simon Glass
-
Add an option, CONFIG_BOOTSTAGE_FDT to pass boot timings to the kernel
in the device tree, if available. To use this, you must have
CONFIG_OF_LIBFDT defined.Signed-off-by: Simon Glass
-
Sometimes we want to add up the amount of time spent in a particular
activity when it is happening in a number of discrete chunks.Add bootstage_start() to mark the start of an acitivity and
bootstage_accum() to accumulate the time since the last start. Calling
these function in pairs results in the accumulated time being collected.Signed-off-by: Simon Glass
-
This function is not static, but not exported either. Add a prototype
in the header file and move the required enum to the header also.Signed-off-by: Simon Glass
02 Oct, 2012
1 commit
-
This patch adds support for networking in SPL. Some devices are
capable of loading SPL via network so it makes sense to load the
main U-Boot binary via network too. This patch tries to use
existing network code as much as possible. Unfortunately, it depends
on environment which in turn depends on other code so SPL size
is increased significantly. No effort was done to decouple network
code and environment so far.Signed-off-by: Ilya Yanok
Acked-by: Joe Hershberger
Signed-off-by: Tom Rini
11 Apr, 2012
1 commit
-
The standalone example does not have get_timer() defined, so we cannot
rely on it being available.Move the timer function into boootstage.c to avoid this problem.
This corrects a build breakage for the standalone example on some boards.
Signed-off-by: Simon Glass
Acked-by: Matthias Fuchs
19 Mar, 2012
11 commits
-
This defines the basics of a new boot time measurement feature. This allows
logging of very accurate time measurements as the boot proceeds, by using
an available microsecond counter.To enable the feature, define CONFIG_BOOTSTAGE in your board config file.
Also available is CONFIG_BOOTSTAGE_REPORT which will cause a report to be
printed just before handing off to the OS.Most IDs are not named at this stage. For that I would first like to
renumber them all.Timer summary in microseconds:
Mark Elapsed Stage
0 0 reset
205,000 205,000 board_init_f
6,053,000 5,848,000 bootm_start
6,053,000 0 id=1
6,058,000 5,000 id=101
6,058,000 0 id=100
6,061,000 3,000 id=103
6,064,000 3,000 id=104
6,093,000 29,000 id=107
6,093,000 0 id=106
6,093,000 0 id=105
6,093,000 0 id=108
7,089,000 996,000 id=7
7,089,000 0 id=15
7,089,000 0 id=8
7,097,000 8,000 start_kernelSigned-off-by: Simon Glass
-
These calls should not be made directly any more, since bootstage
will call the show_boot_...() functions as needed.Signed-off-by: Simon Glass
-
This changes over all the FIT image progress numbers to use enums
from bootstage.h.Signed-off-by: Simon Glass
-
This changes over the network-related progress numbers to use enums
from bootstage.h.Signed-off-by: Simon Glass
-
This changes over the NAND progress numbers to use enums from
bootstage.h.Signed-off-by: Simon Glass
-
This changes over the IDE progress numbers to use enums from bootstage.h.
Signed-off-by: Simon Glass
-
Signed-off-by: Simon Glass
-
Signed-off-by: Simon Glass
Acked-by: Mike Frysinger -
Signed-off-by: Simon Glass
-
Rather than the caller negating our progress numbers to indicate an
error has occurred, which seems hacky, add a function to indicate this.Signed-off-by: Simon Glass
Acked-by: Mike Frysinger -
At present boot_stage_progress() is called with various magic numbers. The
new bootstage.h header will be used to turn these into symbolic names
throughout the code.The intent is not that these numbers are passed to Linux. In fact by using
an enum to track them we should eventually be able to remove the explict
numbers and just have the stages count up from 0.Signed-off-by: Simon Glass