You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's a longstanding limitation of phosphor-pid-control that you can only set the automatic/manual status of a thermal zone. You can't set this on an individual fan basis.
Is there any demand for having this ability? It might be nice for some fans, in the same thermal zone, to be set to manual mode, while still having the other fans run automatically (as guided by PID loops).
Sometimes it comes up, but so rarely that this limitation hasn't really been a problem.
When exploring how to model automatic/manual status in Redfish, this came up. It seems awkward in Redfish to have to do it for an entire thermal zone at a time: #21
The text was updated successfully, but these errors were encountered:
It's a longstanding limitation of
phosphor-pid-control
that you can only set the automatic/manual status of a thermal zone. You can't set this on an individual fan basis.Is there any demand for having this ability? It might be nice for some fans, in the same thermal zone, to be set to manual mode, while still having the other fans run automatically (as guided by PID loops).
The existing IPMI commands only work on an entire thermal zone at a time: https://github.com/openbmc/phosphor-pid-control/blob/master/ipmi.md
Sometimes it comes up, but so rarely that this limitation hasn't really been a problem.
When exploring how to model automatic/manual status in Redfish, this came up. It seems awkward in Redfish to have to do it for an entire thermal zone at a time: #21
The text was updated successfully, but these errors were encountered: