[PATCH v6 016/102] x86: timer: use a timer base of 0
Bin Meng
bmeng.cn at gmail.com
Sun Dec 8 03:41:53 CET 2019
On Sat, Dec 7, 2019 at 12:46 PM Simon Glass <sjg at chromium.org> wrote:
>
> On x86 platforms the timer is reset to 0 when the SoC is reset. Having
> this as the timer base is useful since it provides an indication of how
> long it takes before U-Boot is running.
>
> When U-Boot sets the timer base to something else, time is lost and we
> no-longer have an accurate account of the time since reset. This
> particularly affects bootstage.
>
> Change the default to not read the timer base, leaving it at 0. Add an
> option for when U-Boot is the secondary bootloader.
>
> Signed-off-by: Simon Glass <sjg at chromium.org>
> Reviewed-by: Bin Meng <bmeng.cn at gmail.com>
> ---
>
> Changes in v6: None
> Changes in v5: None
> Changes in v4:
> - Enable option for slimbootloader, coreboot, efi
> - Reverse the sense of the CONFIG option
>
> Changes in v3: None
> Changes in v2: None
>
> arch/x86/cpu/coreboot/Kconfig | 1 +
> arch/x86/cpu/slimbootloader/Kconfig | 1 +
> drivers/timer/Kconfig | 14 ++++++++++++++
> drivers/timer/tsc_timer.c | 3 ++-
> lib/efi/Kconfig | 1 +
> 5 files changed, 19 insertions(+), 1 deletion(-)
>
applied to u-boot-x86/next, thanks!
More information about the U-Boot
mailing list