All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
Date: Fri, 16 Aug 2013 07:03:09 +0000	[thread overview]
Message-ID: <520DCEAD.4070107@ladisch.de> (raw)
In-Reply-To: <CAFSPGzQyxOOhjawcQj=wH+k1b=OC1gGf6CKWoU89TWVTykNcOQ@mail.gmail.com>

Dev, Kapil wrote:
> On Thu, Aug 15, 2013 at 3:55 AM, Clemens Ladisch wrote:
>> On 08/14/2013 09:16 PM, Dev, Kapil wrote:
>>> I got a little confused about the way temperature-computation is
>>> explained on page 393. The interpretation of D18F3xA4[31:21] seems to
>>> be different based on the D18F3xA4[17:16] bits.
>>
>> These two bits should always be 00; Linux never tries to write the
>> temperature value.
>
> I see. It means  that D18F3xA4[31:21] always denotes the Tctl
> temperature (control temperature). Where, Tctl <= Tmeasured <> Tctl+TmpMaxDiffUp.

All four fields in bits 0..12 can make the shown temperature value
slightly out of date.  This is intentional to smooth out the
measurements.

> The value of TmpMaxDiffUp is between 0 and 9C

No, it is between 0 and 9.

> depending on the value of two bits, D18F3xA4[6:5]. Should I check the
> value of these two bits

Over time, the average value should be accurate.

> I noticed, that the reported temperature was very erratic, changing
> anywhere between 3 C and 30C,

No, between 3 and 30.

> even when there was no workload running on the cpu.

When the CPU is mostly idle, even small wakeups for interrupts will
result in rather large relative changes in power consumption and,
therefore, power dissipation.

> If I understand it correctly, the implementation is such that it
> reports following values:
> 1) Highest temperature = 70

This is not the highest possible value; temp1_max is the highest value
during normal operation.  On AMD CPUs, this is the point at which the
CPU fan should run at 100 % (of TDP).

> 2) Critical temperature = mostly 70; [...] which kind of means that
> D18F3x64[22:16] is mostly fixed to 36?

This register has whatever value the BIOS has written into it.

> 3)  Hysteresis value: [...] Is the value of D18F3x64[22:16] fixed or
> it changes based on some condition?

It changes when the BIOS (or somebody else) writes to it.

> I am trying to compute the temperature values as accurately as
> possible because my project involves calibrating the die-temperature
> values against other measurements

Did you read section 2.11.1?  It says:
| Tctl does not represent a temperature which could be measured on the
| die or the case of the processor. Instead, it specifies the processor
| temperature relative to the maximum operating temperature

The maximum operating temperature is defined as 70, but does not
correspond to a known absolute temperature.

This temperature sensor is designed to control the CPU fan; it is _not_
intended to result in a value that can be shown to the user in a way
that makes much sense.


Regards,
Clemens

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2013-08-16  7:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
2013-08-13 20:27 ` Guenter Roeck
2013-08-13 21:11 ` Dev, Kapil
2013-08-13 21:51 ` Guenter Roeck
2013-08-14  2:41 ` Dev, Kapil
2013-08-14  3:02 ` Guenter Roeck
2013-08-14  3:09 ` Dev, Kapil
2013-08-14  4:56 ` Guenter Roeck
2013-08-14  5:17 ` Kapil Dev
2013-08-14  5:30 ` Guenter Roeck
2013-08-14  5:32 ` Phil Pokorny
2013-08-14 17:20 ` Dev, Kapil
2013-08-14 18:29 ` Guenter Roeck
2013-08-14 18:33 ` Guenter Roeck
2013-08-14 19:06 ` Dev, Kapil
2013-08-14 20:03 ` Guenter Roeck
2013-08-14 20:45 ` Dev, Kapil
2013-08-14 22:39 ` Guenter Roeck
2013-08-15  4:16 ` Dev, Kapil
2013-08-15  4:29 ` Guenter Roeck
2013-08-15  4:32 ` Dev, Kapil
2013-08-15  5:30 ` Guenter Roeck
2013-08-15  7:55 ` Clemens Ladisch
2013-08-16  3:48 ` Dev, Kapil
2013-08-16  7:03 ` Clemens Ladisch [this message]
2013-08-16  8:57 ` Kapil Dev
2013-08-16  9:27 ` Clemens Ladisch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=520DCEAD.4070107@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=lm-sensors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.