From: Guenter Roeck <linux@roeck-us.net>
To: Stefan Dietrich <roots@gmx.de>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: hwmon (nct6775): Please fix Invalid temperature source error for NCT6798D
Date: Mon, 13 Jul 2020 22:18:39 -0700 [thread overview]
Message-ID: <2569643c-d050-1663-7da7-641211618aee@roeck-us.net> (raw)
In-Reply-To: <119b8c4d3791bafae015f1643b4fba9114d3eb65.camel@gmx.de>
On 7/13/20 10:40 AM, Stefan Dietrich wrote:
> On Sun, 2020-07-12 at 15:46 -0700, Guenter Roeck wrote:
>> On Sun, Jul 12, 2020 at 09:51:42AM +0200, Stefan Dietrich wrote:
>>> On Sun, 2020-07-05 at 07:21 -0700, Guenter Roeck wrote:
>> [ ... ]
>>> Would you mind giving me a pointer on how this would be done? I
>>> assume
>>> for those familiar with the driver it will be less than a handful
>>> of
>>> lines of code?!
>>> I will certainly report back as soon as I have obtained any
>>> results.
>>
>> Something like the diffs below should do. Caution - this is cut-and-
>> paste,
>> so you'll have to make the changes manually.
>>
>> Guenter
>>
>> ---
>> diff --git a/drivers/hwmon/nct6775.c b/drivers/hwmon/nct6775.c
>> index 7efa6bfef060..ec427ce503f0 100644
>> --- a/drivers/hwmon/nct6775.c
>> +++ b/drivers/hwmon/nct6775.c
>> @@ -786,9 +786,9 @@ static const char *const nct6798_temp_label[] = {
>> "Agent1 Dimm1",
>> "BYTE_TEMP0",
>> "BYTE_TEMP1",
>> - "",
>> - "",
>> - "",
>> + "Unknown28",
>> + "Unknown29",
>> + "Unknown30",
>> "Virtual_TEMP"
>> };
>
> Dankeschoen - I just tried that, but I'm still getting
>
> [ 324.901595] nct6775 nct6775.656: Invalid temperature source 28 at
> index 0, source register 0x100, temp register 0x73
> [ 324.901637] nct6775 nct6775.656: Invalid temperature source 28 at
> index 1, source register 0x200, temp register 0x75
> [ 324.901679] nct6775 nct6775.656: Invalid temperature source 28 at
> index 2, source register 0x300, temp register 0x77
> [ 324.901722] nct6775 nct6775.656: Invalid temperature source 28 at
> index 3, source register 0x800, temp register 0x79
> [ 324.901765] nct6775 nct6775.656: Invalid temperature source 28 at
> index 4, source register 0x900, temp register 0x7b
> [ 324.901807] nct6775 nct6775.656: Invalid temperature source 28 at
> index 5, source register 0xa00, temp register 0x7d
>
> I double checked that it really is the modified driver that is loaded.
> Now does that mean the diffs did not do the trick, or that there's
> really nothing to see here?
>
I forgot: Also change NCT6798_TEMP_MASK to 0xffff0ffe.
Guenter
next prev parent reply other threads:[~2020-07-14 5:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 16:03 hwmon (nct6775): Please fix Invalid temperature source error for NCT6798D Stefan Dietrich
2020-07-03 17:10 ` Guenter Roeck
2020-07-05 13:20 ` Stefan Dietrich
[not found] ` <48f415c34f4ca3f5239650711daaf1e11342da8e.camel@gmx.de>
[not found] ` <d54732db-255c-54be-ab43-997369e0da87@roeck-us.net>
2020-07-05 15:47 ` Stefan Dietrich
[not found] ` <e02ef4f8633e035ecf6019abb72e3a22bfc29732.camel@gmx.de>
[not found] ` <20200712224620.GA19097@roeck-us.net>
2020-07-13 17:40 ` Stefan Dietrich
2020-07-14 5:18 ` Guenter Roeck [this message]
2020-07-14 17:19 ` Stefan Dietrich
2020-07-14 21:29 ` Guenter Roeck
2020-07-14 23:17 Alexey Galakhov
2020-07-14 23:58 ` Guenter Roeck
2020-07-15 0:19 ` Alexey Galakhov
2020-07-15 2:33 ` Guenter Roeck
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=2569643c-d050-1663-7da7-641211618aee@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-hwmon@vger.kernel.org \
--cc=roots@gmx.de \
/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).