CPU and GPU temperature sensors exported as thermal zones only
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
In 5.10, the CPU and GPU temperature sensors are exported as thermal zones (under /sys/devices/virtual/thermal) together with a properly configured cooling device. This is much appreciated, since the board no longer reboots under load, and there is no need to manually throttle the CPU.
On the other hand, the sensors are no longer visible to the usual userspace monitoring tools, such as the sensors command-line utility. It is my (perhaps incorrect) understanding that solving this is a matter of exporting the sensors under /sys/class/hwmon in addition to the existing thermal zones.
Please consider this feature request as having low priority: the current thermal support is great (it has solved all of my problems with boards rebooting in the middle of demos), having the sensors visible to standard monitoring tools would just be a welcome extra.
This is related to https://www.olimex.com/forum/index.php?topic=8142.0 and https://www.olimex.com/forum/index.php?topic=8111.0
Contributor guide
No contributing guide indexed for this repository
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 by tracing how the 5.10 CPU and GPU sensors are exposed under /sys/devices/virtual/thermal and how the cooling device is configured. Compare that exposure with the /sys/class/hwmon interface used by the sensors command-line utility. Done means the sensors are visible to standard monitoring tools while the existing thermal zones and cooling behavior remain intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- embedded-iot, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100