[aon_timer] Consider requirements for clk_aon_i vs clk_i
Open
@GregAC is already working on this.
Since Apr 2, 2024.
Earlgrey-PROD Candidate
IP:aon_timer
Priority:P2
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
The current aon_timer testbench has a limitation so we must start clk_aon_i before clk_i can start (https://github.com/lowRISC/opentitan/issues/6821). This is not an issue for earlgrey as the aon clock is always active before other clocks (the FSM in pwrmgr that enables the fast clocks is clocked from the aon clock).
We should consider either making this an explicit design constraint or fixing the limitation to allow the fast clock to start with the aon clock in the aon_timer testbench.
I'd favour the former as it seems like a reasonable design constraint.
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.
Assessment
This issue has not been assessed yet.