-
Notifications
You must be signed in to change notification settings - Fork 908
[csrng/rtl] Remove three prim_fifo_sync from the data path #28633
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
base: master
Are you sure you want to change the base?
Changes from all commits
b2b3304
c9a5677
612d248
205519d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -178,6 +178,9 @@ | |
| { name: "MAIN_SM.FSM.SPARSE" | ||
| desc: "The CSRNG main state machine uses a sparse state encoding." | ||
| } | ||
| { name: "UPDRSP.FSM.SPARSE" | ||
| desc: "The CSRNG update response state machine uses a sparse state encoding." | ||
| } | ||
| { name: "UPDATE.FSM.SPARSE" | ||
| desc: "The CSRNG update state machine uses a sparse state encoding." | ||
| } | ||
|
|
@@ -188,13 +191,13 @@ | |
| desc: "The CSRNG block output state machine uses a sparse state encoding." | ||
| } | ||
| { name: "GEN_CMD.CTR.REDUN" | ||
| desc: "The generate command uses a counter that is protected by a second counter that counts in the opposite direction." | ||
| desc: "The generate command uses a counter that is protected by a second counter that counts in the opposite direction." | ||
| } | ||
| { name: "DRBG_UPD.CTR.REDUN" | ||
| desc: "The ctr_drbg update algorithm uses a counter that is protected by a second counter that counts in the opposite direction." | ||
| desc: "The ctr_drbg update algorithm uses a counter that is protected by a second counter that counts in the opposite direction." | ||
| } | ||
| { name: "DRBG_GEN.CTR.REDUN" | ||
| desc: "The ctr_drbg generate algorithm uses a counter that is protected by a second counter that counts in the opposite direction." | ||
| desc: "The ctr_drbg generate algorithm uses a counter that is protected by a second counter that counts in the opposite direction." | ||
| } | ||
| { name: "CTRL.MUBI" | ||
| desc: "Multi-bit field used for selection control." | ||
|
|
@@ -728,33 +731,6 @@ | |
| This bit will stay set until the next reset. | ||
| ''' | ||
| } | ||
| { bits: "3", | ||
| name: "SFIFO_RCSTAGE_ERR", | ||
| desc: ''' | ||
| This bit will be set to one when an error has been detected for the | ||
| rcstage FIFO. The type of error is reflected in the type status | ||
| bits (bits 28 through 30 of this register). | ||
| This bit will stay set until the next reset. | ||
| ''' | ||
| } | ||
| { bits: "4", | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I realise that I'm repeating myself (sorry!), but I think it would make sense to split this commit into two pieces: the first one would remove the fifo and wire zero into the error field; the second would remove the field. |
||
| name: "SFIFO_KEYVRC_ERR", | ||
| desc: ''' | ||
| This bit will be set to one when an error has been detected for the | ||
| keyvrc FIFO. The type of error is reflected in the type status | ||
| bits (bits 28 through 30 of this register). | ||
| This bit will stay set until the next reset. | ||
| ''' | ||
| } | ||
| { bits: "7", | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If it's easy, I'd consider splitting this commit in two, where the first part removes the FIFO (and wires zero to this error signal) and the second part removes the register field. I think the result would probably be a lot easier to follow. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Unfortunately, splitting this up would be quite a bit of work, as this affects in total six commits in this and the follow-up PR (which would then become twelve or 13 commits, given your suggestion of splitting one of them into three). Apart from this, I would like to keep the regfile changes together with the rtl and dv changes in a single commit for each FIFO, respectively, for the following reasons:
Of course, please let me know if you feel strongly that the split up would be necessary. |
||
| name: "SFIFO_BENCACK_ERR", | ||
| desc: ''' | ||
| This bit will be set to one when an error has been detected for the | ||
| bencack FIFO. The type of error is reflected in the type status | ||
| bits (bits 28 through 30 of this register). | ||
| This bit will stay set until the next reset. | ||
| ''' | ||
| } | ||
| { bits: "9", | ||
| name: "SFIFO_FINAL_ERR", | ||
| desc: ''' | ||
|
|
@@ -882,6 +858,15 @@ | |
| This bit will stay set until the next reset. | ||
| ''' | ||
| } | ||
| { bits: "27", | ||
| name: "DRBG_CMD_SM_ERR", | ||
| desc: ''' | ||
| This bit will be set when the state machine in the ctr_drbg_cmd unit has entered | ||
| an illegal state. | ||
| This error will signal a fatal alert, and also an interrupt, if enabled. | ||
| This bit will stay set until the next reset. | ||
| ''' | ||
| } | ||
| { bits: "28", | ||
| name: "FIFO_WRITE_ERR", | ||
| desc: ''' | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A bit like with the previous commit, can this one be split as well? Here, it would be in three parts. I think the
SFIFO_RCSTATE_ERRfield could be removed as a later commit (and driven with zero beforehand). Similarly, I thinkDRBG_CMD_SM_ERRbe added as a first commit (driven with zero). That way, all the "register shuffling cruft" gets separated from the real work.