Maybe my way of thinking was too simple! When using 'cpu_thermal' as target in fragment3 that overlay works, using SoC temperature. Hence I simply followed the same approach for the NVMe temp sensor.
Or will it just work that way - by coincidence - because 'cpu_thermal' linked node exists somewhere?
Isn't NVMe drive temperature implemented in hwmon starting from Kernel 5.5 (CONFIG_NVME_HWMON)?
For an HDD which exposes a temperature (hddtemp) one would use 'drivetemp' labelwith hwmon<x> the HDD sensors temperature.
Or am I wrong starting from here?
In case of an NVMe there is no 'drivetemp' entry in hwmon, but the 'nvme' label.
Or will it just work that way - by coincidence - because 'cpu_thermal' linked node exists somewhere?
Isn't NVMe drive temperature implemented in hwmon starting from Kernel 5.5 (CONFIG_NVME_HWMON)?
For an HDD which exposes a temperature (hddtemp) one would use 'drivetemp' label
Code:
cat /sys/class/hwmon/hwmon*/nameCode:
grep -l "drivetemp" /sys/class/hwmon/hwmon*/name/sys/class/hwmon/hwmon<x>/nameOr am I wrong starting from here?
In case of an NVMe there is no 'drivetemp' entry in hwmon, but the 'nvme' label.
Statistics: Posted by aBUGSworstnightmare — Wed Aug 21, 2024 8:50 pm