mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Moger, Babu" <babu.moger@amd.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: clemens@ladisch.de, jdelvare@suse.com,
	linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
	Baski.Kannan@amd.com, yannick.hemery@corp.ovh.com
Subject: Re: [PATCH] hwmon: (k10temp): Check range scale when CUR_TEMP register is read-write
Date: Mon, 17 Apr 2023 09:00:01 -0500	[thread overview]
Message-ID: <6b712dd2-a884-e0ac-bfa4-3b6f8716ce90@amd.com> (raw)
In-Reply-To: <1afe95f1-cea1-418f-b9a1-23be6817157f@roeck-us.net>



On 4/16/23 09:35, Guenter Roeck wrote:
> On Thu, Apr 13, 2023 at 04:39:58PM -0500, Babu Moger wrote:
>> From: Babu Moger <Babu.Moger@amd.com>
>>
>> Spec says, when CUR_TEMP_TJ_SEL == 3 and CUR_TEMP_RANGE_SEL == 0,
>> it should use RangeUnadjusted is 0, which is (CurTmp*0.125 -49) C. The
>> CUR_TEMP register is read-write when CUR_TEMP_TJ_SEL == 3 (bit 17-16).
>>
>> Add the check to detect it.
>>
>> Sensors command's output before the patch.
>> $sensors
>>  k10temp-pci-00c3
>>  Adapter: PCI adapter
>>  Tctl:         +76.6°C <- Wrong value
>>  Tccd1:        +26.5°C
>>  Tccd2:        +27.5°C
>>  Tccd3:        +27.2°C
>>  Tccd4:        +27.5°C
>>  Tccd5:        +26.0°C
>>  Tccd6:        +26.2°C
>>  Tccd7:        +25.0°C
>>  Tccd8:        +26.5°C
>>
>> Sensors command's output after the patch.
>> $sensors
>>  k10temp-pci-00c3
>>  Adapter: PCI adapter
>>  Tctl:         +28.8°C <- corrected value
>>  Tccd1:        +27.5°C
>>  Tccd2:        +28.5°C
>>  Tccd3:        +28.5°C
>>  Tccd4:        +28.5°C
>>  Tccd5:        +27.0°C
>>  Tccd6:        +27.5°C
>>  Tccd7:        +27.0°C
>>  Tccd8:        +27.5°C
>>
>> Signed-off-by: Babu Moger <babu.moger@amd.com>
> 
> Applied. Please update your e-mail address configuration to avoid the
> following checkpatch message.
Thank you.

> 
> CHECK: From:/Signed-off-by: email comments mismatch: 'From: Babu Moger <Babu.Moger@amd.com>' != 'Signed-off-by: Babu Moger <babu.moger@amd.com>'

Sure. Will update.

> 
> Thanks,
> Guenter

-- 
Thanks
Babu Moger

      reply	other threads:[~2023-04-17 14:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-13 21:39 Babu Moger
2023-04-16 14:35 ` Guenter Roeck
2023-04-17 14:00   ` Moger, Babu [this message]

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=6b712dd2-a884-e0ac-bfa4-3b6f8716ce90@amd.com \
    --to=babu.moger@amd.com \
    --cc=Baski.Kannan@amd.com \
    --cc=clemens@ladisch.de \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=yannick.hemery@corp.ovh.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

all inboxes | Powered by JetHome®