Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[spi_device,rtl] Consider adding signalling mechanism to abort #18357

Closed
hcallahan-lowrisc opened this issue May 5, 2023 · 4 comments
Closed
Labels
Component:RTL Earlgrey-PROD Candidate Temporary label to triage issues into Earlgrey-PROD Milestones IP:spi_device Priority:P2 Priority: medium Type:Icebox Changes deferred to future milestones

Comments

@hcallahan-lowrisc
Copy link
Contributor

Description

//logic abort_done; // TODO: Not implemented yet

@hcallahan-lowrisc hcallahan-lowrisc added Component:RTL IP:spi_device Type:Icebox Changes deferred to future milestones labels May 5, 2023
@hcallahan-lowrisc hcallahan-lowrisc changed the title [spi_device] Consider adding signalling mechanism to abort [spi_device,rtl] Consider adding signalling mechanism to abort May 5, 2023
@msfschaffner msfschaffner added the Earlgrey-PROD Candidate Temporary label to triage issues into Earlgrey-PROD Milestones label Oct 7, 2023
@msfschaffner msfschaffner added this to the Earlgrey-PROD.M2 milestone Nov 7, 2023
@msfschaffner msfschaffner added the Priority:P3 Priority: low label Dec 4, 2023
@msfschaffner
Copy link
Contributor

@a-will is this related to #20654?

@msfschaffner msfschaffner added Priority:P2 Priority: medium and removed Priority:P3 Priority: low labels Dec 19, 2023
@a-will
Copy link
Contributor

a-will commented Dec 19, 2023

@a-will is this related to #20654?

No, this issue appears to be about some kind of OT-triggered abort (which doesn't make sense to me). Notice that it's assigned by CSRs:

assign abort = reg2hw.control.abort.q;

The other issue is about being able to handle the host abandoning SPI TPM transactions before they have completed. The buffering architecture has a poor design for handling such sequences, since it adds ambiguity.

@msfschaffner
Copy link
Contributor

Ah I see. It looks like this is allocated for generic mode, which we plan to deprecate:

{ bits: "0",
name: "ABORT",
desc: '''Abort pending TX data in Generic mode.
If TX_FIFO (Asynchronous) is full, the TXF waits indefinitely to
push the next byte into the asynchronous FIFO. SW may reset the
Async FIFO along with aborting the current task. SW should update
the write pointer of the TXF in order not to push the byte to
Asynchronous FIFO again by TXF logic.
'''
resval: "0"
},

Hence this can be resolved by removing it entirely.

@a-will
Copy link
Contributor

a-will commented Jan 8, 2024

Closing, since we plan to remove firmware mode.

@a-will a-will closed this as not planned Won't fix, can't repro, duplicate, stale Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component:RTL Earlgrey-PROD Candidate Temporary label to triage issues into Earlgrey-PROD Milestones IP:spi_device Priority:P2 Priority: medium Type:Icebox Changes deferred to future milestones
Projects
None yet
Development

No branches or pull requests

3 participants