There are drivers writing to WUFC uncondtionally of anything. In order to
not panic gem5 in these cases, ignore writes to WUFC and WUS as we do for
WUC. Similarly return 0 (default reset value) on reads.
Testing Done: Booted in FS with such a driver revision which would
previously panic and now boots fine.
Reviewed at http://reviews.gem5.org/r/3791/
Signed-off-by: Jason Lowe-Power <jason@lowepower.com>
pkt->set<uint32_t>(regs.pba());
break;
case REG_WUC:
+ case REG_WUFC:
+ case REG_WUS:
case REG_LEDCTL:
pkt->set<uint32_t>(0); // We don't care, so just return 0
break;
regs.pba.txa(64 - regs.pba.rxa());
break;
case REG_WUC:
+ case REG_WUFC:
+ case REG_WUS:
case REG_LEDCTL:
case REG_FCAL:
case REG_FCAH:
const uint32_t REG_VFTA = 0x05600;
const uint32_t REG_WUC = 0x05800;
+const uint32_t REG_WUFC = 0x05808;
+const uint32_t REG_WUS = 0x05810;
const uint32_t REG_MANC = 0x05820;
const uint32_t REG_SWSM = 0x05B50;
const uint32_t REG_FWSM = 0x05B54;