lowRISC
[spi_device] Add an event for unexpected host behavior
Host jumps the read address
The SPI_DEVICE assumes the host reads the address relatively sequentially. If not, (read next 1kB then roll back to previous 1kB), it is worth to notify SW to handle the scenario.
(Removing the hotlist label on the basis that this is a P2. Feel free to re-add if you would like this to be discussed in the next SW WG.)
is this one still valid given the recent mailbox change?
Yes. Still need to detect the host's incorrect behaviors.
Triaged for spi_device. Assigning to M2.5 with https://github.com/lowRISC/opentitan/labels/Priority%3AP2 because we should check with the product team if we need to handle such unexpected host behavior. If not, we can defer this to https://github.com/lowRISC/opentitan/labels/Type%3AFutureRelease.
Adding the FutureRelease label as we consider this an useful feature to have in a production instantiation of OpenTitan.
@moidx Do we even have a usecase that would not do continuous reads? Because if not I would advocate no change at this point.
I am ok if we close this issue as not planned. Given the schedule constraints of this iteration, it is perfectly fine to document this limitation in the specification. The use case is restricted to linear access.