Guenter Roeck wrote:
> On Tue, Sep 05, 2017 at 04:12:07PM +0200, Clemens Ladisch wrote:
>> Guenter Roeck wrote:
>>> What we should do then, as we did for coretemp, would be to collect the
>>> various
>>> temperature offsets (and temperature limits, for that matter) and apply
>>> per-CPU
>>> adjus
On Tue, Sep 05, 2017 at 04:12:07PM +0200, Clemens Ladisch wrote:
> Guenter Roeck wrote:
> > On 09/04/2017 11:47 PM, Clemens Ladisch wrote:
> >> Guenter Roeck wrote:
> >>> Some of this is guesswork, but afaics it is working. No idea if there
> >>> is a better way to determine the temperature offset.
Guenter Roeck wrote:
> On 09/04/2017 11:47 PM, Clemens Ladisch wrote:
>> Guenter Roeck wrote:
>>> Some of this is guesswork, but afaics it is working. No idea if there
>>> is a better way to determine the temperature offset.
>>
>> The reported value is not an absolute temperature on any CPU.
>>
>>
On 09/04/2017 11:47 PM, Clemens Ladisch wrote:
Guenter Roeck wrote:
Add support for temperature sensors on Family 17h (Ryzen) processors.
Signed-off-by: Guenter Roeck
---
Some of this is guesswork, but afaics it is working. No idea if there
is a better way to determine the temperature offset.
Guenter Roeck wrote:
> Add support for temperature sensors on Family 17h (Ryzen) processors.
>
> Signed-off-by: Guenter Roeck
> ---
> Some of this is guesswork, but afaics it is working. No idea if there
> is a better way to determine the temperature offset.
The reported value is not an absolute
Add support for temperature sensors on Family 17h (Ryzen) processors.
Signed-off-by: Guenter Roeck
---
Some of this is guesswork, but afaics it is working. No idea if there
is a better way to determine the temperature offset.
drivers/hwmon/k10temp.c | 42 +++-
6 matches
Mail list logo