Invalidate the LQSPI cached page when transitioning into LQSPI mode. Otherwise there is a possibility that the controller will return stale data to the guest when transitioning back to LQ_MODE after a page program.
Signed-off-by: Peter Crosthwaite <peter.crosthwa...@xilinx.com> --- hw/xilinx_spips.c | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-) diff --git a/hw/xilinx_spips.c b/hw/xilinx_spips.c index 78a3fec..4f921f8 100644 --- a/hw/xilinx_spips.c +++ b/hw/xilinx_spips.c @@ -390,6 +390,9 @@ static void xilinx_spips_write(void *opaque, hwaddr addr, int mask = ~0; int man_start_com = 0; XilinxSPIPS *s = opaque; + /* FIXME: abstract away somehow */ + XilinxQSPIPS *q = (XilinxQSPIPS *)object_dynamic_cast(OBJECT(s), + TYPE_XILINX_QSPIPS); DB_PRINT("addr=" TARGET_FMT_plx " = %x\n", addr, (unsigned)value); addr >>= 2; @@ -435,6 +438,11 @@ static void xilinx_spips_write(void *opaque, hwaddr addr, case R_TXD3: tx_data_bytes(s, (uint32_t)value, 3); goto no_reg_update; + case R_LQSPI_CFG: + if (q) { + q->lqspi_cached_addr = ~0ULL; + } + break; } s->regs[addr] = (s->regs[addr] & ~mask) | (value & mask); no_reg_update: -- 1.7.0.4