All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <guenter.roeck@ericsson.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Lack of fan sensor output after Ubuntu upgrade
Date: Mon, 13 Sep 2010 16:13:49 +0000	[thread overview]
Message-ID: <20100913161349.GB593@ericsson.com> (raw)
In-Reply-To: <201009101529.26294.larsivar@igesund.net>

On Mon, Sep 13, 2010 at 10:43:57AM -0400, Jean Delvare wrote:
> Hi Guenter,
> 
> On Mon, 13 Sep 2010 07:17:16 -0700, Guenter Roeck wrote:
> > On Mon, Sep 13, 2010 at 04:05:45AM -0400, Jean Delvare wrote:
> > > On Sun, 12 Sep 2010 12:32:13 -0700, Guenter Roeck wrote:
> > > > On Sat, Sep 11, 2010 at 05:03:31AM -0400, Jean Delvare wrote:
> > > > > BTW... A quick search reveals that several Dell XPS Studio laptops
> > > > > embed an ITE IT8512 infra-red receiver chip. Probably not a
> > > > > coincidence...
> > > > > 
> > > > You are right. IT8512E/F is a Super-IO chip from ITE, and it uses 0x8512 as chip ID.
> > > 
> > > How do you know for sure? Do you have a datasheet? Once we're sure we
> > > can identify the chip reliably, support should be added to
> > > sensors-detect.
> > > 
> > I was able to dig up a datasheet on the web, and checked the chip ID.
> > The datasheet is at http://www.docin.com/p-4432074.html. The site is in Chinese (?), 
> > and the datasheet is not in pdf but displayed with flash, so it is a bit cumbersome
> > to read.
> 
> Indeed not user-friendly, and quite possibly illegal.
> 
> > Chip ID is 0x8512 (registers 0x20 and 0x21), and chip version is 0x22 (register 0x22).
> > Not sure if the version is correct, as it matches the register address, but that is
> > what it says.
> > 
> > I agree, it would make sense to add it to sensors-detect. I looked through the code,
> > but wasn't entirely sure how to do that, since the NS chip IDs are all 8 bit.
> > Can I just add an entry for chip ID 0x8512 ?
> 
> Yes, this should work. The code automatically figures out if there are
> one or two device ID registers.
> 
> > Also, I don't know what to specify as logdev,
> > since the sensors are all accessed through an embedded 8032 controller. 
> 
> That's more of an issue. The point of listing a logical device is that
> logical devices can be disabled, so it's a convenient way to figure out
> whether the monitoring feature is used on a given system. If the
> "embedded 8032 controller" corresponds to one logical device then
> that's the one to test. If not, we may have to write custom code for
> this device.
> 
It looks like data is passed between 8031 and host using LDA 11h and/or 12h
(power management).  However, if those LDAs are active, it does not mean that
ADCs or fan control is active. The datasheet does not specify details of ADC
and fan control communication between host and 8031; that seems to be microcode
specific. Also, it looks like the 8031 code is system specific and not provided
by the chip vendor. So it might not even be possible to obtain ADC and fan control
status.

Or, of course, I might simply be missing something.

For sensors-detect, we could possibly tag ADC and fan control support to 
LDA 11h and/or 12h. Would that make sense ?

Guenter


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2010-09-13 16:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10 13:29 [lm-sensors] Lack of fan sensor output after Ubuntu upgrade Lars Ivar Igesund
2010-09-10 16:15 ` Guenter Roeck
2010-09-11  8:53 ` Jean Delvare
2010-09-11  9:03 ` Jean Delvare
2010-09-11 14:11 ` Guenter Roeck
2010-09-12 19:32 ` Guenter Roeck
2010-09-13  6:44 ` Lars Ivar Igesund
2010-09-13  8:05 ` Jean Delvare
2010-09-13 14:17 ` Guenter Roeck
2010-09-13 14:43 ` Jean Delvare
2010-09-13 16:13 ` Guenter Roeck [this message]
2010-09-13 17:02 ` Jean Delvare
2010-09-13 17:24 ` Guenter Roeck
2010-09-13 18: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=20100913161349.GB593@ericsson.com \
    --to=guenter.roeck@ericsson.com \
    --cc=lm-sensors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.