armsse: Wire up systick cpuclk clock
Wire up the cpuclk for the systick devices to the SSE object's existing mainclk clock. We do not wire up the refclk because the SSE subsystems do not provide a refclk. (This is documented in the IoTKit and SSE-200 TRMs; the SSE-300 TRM doesn't mention it but we assume it follows the same approach.) When we update the systick device later to honour "no refclk connected" this will fix a minor emulation inaccuracy for the SSE-based boards. Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Acked-by: Alistair Francis <alistair.francis@wdc.com> Reviewed-by: Luc Michel <luc@lmichel.fr> Message-id: 20210812093356.1946-8-peter.maydell@linaro.org
This commit is contained in:
parent
d5093d9615
commit
712bd17f3e
@ -995,6 +995,9 @@ static void armsse_realize(DeviceState *dev, Error **errp)
|
|||||||
int j;
|
int j;
|
||||||
char *gpioname;
|
char *gpioname;
|
||||||
|
|
||||||
|
qdev_connect_clock_in(cpudev, "cpuclk", s->mainclk);
|
||||||
|
/* The SSE subsystems do not wire up a systick refclk */
|
||||||
|
|
||||||
qdev_prop_set_uint32(cpudev, "num-irq", s->exp_numirq + NUM_SSE_IRQS);
|
qdev_prop_set_uint32(cpudev, "num-irq", s->exp_numirq + NUM_SSE_IRQS);
|
||||||
/*
|
/*
|
||||||
* In real hardware the initial Secure VTOR is set from the INITSVTOR*
|
* In real hardware the initial Secure VTOR is set from the INITSVTOR*
|
||||||
|
Loading…
Reference in New Issue
Block a user