oxidecomputer / oxidecomputer/quartz
qsfp_x32: monitor the main QSFP V3P3 rail
Open
Nobody has claimed this yet.
Front IO - QSFPx32
- Dominant language
- VHDL
- Stars
- 22
- Forks
- 2
- Avg merge
- 9h 38m
- Merged PRs (30d)
- 1
Description
Right now the enable is just tied on and the pg/alert pins go nowhere (https://github.com/oxidecomputer/quartz/blob/main/hdl/projects/sidecar/qsfp_x32/QsfpX32ControllerTop.bsv#L769-L771).
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 in hdl/projects/sidecar/qsfp_x32/QsfpX32ControllerTop.bsv at lines 769-771, where the QSFP V3P3 enable, pg, and alert pins are handled. Trace the surrounding controller logic and determine how the main rail should be monitored; done means the power-good and alert signals are no longer unused and the rail status is represented by the controller.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100