| commit | 9b8fa6d0a8ca53173aa6f0c4b3a3f69cc37d3b5c | [log] [tgz] |
|---|---|---|
| author | Timothy Chen <timothytim@google.com> | Sat Apr 24 15:39:16 2021 -0700 |
| committer | tjaychen <timothytim@google.com> | Mon Apr 26 16:53:37 2021 -0700 |
| tree | 80f9d951c50e07d3492fca17af76c3402e1a0cbc | |
| parent | 7233243ff5a7e1e7eea238299bc6311f30513a00 [diff] |
[util] Fix for intermodule names This issue was originally discovered by @eunchan. The top level template code originally used im_netname for determining the code for dangling nets at both the module instantiation level, as well as the broadcast tie-off (for modules like kmac_app and edn1). However, the input to im_netname was different in each case. For module level instantiation, the input was the module `inter_signal` definition which does not include `req/rsp` as part of the struct name. For broadcast tie-off, such as kmac_app and edn1, the input was the top level inter_module definition that includes `req/rsp` as part of the struct name already. This creates a conflict where either the module level didn't contain the suffix or the top level had an extra suffix. The fix moves the default net name creation directly to when the top level defintion is created and avoids this conflict. Eventually this same scheme can be ported to im_netname as well without needing to construct on the fly. But that will be done in a separate PR. Signed-off-by: Timothy Chen <timothytim@google.com>
OpenTitan is an open source silicon Root of Trust (RoT) project. OpenTitan will make the silicon RoT design and implementation more transparent, trustworthy, and secure for enterprises, platform providers, and chip manufacturers. OpenTitan is administered by lowRISC CIC as a collaborative project to produce high quality, open IP for instantiation as a full-featured product. See the OpenTitan site and OpenTitan docs for more information about the project.
This repository contains hardware, software and utilities written as part of the OpenTitan project. It is structured as monolithic repository, or “monorepo”, where all components live in one repository. It exists to enable collaboration across partners participating in the OpenTitan project.
The project contains comprehensive documentation of all IPs and tools. You can access it online at docs.opentitan.org.
Have a look at CONTRIBUTING for guidelines on how to contribute code to this repository.
Unless otherwise noted, everything in this repository is covered by the Apache License, Version 2.0 (see LICENSE for full text).