diff options
| author | Peter Maydell | 2020-08-25 18:08:47 +0200 |
|---|---|---|
| committer | Peter Maydell | 2020-09-14 15:23:19 +0200 |
| commit | c9ebc8c207e997c01d459529fd83ffd85c66cf9d (patch) | |
| tree | 915f5e0d982c21f8f9e5e1706c9a0ce9834344ac /hw/timer/digic-timer.c | |
| parent | hw/misc/a9scu: Report unimplemented accesses with qemu_log_mask(UNIMP) (diff) | |
| download | qemu-c9ebc8c207e997c01d459529fd83ffd85c66cf9d.tar.gz qemu-c9ebc8c207e997c01d459529fd83ffd85c66cf9d.tar.xz qemu-c9ebc8c207e997c01d459529fd83ffd85c66cf9d.zip | |
hw/timer/armv7m_systick: assert that board code set system_clock_scale
It is the responsibility of board code for an armv7m system to set
system_clock_scale appropriately for the CPU speed of the core.
If it forgets to do this, then QEMU will hang if the guest tries
to use the systick timer in the "tick at the CPU clock frequency" mode.
We forgot that in a couple of our boards (see commits ce4f70e81ed23c93f,
e7e5a9595ab1136). Add an assertion in the systick reset method so
we don't let any new boards in with the same bug.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-id: 20200825160847.18091-1-peter.maydell@linaro.org
Diffstat (limited to 'hw/timer/digic-timer.c')
0 files changed, 0 insertions, 0 deletions