linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Caesar Wang <caesar.wang@rock-chips.com>
To: Daniel Kurtz <djkurtz@chromium.org>, Caesar Wang <wxt@rock-chips.com>
Cc: Heiko Stuebner <heiko@sntech.de>, Zhang Rui <rui.zhang@intel.com>,
	Eduardo Valentin <edubezval@gmail.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	linux-pm@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] thermal: rockchip: make temperature reporting much more accurate
Date: Thu, 22 Jan 2015 12:21:43 +0800	[thread overview]
Message-ID: <54C07AD7.9020102@rock-chips.com> (raw)
In-Reply-To: <CAGS+omAi+F1_1-8wmDMf9oUq6GCjXu8N4kyeNmKRWv8m3eaCrA@mail.gmail.com>


在 2015年01月22日 12:01, Daniel Kurtz 写道:
> On Thu, Jan 22, 2015 at 1:29 AM, Caesar Wang <wxt@rock-chips.com> wrote:
>> In general, the kernel should report temperature readings exactly as
>> reported by the hardware. The cpu / gpu thermal driver works in 5 degree
>> increments,but we ought to do more accurate. The temperature will do
>> linear interpolation between the entries in the table.
>>
>> Test= $md5sum /dev/zero &
>> $while true; do grep "" /sys/class/thermal/thermal_zone[1-2]/temp;
>> sleep .5; done
>>
>> e.g. We can get the result as follows:
>>      /sys/class/thermal/thermal_zone1/temp:39994
>>      /sys/class/thermal/thermal_zone2/temp:39086
>>      /sys/class/thermal/thermal_zone1/temp:39994
>>      /sys/class/thermal/thermal_zone2/temp:39540
>>      /sys/class/thermal/thermal_zone1/temp:39540
>>      /sys/class/thermal/thermal_zone2/temp:39540
>>      /sys/class/thermal/thermal_zone1/temp:39540
>>      /sys/class/thermal/thermal_zone2/temp:39994
>>
>> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
>> Reviewed-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
>>
>> ---
>>
>> Changes in v3:
>> Suggested-by Daniel Kurtz,
>> the check doesn't reject "code == 0xfff"
>> Fixed in rk_tsadcv2_code_to_temp(u32 code)
>>
>> Changes in v2:
>> Reviewed-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
>>
>>   drivers/thermal/rockchip_thermal.c | 32 ++++++++++++++++++++++----------
>>   1 file changed, 22 insertions(+), 10 deletions(-)
>>
>> diff --git a/drivers/thermal/rockchip_thermal.c b/drivers/thermal/rockchip_thermal.c
>> index 1bcddfc..ce18007 100644
>> --- a/drivers/thermal/rockchip_thermal.c
>> +++ b/drivers/thermal/rockchip_thermal.c
>> @@ -193,19 +193,22 @@ static u32 rk_tsadcv2_temp_to_code(long temp)
>>
>>   static long rk_tsadcv2_code_to_temp(u32 code)
>>   {
>> -       int high, low, mid;
>> -
>> -       low = 0;
>> -       high = ARRAY_SIZE(v2_code_table) - 1;
>> -       mid = (high + low) / 2;
>> +       unsigned int low = 0;
>> +       unsigned int high = ARRAY_SIZE(v2_code_table) - 1;
>> +       unsigned int mid = (low + high) / 2;
>> +       unsigned int num;
>> +       unsigned long denom;
>>
>> +       /* No code available, return callback */
>>          if (code > v2_code_table[low].code || code < v2_code_table[high].code)
>> -               return 125000; /* No code available, return max temperature */
>> +               return rk_tsadcv2_code_to_temp(code);
> Isn't this an infinite recursion?

No, I think we can try check if it  is happened.
Maybe we can return a warning/error for it.
>>          while (low <= high) {
>> -               if (code >= v2_code_table[mid].code && code <
>> -                   v2_code_table[mid - 1].code)
>> -                       return v2_code_table[mid].temp;
>> +               if (code >= v2_code_table[mid].code &&
>> +                   code < v2_code_table[mid - 1].code)
>> +                       break;
>> +               else if (code == TSADCV2_DATA_MASK)
>> +                       break;
>>                  else if (code < v2_code_table[mid].code)
>>                          low = mid + 1;
>>                  else
>> @@ -213,7 +216,16 @@ static long rk_tsadcv2_code_to_temp(u32 code)
>>                  mid = (low + high) / 2;
>>          }
>>
>> -       return 125000;
>> +       /*
>> +        * The 5C granularity provided by the table is too much. Let's
>> +        * assume that the relationship between sensor readings and
>> +        * temperature between 2 table entries is linear and interpolate
>> +        * to produce less granular result.
>> +        */
>> +       num = v2_code_table[mid].temp - v2_code_table[mid - 1].temp;
>> +       num *= v2_code_table[mid - 1].code - code;
>> +       denom = v2_code_table[mid - 1].code - v2_code_table[mid].code;
>> +       return v2_code_table[mid - 1].temp + (num / denom);
>>   }
>>
>>   /**
>> --
>> 1.9.1
>>
>>
>
>

-- 
Best regards
Caesar Wang (王晓腾)
福州瑞芯微电子有限公司
Fuzhou Rockchip Electronics Co.Ltd
福建省福州市铜盘路软件大道89号软件园A区18号楼(350003)
Addr:No.18 Building, A District, No.89, software Boulevard Fuzhou, Fujian,PRC
Email:wxt@rock-chips.com
Tel:+86-591-83991906/07->8221



  reply	other threads:[~2015-01-22  4:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21 17:29 [PATCH v3 0/1] thermal: rockchip: make temperature reporting much more accurate Caesar Wang
2015-01-21 17:29 ` [PATCH v3] " Caesar Wang
2015-01-22  4:01   ` Daniel Kurtz
2015-01-22  4:21     ` Caesar Wang [this message]
2015-01-22  4:25       ` Daniel Kurtz
2015-01-22  4:57         ` Caesar Wang

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=54C07AD7.9020102@rock-chips.com \
    --to=caesar.wang@rock-chips.com \
    --cc=djkurtz@chromium.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=edubezval@gmail.com \
    --cc=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=rui.zhang@intel.com \
    --cc=wxt@rock-chips.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).