oxidecomputer / oxidecomputer/hubris
thermal: want a mechanism to disable components instead of the main system
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
As the thermal management subsystem works today, when any sensor reaches its model.should_power_down value, which gives us a ControlResult::PowerDown, with the ultimate result of thermal task calling the power_down() method of its BSP. I think what we want here is a way for a model to specify what should be powered down. For example: if a transceiver module were to to have reported a temperature above the power down threshold in our model for it, the entire switch would power down. This behavior is not acceptable given the failure mode. The behavior we'd want is for the thermal model to optionally specify a device to shut down instead of the whole system.
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 thermal management flow from model.should_power_down through ControlResult::PowerDown, the thermal task, and the BSP power_down() method. Trace how a model currently signals a system shutdown, then define completion as allowing it to optionally identify a component to shut down instead of powering down the entire system.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100