diff options
author | Philipp Tomsich <philipp.tomsich@theobroma-systems.com> | 2018-11-26 20:20:19 +0100 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2018-12-06 23:26:31 -0500 |
commit | 291da96b8e11d015d7725747bb8da677dcf01006 (patch) | |
tree | 709fde3ff77d91a7d02541e6f840922852dd849e /configs/ls1088ardb_qspi_SECURE_BOOT_defconfig | |
parent | 8b021bb956c3c890255d611f3780d3be7638a63a (diff) |
clk: Allow clock defaults to be set during re-reloc state for SPL only
In commit e5e06b65ad65 ("clk: Allow clock defaults to be set also
during re-reloc state") the earlier guard against setting clock
defaults in pre-reloc state was removed. While it is easy to filter
'assigned-clocks' properties for SPL using CONFIG_OF_SPL_REMOVE_PROPS,
no such mechanism exists for the pre-reloc stage of the full U-Boot.
With the default defconfig for the RK3399-Q7 (which filter the
'assigned-clocks' property for the DTS used by SPL anyway), this
caused a pause during startup of the full U-Boot stage that lasted for
almost 10s (due to the CPU not having been clocked up yet).
This reintroduces the guard from commit f4fcba5c5baa ("clk: Allow
clock defaults to be set also during re-reloc state") and extends it
to only apply outside of a TPL/SPL build: i.e. clk_set_defaults will
now run in pre-reloc state for SPL, but only after reloc for the full
U-Boot.
References: commit f4fcba5c5baa ("clk: implement clk_set_defaults()")
References: commit e5e06b65ad65 ("clk: Allow clock defaults to be set
also during re-reloc state")
Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
Diffstat (limited to 'configs/ls1088ardb_qspi_SECURE_BOOT_defconfig')
0 files changed, 0 insertions, 0 deletions