summaryrefslogtreecommitdiffstats
path: root/hw/arm/strongarm.c
diff options
context:
space:
mode:
authorLuc Michel2020-10-10 15:57:46 +0200
committerPeter Maydell2020-10-27 12:10:44 +0100
commita6414d3b59fe8666a7b093cdcf23c747ce3055b8 (patch)
tree3550ec9205c4b83683208f0c422990d790845be8 /hw/arm/strongarm.c
parenthw/core/clock: provide the VMSTATE_ARRAY_CLOCK macro (diff)
downloadqemu-a6414d3b59fe8666a7b093cdcf23c747ce3055b8.tar.gz
qemu-a6414d3b59fe8666a7b093cdcf23c747ce3055b8.tar.xz
qemu-a6414d3b59fe8666a7b093cdcf23c747ce3055b8.zip
hw/core/clock: trace clock values in Hz instead of ns
The nanosecond unit greatly limits the dynamic range we can display in clock value traces, for values in the order of 1GHz and more. The internal representation can go way beyond this value and it is quite common for today's clocks to be within those ranges. For example, a frequency between 500MHz+ and 1GHz will be displayed as 1ns. Beyond 1GHz, it will show up as 0ns. Replace nanosecond periods traces with frequencies in the Hz unit to have more dynamic range in the trace output. Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org> Reviewed-by: Damien Hedde <damien.hedde@greensocs.com> Signed-off-by: Luc Michel <luc@lmichel.fr> Tested-by: Guenter Roeck <linux@roeck-us.net> Tested-by: Philippe Mathieu-Daudé <f4bug@amsat.org> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Diffstat (limited to 'hw/arm/strongarm.c')
0 files changed, 0 insertions, 0 deletions