diff options
author | Sean Anderson <seanga2@gmail.com> | 2020-09-28 10:52:21 -0400 |
---|---|---|
committer | Andes <uboot@andestech.com> | 2020-09-30 08:54:45 +0800 |
commit | c33efafaf949ef11fc525cd5be018ea48c40898c (patch) | |
tree | 1e9860f9e33d19c16576d6db330da2b3cda7c64c /include/timer.h | |
parent | 9981a8009e17fd51b74a4a58ba436998ebbf81ed (diff) | |
download | u-boot-c33efafaf949ef11fc525cd5be018ea48c40898c.tar.gz u-boot-c33efafaf949ef11fc525cd5be018ea48c40898c.tar.bz2 u-boot-c33efafaf949ef11fc525cd5be018ea48c40898c.zip |
riscv: Rework riscv timer driver to only support S-mode
The riscv-timer driver currently serves as a shim for several riscv timer
drivers. This is not too desirable because it bypasses the usual timer
selection via the driver model. There is no easy way to specify an
alternate timing driver, or have the tick rate depend on the cpu's
configured frequency. The timer drivers also do not have device structs,
and so have to rely on storing parameters in gd_t. Lastly, there is no
initialization call, so driver init is done in the same function which
reads the time. This can result in confusing error messages. To a user, it
looks like the driver failed when trying to read the time, whereas it may
have failed while initializing.
This patch removes the shim functionality from the riscv-timer driver, and
has it instead implement the former rdtime.c timer driver. This is because
existing u-boot users who pass in a device tree (e.g. qemu) do not create a
timer device for S-mode u-boot. The existing behavior of creating the
riscv-timer device in the riscv cpu driver must be kept. The actual reading
of the CSRs has been redone in the style of Linux's get_cycles64.
Signed-off-by: Sean Anderson <seanga2@gmail.com>
Reviewed-by: Bin Meng <bin.meng@windriver.com>
Reviewed-by: Rick Chen <rick@andestech.com>
Diffstat (limited to 'include/timer.h')
0 files changed, 0 insertions, 0 deletions