https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #12 from Maciej Stanczew <maciej.stancze...@gmail.com> --- My usecases for all of the filtered drivers: coretemp: Similarly to what Artem mentioned, I'm interested in package temperature, not per-core temperatures. k10temp: Ryzen CPUs have a peculiar way of reporting Tctl (search "Ryzen sawtooth"), and because of that I'd like to also monitor Tccd1 (which behaves much more reasonably). (Also, k10temp only provides package temperatures, so it's a bit unintuitive when the CPU plugin splits it per-core, with all cores reporting the same temperature.) amdgpu: This I think is the most clear, we're missing edge/junction/memory temperatures, fan speed, power, and voltage, and they are not available in any other way. > The cause of the problem is, that in the new sensors plugin coretemp, k10temp > and amdgpu are intentionally excluded to not expose duplicated sensors > because these are already handles by the CPU and GPU plugins. Is there any harm in having those sensors duplicated? Personally I think that CPU/GPU plugins could expose a vendor-neutral, standardized set of sensors, while Hardware Sensors could still expose raw, driver-specific sensor data. That way users could use sensors from CPU/GPU plugins for basic temperature/frequency/usage monitoring, while more demanding users could get all the data that the drivers provide. -- You are receiving this mail because: You are watching all bug changes.
