lowRISC / lowRISC/opentitan

[racl_ctrl] V1 Review & Signoff

Open
#27,762 0 comments 0 reactions 3 assignees View on GitHub

@rswarbrick is already working on this.

Since Jul 29, 2025.

IP:racl_ctrl
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

## Verification specification checks / updates

- [ ] https://github.com/lowRISC/opentitan/issues/27758
- [ ] https://github.com/lowRISC/opentitan/issues/27759
- [ ] https://github.com/lowRISC/opentitan/issues/27760
- [ ] https://github.com/lowRISC/opentitan/issues/27761

## Test suite checks

- [ ] SIM_SMOKE_TEST_PASSING
- [ ] SIM_CSR_MEM_TEST_SUITE_PASSING
- [ ] SIM_SMOKE_REGRESSION_SETUP
- [ ] SIM_NIGHTLY_REGRESSION_SETUP plus TB_LINT_SETUP

## Tools checks

- [ ] SIM_ALT_TOOL_SETUP

## Various checks

The following items are also part of the V1 signoff checklist.
They are explicitly included in tasks listed above and are not tracked separately; their current status is visible in the [checklist document for this IP](https://github.com/lowRISC/opentitan/blob/master/hw/ip/mbx/doc/checklist.md):
- TB_TOP_CREATED (done as part of DV_DOC_DRAFT_COMPLETED)
- PRELIMINARY_ASSERTION_CHECKS_ADDED (done as part of DV_DOC_DRAFT_COMPLETED)
- SIM_TB_ENV_CREATED (done as part of DV_DOC_DRAFT_COMPLETED)
- SIM_RAL_MODEL_GEN_AUTOMATED (done as part of DV_DOC_DRAFT_COMPLETED)
- CSR_CHECK_GEN_AUTOMATED (done as part of DV_DOC_DRAFT_COMPLETED)
- SIM_COVERAGE_MODEL_ADDED (done as part of DV_DOC_DRAFT_COMPLETED)
- TB_LINT_SETUP (done as part of SIM_NIGHTLY_REGRESSION_SETUP)
- STD_TEST_CATEGORIES_PLANNED (done as part of TESTPLAN_REVIEWED)
- V2_CHECKLIST_SCOPED (done as part of TESTPLAN_REVIEWED)

The following item does not apply to this IP, as only the one configuration currently instantiated in Darjeeling gets verified:
- TB_GEN_AUTOMATED

The following item does not apply to this IP, as it has no pre-verified submodules.
- PRE_VERIFIED_SUB_MODULES_V1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.