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

Question about pipeline FF enable signals #110

Open
tunefish777 opened this issue Jun 13, 2022 · 0 comments
Open

Question about pipeline FF enable signals #110

tunefish777 opened this issue Jun 13, 2022 · 0 comments

Comments

@tunefish777
Copy link

Hi,

I'm currently trying to understand the pipeline but I'm puzzled by one small detail. The dec_iX_decode_d signal is used as the highest value of the iX_pipe_en signal which is then shifted down the pipe. From this value, we derive the enable signals (iX_eX_data_en and iX_eX_ctl_en) for the individual pipeline FFs. For the ...data_en signals, this makes sense to me, but the ...ctl_en signals stay active for one additional cycle. This leads to some "random" value being latched in the control FFs one cycle after dec_iX_decode_d changes to 0 (due to stalling etc.). So far, I don't think this "random" value matters, since the piped destination-packet contains a valid-decode flag that is not set for this cycle. But what was the design decision for this behavior?
Is this related to the comment that reads "// allow illegals to flow down the pipe"?

I would really appreciate some explanation.

Kind regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant