linux-hwmon.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Galakhov <agalakhov@gmail.com>
To: linux-hwmon@vger.kernel.org
Subject: Re: hwmon (nct6775): Please fix Invalid temperature source error for NCT6798D
Date: Wed, 15 Jul 2020 01:17:48 +0200	[thread overview]
Message-ID: <20200715011748.3507fc2b.agalakhov@gmail.com> (raw)

Hi,

I'm facing the same problem. I did some research on my machine.

On Fri, 2020-07-03 at 10:10 -0700, Guenter Roeck wrote:

> There is nothing much if anything we can do about that. The NCT6798D
> datasheet reports temperature source 28 as reserved. You could ask
> Asus for support, but their usual response is that they don't support
> Linux.

Looks like there are different versions of the datasheet. The one of
NCT6796D, Revision 0.6 states that 28 (0x1c or 11100) is "Select PECI
Agent 0 Calibration as CPUFAN monitoring source." This seems to be correct
since the fan in question is the CPU one and the value of "PECI Agent 0
Calibration" is actually very similar to the CPU temperature and rises
with CPU load.

Also, looking at the driver code I found no signs of reading so-called
"HM Read-Only Registers". They are described in section 9.481 of the
above datasheet. They are I/O ports (readable with `inb`) with their
base address located in configuration registers 0x64 and 0x65 of the
SuperIO. Some temperatures seem to be directly readable only through
these registers. Looks like the driver monitors all temperatures only
indirectly via switchable channels, is it true?

Regards,
Alexey
  

             reply	other threads:[~2020-07-14 23:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14 23:17 Alexey Galakhov [this message]
2020-07-14 23:58 ` hwmon (nct6775): Please fix Invalid temperature source error for NCT6798D Guenter Roeck
2020-07-15  0:19   ` Alexey Galakhov
2020-07-15  2:33     ` Guenter Roeck
  -- strict thread matches above, loose matches on Subject: below --
2020-07-03 16:03 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
2020-07-14 17:19               ` Stefan Dietrich
2020-07-14 21:29                 ` 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=20200715011748.3507fc2b.agalakhov@gmail.com \
    --to=agalakhov@gmail.com \
    --cc=linux-hwmon@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 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).