PR to merge chips-IT changes to iDMA#109
Conversation
|
@RiccardoGandolfi make sure you align the parameter definition to the IP name convention (i.s. |
Should be done now |
81b2ee6 to
98bd341
Compare
There was a problem hiding this comment.
A few things:
-
Rebase first
-
Default regression:
BurstLendefaults to 5, but the splitter was hardcoded to 8, so every existing variant's default burst drops 2048B→256B on a 64-bit bus (8×). The cap belongs to a specific system; keep the default at 8. -
These are DB values:
'd8 = log2(max_beats_per_burst=256)and'd12 = log2(page_size=4096)fromidma_axi.yml. The legalizer already derives bursts from these per-protocol; the page splitter should takelog2(max_beats_per_burst)/log2(page_size)from the DB (asidma_legalizer_pow2_splitteralready does) instead of a hand-set param.
For the 256B bursts themselves, the reg frontend already exposes reduce_len/max_llen - set reduce_len=1, max_llen=5, no RTL change.
Co-authored-by: Daniel Keller <daniel.keller.m@gmail.com>
53d5fe9 to
99f0f6a
Compare
Co-authored-by: Daniel Keller <daniel.keller.m@gmail.com>
Co-authored-by: Daniel Keller <daniel.keller.m@gmail.com>
Co-authored-by: Daniel Keller <daniel.keller.m@gmail.com>
PR #109's rebased NumStreams commit resurrected idma_reg.hjson.tpl (removed by the SystemRDL conversion in #73) and re-added a second gen_hw2reg_unused generate block in idma_reg.sv.tpl. The duplicate label breaks elaboration of the reg block on every variant (DC VER-288, VCS IPD, Questa vlog-2388), failing the devel pipeline. Keep only #109's BurstLen change.
Just added a parameter to the iDMA_legalizer_page_splitter module.
Related to this PR: pulp-platform/pulp_cluster#115