summaryrefslogtreecommitdiff
path: root/drivers/timer/nomadik-mtu-timer.c
diff options
context:
space:
mode:
authorBin Meng <bmeng.cn@gmail.com>2021-05-11 20:04:12 +0800
committerLeo Yu-Chi Liang <ycliang@andestech.com>2021-05-17 16:42:24 +0800
commita6d7e8c9149f5f1b94f68129fbe5dec9e1e1489d (patch)
tree282c6060fdc4bb24f483900897d51116fa5b0e0e /drivers/timer/nomadik-mtu-timer.c
parent2b039940f308cb6a3e6d45d0e8136f7bd35a0356 (diff)
downloadu-boot-a6d7e8c9149f5f1b94f68129fbe5dec9e1e1489d.tar.gz
riscv: Split SiFive CLINT support between SPL and U-Boot proper
At present there is only one Kconfig option CONFIG_SIFIVE_CLINT to control the enabling of SiFive CLINT support in both SPL (M-mode) and U-Boot proper (S-mode). So for a typical SPL config that the SiFive CLINT driver is enabled in both SPL and U-Boot proper, that means the S-mode U-Boot tries to access the memory-mapped CLINT registers directly, instead of the normal 'rdtime' instruction. This was not a problem before, as the hardware does not forbid the access from S-mode. However this becomes an issue now with OpenSBI commit 8b569803475e ("lib: utils/sys: Add CLINT memregion in the root domain") that the SiFive CLINT register space is protected by PMP for M-mode access only. U-Boot proper does not boot any more with the latest OpenSBI, that access exceptions are fired forever from U-Boot when trying to read the timer value via the SiFive CLINT driver in U-Boot. To solve this, we need to split current SiFive CLINT support between SPL and U-Boot proper, using 2 separate Kconfig options. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Sean Anderson <seanga2@gmail.com>
Diffstat (limited to 'drivers/timer/nomadik-mtu-timer.c')
0 files changed, 0 insertions, 0 deletions