public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Carlos Corbacho <carlos@strangeworlds.co.uk>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Shaohua Li <shaohua.li@intel.com>,
	Mike Houston <mikeserv@bmts.com>, Adrian Bunk <bunk@stusta.de>,
	Elvis Pranskevichus <el@prans.net>,
	mhoffman@lightlink.com, linux-kernel@vger.kernel.org,
	lm-sensors@lm-sensors.org, Adam Belay <ambx1@neo.rr.com>,
	Zhao Yakui <yakui.zhao@intel.com>,
	Thomas Renninger <trenn@suse.de>,
	lenb@kernel.org, linux-acpi@vger.kernel.org
Subject: Re: 2.6.24-rc4 hwmon it87 probe fails
Date: Sat, 12 Jan 2008 10:56:58 +0100	[thread overview]
Message-ID: <20080112105658.6fb3995f@hyperion.delvare> (raw)
In-Reply-To: <4769C0E2.4000500@shaw.ca>

Hi Robert,

On Wed, 19 Dec 2007 19:09:54 -0600, Robert Hancock wrote:
> It's quite possible that the BIOS accesses the device either from ACPI 
> AML or possibly even from SMI. In that case it would be quite reasonable 
> for the BIOS to reserve that region to prevent another driver from 
> loading and trying to take conflicting control of the device. One has to 
> be careful before assuming that any such reservation is bogus.

Again I am all for honoring such BIOS requests so as to prevent
conflicts between ACPI or SMI and native drivers. The problem is that
no two BIOS out there do the same in this respect. I couldn't see any
correlation between machines declaring their hwmon device in PNP and
machines where ACPI or SMI access the device in question. Many boards
declare their device and seemingly never touch it so it's fine for
Linux to drive them. Some boards no not declare the devices but still
access them in our back.

Thomas' patches should deal with the ACPI AML case in most cases, but
not with SMI.

So either the PNP code in Linux isn't exporting enough details to
differentiate, or even the PNP code has no way to tell these cases
apart. In the latter case there's not much we can do. In the former
case, let's have the PNP code export the information so that hwmon
drivers can decide whether they should bind to the devices or not by
default.

-- 
Jean Delvare

  reply	other threads:[~2008-01-12  9:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.QPUBl9Xd2PDsImgWn6hbR+ShV1U@ifi.uio.no>
     [not found] ` <fa.ri5Klmu4+MwjYC8x5nSms+xKXfI@ifi.uio.no>
     [not found]   ` <fa.B/J+j9kGGZ1+gW9FrfHky+cj0Eo@ifi.uio.no>
     [not found]     ` <fa.Xv3BmMxnCGLOeEijySte5mKDO5k@ifi.uio.no>
2007-12-20  1:09       ` [lm-sensors] 2.6.24-rc4 hwmon it87 probe fails Robert Hancock
2008-01-12  9:56         ` Jean Delvare [this message]
2007-12-21 19:00 Bjorn Helgaas
2007-12-22 11:21 ` Jean Delvare
  -- strict thread matches above, loose matches on Subject: below --
2007-12-23 23:14 [lm-sensors] " Bjorn Helgaas
2007-12-25 21:31 ` Jean Delvare
2008-01-02 18:30   ` Bjorn Helgaas
2008-01-12  9:49     ` 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=20080112105658.6fb3995f@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=ambx1@neo.rr.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=bunk@stusta.de \
    --cc=carlos@strangeworlds.co.uk \
    --cc=el@prans.net \
    --cc=hancockr@shaw.ca \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=mhoffman@lightlink.com \
    --cc=mikeserv@bmts.com \
    --cc=shaohua.li@intel.com \
    --cc=trenn@suse.de \
    --cc=yakui.zhao@intel.com \
    /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