Add asyncReset support to CsrTopConfig
- Dominant language
- Dart
- Stars
- 115
- Forks
- 39
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 1
Description
CSR registers built by `CsrBlock` use ROHD's `Sequential` to drive
storage, which supports an `asyncReset` flag to treat `reset` as
asynchronous instead of synchronous. `CsrTopConfig` had no way to
request this, so CSR registers were always reset synchronously.
Add an `asyncReset` flag (default `false`, backward compatible) to
`CsrTopConfig`, threaded down through `CsrTop` and `CsrBlock` into the
`Sequential(...)` call that drives each register.
See proposed fix: caflore1/rohd-hcl#2
Contributor guide
Research direction
Start by locating CsrTopConfig, then trace how configuration reaches CsrTop and CsrBlock. Inspect the Sequential call that drives each CSR register and confirm how its asyncReset option is used. Done means the flag defaults to false for compatibility and can request asynchronous reset throughout the CSR construction path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100