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

fix README documentation for RoCC accelerators

Browse Source
This commit is contained in:
Howard Mao
2019-02-15 15:30:22 -08:00
parent 51ca3dd1b9
commit e5cbf49bb4
1 changed files with 16 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
README.md
View File

@@ -320,11 +320,13 @@ RoCC accelerators are lazy modules that extend the LazyRoCC class.
Their implementation should extends the LazyRoCCModule class. Their implementation should extends the LazyRoCCModule class.
```scala ```scala
class CustomAccelerator(implicit p: Parameters) extends LazyRoCC { class CustomAccelerator(opcodes: OpcodeSet)
(implicit p: Parameters) extends LazyRoCC(opcodes) {
override lazy val module = new CustomAcceleratorModule(this) override lazy val module = new CustomAcceleratorModule(this)
} }
class CustomAcceleratorModule(outer: CustomAccelerator) extends LazyRoCCModule(outer) { class CustomAcceleratorModule(outer: CustomAccelerator)
extends LazyRoCCModuleImp(outer) {
val cmd = Queue(io.cmd) val cmd = Queue(io.cmd)
// The parts of the command are as follows // The parts of the command are as follows
// inst - the parts of the instruction itself // inst - the parts of the instruction itself
@@ -342,7 +344,11 @@ Their implementation should extends the LazyRoCCModule class.
} }
``` ```
The LazyRoCC class contains two TLOutputNode instances, `atlNode` and `tlNode`. The `opcodes` parameter for `LazyRoCC` is
the set of custom opcodes that will map to this accelerator. More on this
in the next subsection.
The `LazyRoCC` class contains two TLOutputNode instances, `atlNode` and `tlNode`.
The former connects into a tile-local arbiter along with the backside of the The former connects into a tile-local arbiter along with the backside of the
L1 instruction cache. The latter connects directly to the L1-L2 crossbar. L1 instruction cache. The latter connects directly to the L1-L2 crossbar.
The corresponding Tilelink ports in the module implementation's IO bundle The corresponding Tilelink ports in the module implementation's IO bundle
@@ -358,26 +364,21 @@ detailed information on the different IOs.
### Adding RoCC accelerator to Config ### Adding RoCC accelerator to Config
RoCC accelerators can be added to a core by overriding the BuildRoCC parameter RoCC accelerators can be added to a core by overriding the `BuildRoCC` parameter
in the configuration. This takes a sequence of RoccParameters objects, one in the configuration. This takes a sequence of functions producing `LazyRoCC`
for each accelerator you wish to add. The two required fields for this objects, one for each accelerator you wish to add.
object are `opcodes` which determines which custom opcodes get routed to the
accelerator, and `generator` which specifies how to build the accelerator itself.
For instance, if we wanted to add the previously defined accelerator and For instance, if we wanted to add the previously defined accelerator and
route custom0 and custom1 instructions to it, we could do the following. route custom0 and custom1 instructions to it, we could do the following.
```scala ```scala
class WithCustomAccelerator extends Config((site, here, up) => { class WithCustomAccelerator extends Config((site, here, up) => {
case RocketTilesKey => up(RocketTilesKey, site).map { r => case BuildRoCC => Seq((p: Parameters) => LazyModule(
r.copy(rocc = Seq( new CustomAccelerator(OpcodeSet.custom0 | OpcodeSet.custom1)(p)))
RoCCParams(
opcodes = OpcodeSet.custom0 | OpcodeSet.custom1,
generator = (p: Parameters) => LazyModule(new CustomAccelerator()(p)))))
}
}) })
class CustomAcceleratorConfig extends Config( class CustomAcceleratorConfig extends Config(
new WithCustomAccelerator ++ new BaseConfig) new WithCustomAccelerator ++ new DefaultExampleConfig)
``` ```
## Adding a submodule ## Adding a submodule