Closed rnongie closed 2 months ago
sensor_ctrl got previously signed off at D3 in 9f31bc3b2ea59614655532e00294248f7bbbb04a and that wasn't changed when the version was increased to 2.0.0 in d352f0cf45299ed1a9715ca72fce052be21cb00b. So formally, sensor_ctrl is currently still signed off at D3. For completeness' sake, however, here are the changes since the previous D3 signoff (git log --pretty=oneline 9f31bc3b2ea59614655532e00294248f7bbbb04a..bff93a06f5e569270c56ec08db723722de9da805 hw/top_earlgrey/ip/sensor_ctrl/rtl | tac
, thus old to new):
ALERT_EN
CSRs to MuBiTrue
--> changes all alerts to be enabled at reset; part of #23149; LGTMThus the functional changes since the previous D3 signoff LGTM.
TODO
s in sensor_ctrl's RTL code.Thanks a lot @andreaskurth for taking care of this! This looks good.
The https://github.com/lowRISC/opentitan/commit/e063764dd06f0c61dad3f992cee794d13679c716 [tlul] Add access latency and ifetch to adapter_reg
change has already been taped out as part of ES. The other changes look all good to me (quickly reviewed the critical RTL parts and the list of reviewers for the PRs).
Whether the SW changes have been implemented in the DIF isn't a criteria for the D3 signoff so this should be fine - but as you say, the changes should be simple. Also thanks for reaching out to the SW team. Let's wait until THU for comments.
As for the lint waiver: there have not been any changes to the lint waiver since May 2020. I believe there is nothing to be reviewed by the TC. :-)
Description
No response