Home
last modified time | relevance | path

Searched refs:bootstage (Results 1 – 17 of 17) sorted by relevance

/u-boot/common/
A Dbootstage.c61 struct bootstage_data *data = gd->bootstage; in bootstage_relocate()
117 struct bootstage_data *data = gd->bootstage; in bootstage_add_record()
195 struct bootstage_data *data = gd->bootstage; in bootstage_start()
209 struct bootstage_data *data = gd->bootstage; in bootstage_accum()
274 struct bootstage_data *data = gd->bootstage; in add_bootstages_devicetree()
275 int bootstage; in add_bootstages_devicetree() local
288 if (bootstage < 0) in add_bootstages_devicetree()
332 struct bootstage_data *data = gd->bootstage; in bootstage_report()
435 struct bootstage_data *data = gd->bootstage; in bootstage_unstash()
526 if (!gd->bootstage) in bootstage_init()
[all …]
A Dboard_f.c657 gd->bootstage, gd->new_bootstage, size); in reloc_bootstage()
658 memcpy(gd->new_bootstage, gd->bootstage, size); in reloc_bootstage()
659 gd->bootstage = gd->new_bootstage; in reloc_bootstage()
A DMakefile46 obj-$(CONFIG_$(SPL_TPL_)BOOTSTAGE) += bootstage.o
/u-boot/cmd/
A Dbootstage.c90 U_BOOT_CMD(bootstage, 4, 1, do_boostage,
A DMakefile38 obj-$(CONFIG_CMD_BOOTSTAGE) += bootstage.o
A DKconfig2142 milliseconds. See also the 'bootstage' command which provides more
2327 bool "Enable the 'bootstage' command"
2330 Add a 'bootstage' command which supports printing a report
2331 and un/stashing of bootstage data.
/u-boot/include/asm-generic/
A Dglobal_data.h376 struct bootstage_data *bootstage; member
/u-boot/boot/
A DKconfig895 Normally, IDs are defined in bootstage.h but a small number of
944 This is the size of the bootstage record list and is the maximum
945 number of bootstage records that can be recorded.
952 This is the size of the bootstage record list and is the maximum
953 number of bootstage records that can be recorded.
961 number of bootstage records that can be recorded.
967 Stash the bootstage information in the FDT. A root 'bootstage'
968 node is created with each bootstage id as a child. Each child
971 accumulated time for that bootstage id in microseconds.
974 bootstage {
[all …]
/u-boot/doc/develop/driver-model/
A Dmigration.rst110 There is only one method to implement, unless you want to support bootstage,
/u-boot/doc/develop/
A Dtrace.rst199 use bootstage.
281 doing end-to-end timing using bootstage.
A Dcodingstyle.rst118 #include <bootstage.h>
/u-boot/drivers/timer/
A DKconfig284 bootstage we want to record the time since reset as accurately as
/u-boot/doc/board/google/
A Dchromebook_coral.rst308 boot. Use 'bootstage report' in U-Boot to see the report, e.g.::
/u-boot/doc/arch/
A Dx86.rst273 U-Boot prints out some bootstage timing. This is more useful if you put the
/u-boot/tools/buildman/
A DREADME.rst715 04: x86: Permit bootstage and timer data to be used prior to relocation
A Dbuildman.rst715 04: x86: Permit bootstage and timer data to be used prior to relocation
/u-boot/doc/build/
A Dbuildman.rst715 04: x86: Permit bootstage and timer data to be used prior to relocation

Completed in 27 milliseconds