[alert_handler] Allow latching of alerts that were received before an alert source was enabled
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
As discussed in [AST alert reset configuration and post-reset behavior](https://docs.google.com/document/d/1KTAkLexrTPsEyJrMc6Auxiuxdv161GdEnyTbjLDY6Fw/edit), it would be great if alert_handler allowed latching alerts that were received before an alert source was enabled (see last comments in the open comment thread in that doc). This should be controlled by a new CSR bit (that would have a reset value of enabled, and clearing that bit would clear the latched value).
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 the alert_handler entry point and the linked “AST alert reset configuration and post-reset behavior” document, especially its final comments. Confirm the existing alert-source enable and latching behavior, then define the new CSR bit so its reset value enables latching and clearing it clears the latched value. Done means the requested pre-enable alert behavior and CSR semantics are covered.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100