[top, padring] Template padring generation or move padring parameterization into padring package
Open
Nobody has claimed this yet.
TOP:earlgrey
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
Description
As pointed out by @glaserf in this comment, we should consider templating the padring or a top-specific padring package file taking care of driving the padring parameters like pad orientation and scan role. Right now, these parameter lists are large and updating them is error prone.
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 by reviewing the top-specific padring parameter lists and the padring package boundary, then read the referenced discussion in PR 30545. Determine whether templating the padring or moving parameterization into a padring package is the agreed direction; done means the large parameter lists are no longer error-prone to update.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100