We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The dynamic MUX, in certain instances, can violate RSP-3 and RSP-5 and cause similar violations in downstream modules. The root cause is that the r_ready signal is propagated incorrectly: https://github.com/pulp-platform/hci/blame/afe0220f9a2f132dc8655c48da05aae5121a570b/rtl/core/hci_core_mux_dynamic.sv#L212 The correct behavior would be to route r_ready similarly to what is done for r_valid.
r_ready
r_valid
The text was updated successfully, but these errors were encountered:
FrancescoConti
No branches or pull requests
The dynamic MUX, in certain instances, can violate RSP-3 and RSP-5 and cause similar violations in downstream modules. The root cause is that the
r_ready
signal is propagated incorrectly:https://github.com/pulp-platform/hci/blame/afe0220f9a2f132dc8655c48da05aae5121a570b/rtl/core/hci_core_mux_dynamic.sv#L212
The correct behavior would be to route
r_ready
similarly to what is done forr_valid
.The text was updated successfully, but these errors were encountered: