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 02:19:54 +0200	[thread overview]
Message-ID: <20200715021954.68a03582.agalakhov@gmail.com> (raw)
In-Reply-To: <d2769820-426c-bc4a-bcc2-2720fde4f5bc@roeck-us.net>

On Tue, 14 Jul 2020 16:58:29 -0700
Guenter Roeck <linux@roeck-us.net> wrote:

> On 7/14/20 4:17 PM, Alexey Galakhov wrote:
> > 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  
> 
> We are talking about NCT6798D here.

I have NCT6798D on my machine and I also double-checked the chip marking
on the motherboard. I just looked at the 96's datasheet (not found a
98's one). Even with 98 this configuration seems to be correct. Looks
like at least on some revisions of 98 it is not reserved and usable.
The fan in controlled correctly with this setting.

> I have no idea how to access the "HM Read-Only" registers. The datasheets
> are not exactly verbal about it.

I successfully accessed them. The access procedure is poorly described
but quite simple.

Each of these "HM Read-Only" registers is just a plain I/O port. Just
inb() reads them. Their addresses are sequential. The base address
(address of register 00) is configured similar to the main I/O address
(the one which is usually 0x295). Its MSB is in register 0x64 and its
LSB is in 0x65 of the SuperIO. Like that:

  superio_select(sioreg, NCT6775_LD_HWM);
  hm_ro_base = superio_inb(sioreg, 0x64) << 8;
  hm_ro_base |= superio_inb(sioreg, 0x65);

  // on my machine hm_ro_base == 0x800

  val = inb(hm_io_base + hm_reg);

Hope this helps.

Regards,

Alexey

  reply	other threads:[~2020-07-15  0:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14 23:17 hwmon (nct6775): Please fix Invalid temperature source error for NCT6798D Alexey Galakhov
2020-07-14 23:58 ` Guenter Roeck
2020-07-15  0:19   ` Alexey Galakhov [this message]
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=20200715021954.68a03582.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).