From: Luca Tettamanti <kronos.it@gmail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH] hwmon: Add driver for intel PCI thermal subsystem
Date: Fri, 11 Dec 2009 17:58:03 +0100 [thread overview]
Message-ID: <68676e00912110858i1cb8f7aclc8e7802840b6f84e@mail.gmail.com> (raw)
In-Reply-To: <20091211165004.GA2156@srcf.ucam.org>
On Fri, Dec 11, 2009 at 5:50 PM, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> On Fri, Dec 11, 2009 at 05:47:29PM +0100, Luca Tettamanti wrote:
>> Sorry, I think we're not understanding each other :)
>> Does the PCH samples the values directly from the probes? Or is it an
>> interface for the real monitoring chip (most likely the superio chip)?
>> In the latter case it might be possible to access directly the
>> monitoring hardware using another driver (e.g. w83627ehf, lm80, etc.),
>> thus racing against the PCI driver.
>> Did I make myself clear?
>
> I don't think there's any other chip. On systems using external chips,
> this PCI device will simply be disabled by the BIOS before the OS boots.
Ok, good.
The other potential issue is asus_atk0110 driver; ASUS boards have a
ACPI interface to the hwmon stuff.
Will check with my testers.
Luca
next prev parent reply other threads:[~2009-12-11 16:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 15:52 Matthew Garrett
2009-12-11 16:28 ` [lm-sensors] " Luca Tettamanti
2009-12-11 16:33 ` Matthew Garrett
2009-12-11 16:36 ` Luca Tettamanti
2009-12-11 16:38 ` Matthew Garrett
2009-12-11 16:47 ` Luca Tettamanti
2009-12-11 16:50 ` Matthew Garrett
2009-12-11 16:58 ` Luca Tettamanti [this message]
2009-12-11 23:58 ` Robert Hancock
2010-04-03 17:09 ` Matthew Garrett
2010-04-11 8:24 ` Jean Delvare
2010-04-15 1:27 ` Andrew Morton
2010-04-15 6:44 ` Jean Delvare
2010-04-11 11:24 ` [lm-sensors] " Jean Delvare
2010-05-18 9:06 ` Jean Delvare
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=68676e00912110858i1cb8f7aclc8e7802840b6f84e@mail.gmail.com \
--to=kronos.it@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mjg59@srcf.ucam.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
all inboxes | Powered by JetHome®