[ast] Check whether AST register map can be autogenerated instead of checking it in
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
The AST register table seems to be checked into the repo at the moment:
https://github.com/lowRISC/opentitan/blob/master/hw/top_earlgrey/ip/ast/doc/ast_regs.html
We should consider making this fully autogenerated as all other comportable IPs.
This is not urgent, I have hence moved this to M3.
CC @tjaychen @arnonsha @Jacob-Levy
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with hw/top_earlgrey/ip/ast/doc/ast_regs.html and compare how the other comportable IPs generate their register maps. Determine the automation path and what repository artifacts should remain; done means the AST register table is generated consistently rather than checked in manually.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100