Andreas Kurth

Triaged for `spi_device`. Assigning to M2.5 with https://github.com/lowRISC/opentitan/labels/Priority%3AP2 because even though this is about robustness in an environment with errors, we should check with the product team if the behavior...

> From the V2 review https://github.com/lowRISC/opentitan/issues/15539, it sounds like https://github.com/lowRISC/opentitan/pull/15637 was merged to check the block does not lock up if CSB de-asserts in bits 0-7. Caution: Since PR #15770,...

I agree that this isn't needed for the current release. For a future release, however, we may want to consider an enhancement where SW can configure `tlul_adapter_host` to 'wipe' the...

Triaged for `spi_device`. Assigning to M2.5 with https://github.com/lowRISC/opentitan/labels/Priority%3AP2 because even though this is about robustness in an environment with errors, we should check with the product team if the behavior...

@vogelpi: For a V1 signoff I think we don't need the DV stats. The smoke test still passes according to [current nightly results](https://reports.opentitan.org/hw/ip/edn/dv/latest/report.html), and if the changes made to EDN...

@andreaskurth: Planning to look into this early next week.

Triaged for `tlul`. Are we sure we don't want to check the integrity of data read in `tlul_sram_byte` by adding a `tlul_data_integ_dec` and feeding its `data_err_o` into `error_o`? (This to...

Triaged for `spi_device`. I think this is not necessary for this release and thus correctly labeled https://github.com/lowRISC/opentitan/labels/Type%3AFutureRelease.

@gdessouky As discussed, here's a first implementation of save & restore. I would be super happy to get your feedback on this. Unless you think this is fundamentally broken, I...

kokoro reported lint errors that I've fixed by now; the remaining _flow errors_ seem to be spurious.