wu-arch/chipyard
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

docs: Fix comment on rocc tag bits

Browse Source
This commit is contained in:
Jerry Zhao
2023-06-13 00:57:56 -07:00
parent 8a60b36125
commit e4eaa50354
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/Customization/RoCC-Accelerators.rst
View File

@@ -88,7 +88,8 @@ In your ``LazyRoCCModuleImp``, the signal ``io.mem`` is a ``HellaCacheIO``, whic
At a high level, you must tag requests that you send across this interface using the ``io.mem.req.tag``, and the tag will be returned to you when the data is ready. At a high level, you must tag requests that you send across this interface using the ``io.mem.req.tag``, and the tag will be returned to you when the data is ready.
Responses may come back out of order if you issue multiple requests, so you can use these tags to tell what data came back. Responses may come back out of order if you issue multiple requests, so you can use these tags to tell what data came back.
Note that the top two bits of the tag are reserved, and MUST be set to zero, or the interface will exhibit undefined behavior. Note that the number of tag bits is controled by ``dcacheReqTagBits``, which is usually set to 6.
Using more than 6 bits will cause errors or hangs.
Adding RoCC accelerator to Config Adding RoCC accelerator to Config