lowRISC / lowRISC/opentitan

[top_darjeeling] Enable lint checks for all HW IP blocks

Open
#26,245 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

- [ ] clkmgr
- [ ] pinmux
- [ ] soc_dbg_ctrl_decode
- [ ] soc_proxy
- [ ] jtag_dtm
- [ ] chip_darjeeling_asic
- [ ] adapter_dmi
- [ ] ac_range_check (new)
- [ ] other new IPs?

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.

Research direction

Start by reviewing the lint setup and the listed HW IP blocks: clkmgr, pinmux, soc_dbg_ctrl_decode, soc_proxy, jtag_dtm, chip_darjeeling_asic, adapter_dmi, and ac_range_check. Determine how lint checks are enabled for each block and whether other new IPs are included; done means all applicable blocks pass the enabled lint checks.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot, testing-qa, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.