Closed antmarzam closed 13 hours ago
List of commits since ES. The list has been compiled via:
git log Earlgrey-M2.5.2-RC0..HEAD hw/ip/spi_device/ hw/dv/sv/spi_agent/
All the commits covered in V1 sign-off have been taken out of the list.
Newer commits at the top:
sd_en_o
with read_pipeline signals in passthrough modeApart from the issues above, there are a couple of TB related Spi_device PRs open:
All RTL changes have been reflected in the spec
Functional coverage for new features has been implemented
Yes
Yes - except for the open ticket
Yes
Not true in an absolute manner but true for our metrics. Currently there are between 0/1 failures per overnight regression run which runs 1101 tests
Yes, current passing rate is very high as there's 0/1 failure per run
Yes, although there is an issue with the path in an RTL waiver file and the FSM numbers for passtrough are low, but that feature is unsupported and hence waivable.
Yes, current metric is 99.25% for FCOV
Yes, and already implemented
No P0/1 issues Low priority only issue
No change here
The checklist hasn't been scoped, but given the coverage numbers (shown below). I anticipate an effort of up to 2 weeks to close coverage and do the necessary cleanup
Note: FPV and SIM_FW_SIMULATED have been removed from above list since they don't apply to spi device.
I would say a pessimistic estimate would be 1-week + 1 week + 1 week + 5 days = 20 days
CC @a-will
@andreaskurth / @rswarbrick I believe this issue can now be closed since the last spi-device (DV) PR has been merged on master? If so #22473 could also be closed
I think I agree this is done (thanks!). To close the issue, could you push a PR that changes the status in spi_device.hjson
(line 40).
Description
Get spi_device ready for V2S signoff and sign it off