diff options
author | Peter Maydell | 2020-07-27 21:34:58 +0200 |
---|---|---|
committer | Peter Maydell | 2020-08-03 18:55:31 +0200 |
commit | ce4f70e81ed23c93ff39234672aff33114532640 (patch) | |
tree | c746d4681500e8d7f472c4823cee9c8242013c70 /hw/timer | |
parent | target/arm: Avoid maybe-uninitialized warning with gcc 4.9 (diff) | |
download | qemu-ce4f70e81ed23c93ff39234672aff33114532640.tar.gz qemu-ce4f70e81ed23c93ff39234672aff33114532640.tar.xz qemu-ce4f70e81ed23c93ff39234672aff33114532640.zip |
hw/arm/nrf51_soc: Set system_clock_scale
The nrf51 SoC model wasn't setting the system_clock_scale
global.which meant that if guest code used the systick timer in "use
the processor clock" mode it would hang because time never advances.
Set the global to match the documented CPU clock speed for this SoC.
This SoC in fact doesn't have a SysTick timer (which is the only thing
currently that cares about the system_clock_scale), because it's
a configurable option in the Cortex-M0. However our Cortex-M0 and
thus our nrf51 and our micro:bit board do provide a SysTick, so
we ought to provide a functional one rather than a broken one.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-id: 20200727193458.31250-1-peter.maydell@linaro.org
Diffstat (limited to 'hw/timer')
0 files changed, 0 insertions, 0 deletions