Skip to content

[axi_sub] Remove the duplicated axi_sub library#209

Open
glaserf wants to merge 4 commits into
chipsalliance:v1p5from
glaserf:rm-i3c-axi-sub
Open

[axi_sub] Remove the duplicated axi_sub library#209
glaserf wants to merge 4 commits into
chipsalliance:v1p5from
glaserf:rm-i3c-axi-sub

Conversation

@glaserf

@glaserf glaserf commented Jun 2, 2026

Copy link
Copy Markdown
Collaborator

The lib was previously duplicated from the original Caliptra version, solely to introduce a duplicate parameter (AG with the same function as BW).

Additionally, axi_sub does anyways not support different data widths for the axi and component side, which the additional parameter seems to have been targeted at.

@linux-foundation-easycla

linux-foundation-easycla Bot commented Jun 2, 2026

Copy link
Copy Markdown

CLA Signed
The committers listed above are authorized under a signed CLA.

  • ✅ login: glaserf / name: Florian Glaser (41a7968)

The lib was previously duplicated from the original caliptra version
only to introduce a duplicate parameter (AG with the same function as
BW). Additionally, axi_sub would not support different data widths for
the axi and component side.

Signed-off-by: Florian Glaser <glaserf@lowrisc.org>
moidx
moidx previously approved these changes Jun 3, 2026

@calebofearth calebofearth left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Sorry to change my review. I realized that the underlying lint problem we need to resolve also requires changes here:
https://github.com/glaserf/i3c-core/blob/41a7968399d318445bece2750a1eac93a8b37103/src/hci/axi_adapter.sv#L142
The axi_if adds 4 new AR and AW signals in newer versions of caliptra-rtl, so you will need to update the submodule. Then the new AxPROT,AxCACHE, AxREGION, AxQOS signals should be routed from the top level down into axi_sub.

In fact, I'd actually recommend getting rid of all the local signal definitions entirely, and just routing the axi_if from the top i3c module all the way down to axi_adapter/axi_sub. Then it will be portable and compatible with any future changes without having to modify the i3c repo.

@glaserf

glaserf commented Jun 8, 2026

Copy link
Copy Markdown
Collaborator Author

In fact, I'd actually recommend getting rid of all the local signal definitions entirely, and just routing the axi_if from the top i3c module all the way down to axi_adapter/axi_sub. Then it will be portable and compatible with any future changes without having to modify the i3c repo.

Hi @calebofearth
Sure, no problem. This absolutely makes sense. I will implement this as soon as my schedule allows.

@glaserf

glaserf commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator Author

Apologies for the longer wait time. axi_if is now in, lets see what CI has to say about it.

glaserf added 3 commits June 12, 2026 09:42
This allows for easier updates of the bus infra in caliptra-ss

Signed-off-by: Florian Glaser <glaserf@lowrisc.org>
Signed-off-by: Florian Glaser <glaserf@lowrisc.org>
This is mainly done to incorporate the added signals of the axi_if, but
also to get rid of the vastly outdated submodule version.

Signed-off-by: Florian Glaser <glaserf@lowrisc.org>
@glaserf

glaserf commented Jun 12, 2026

Copy link
Copy Markdown
Collaborator Author

@calebofearth I updated the caliptra-rtl submodule to the current head of main in order to get the axi_if with the added signals. PLMK if I should change anything about that.

@glaserf glaserf requested review from calebofearth and moidx June 12, 2026 07:49
@calebofearth

Copy link
Copy Markdown
Collaborator

@calebofearth I updated the caliptra-rtl submodule to the current head of main in order to get the axi_if with the added signals. PLMK if I should change anything about that.

It looks like the only relevant updates from caliptra-rtl are for skidbuffer, axi_if, axi_sub, and caliptra_prim modules (fifo_sync and flop_2sync). The AXI changes are necessary, and the caliptra_prim changes are innocuous IMO. Do you see any other modules affected by the update? If not, I think this is fine.

@glaserf

glaserf commented Jun 17, 2026

Copy link
Copy Markdown
Collaborator Author

@calebofearth Sorry I totally forgot to reply. I agree that the submodule update should be unproblematic.

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