rust-embedded / rust-embedded/riscv
`riscv-peripheral`: Allow dynamic change of ACLINT's clock frequency
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.1k
- Forks
- 200
- Avg merge
- 11d 2h
- Merged PRs (30d)
- 2
Description
As noted here, some implementations of the CLINT peripheral allow different clock frequencies. Even if the specification tells that the clock frequency must be fixed, we might extend our CLINT API to allow dynamic frequency.
I would still use the fixed frequency approach, but adding an auxiliary struct that keeps track of clock frequency would be useful.
Contributor guide
No contributing guide indexed for this repository
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 reading the existing ACLINT/CLINT API and the linked config.yml entry describing clock frequency. Determine how an auxiliary clock-frequency state would fit while preserving the current fixed-frequency approach; done means the API supports implementations with dynamically changing frequencies and the behavior is covered by the repository's existing validation or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100