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

[RACL] Enable initial RACL support for sram_ctrl #26047

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

davidschrammel
Copy link
Contributor

@davidschrammel davidschrammel commented Jan 28, 2025

This commit enables RACL for sram_ctrl. However, we only enable it for its regs tlul interface for now. Enabling RACL for its sram tlul interface will follow in a separate commit or PR since it requires more intrusive changes.

The issues raised in #26004 also affect generated files here.
They are fixed in #26056 and I will rebase this PR on top assuming #26056 will be merged to master before this PR.

@davidschrammel davidschrammel requested review from Razer6, rswarbrick and vogelpi and removed request for msfschaffner January 28, 2025 18:37
Copy link
Member

@Razer6 Razer6 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me.

Copy link
Contributor

@rswarbrick rswarbrick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The technical change looks sensible to me, but please could we tidy up the history a bit? It looks like several changes have been globbed together into a single commit.

// Enable asynchronous transitions on alerts.
parameter logic [NumAlerts-1:0] AlertAsyncOn = {NumAlerts{1'b1}},
parameter logic [NumAlerts-1:0] AlertAsyncOn = {NumAlerts{1'b1}},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I realise that this indentation change is probably the right thing to do (either that or shortening some of the indents, to wrap "per block").

But can we split it out of the commit that enables RACL? Or drop the change from this PR?

There's no reason the changes need to be atomic.

.clk_i,
.rst_ni,
.tl_i (regs_tl_i),
.tl_o (regs_tl_o),
.tl_i ( regs_tl_i ),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A similar note here to the one about the spacing earlier. I'd suggest trying to match the format in the existing code.

(I've just looked and it's really rather inconsistent in this file! Very happy for a follow-up that makes it consistent, but it should be a separate commit)

@davidschrammel
Copy link
Contributor Author

It looks like several changes have been globbed together into a single commit.

@rswarbrick I have separated out the formatting changes. Are there any other changes that you wanted to be separate? Unfortunately, a lot of the code changes are auto-generated and I don't think it makes sense to put those in a separate commit as well.

Apart from that, similarly to #26044 I would also rebase this PR on top of #26056 after it has been merged.

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

Successfully merging this pull request may close these issues.

3 participants