From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Zhao Yakui <yakui.zhao@intel.com>
Cc: Len Brown <lenb@kernel.org>, Peter Mahlknecht <mali100@gmx.net>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: ACPI reads wrong temperature
Date: Thu, 6 Nov 2008 09:11:26 +0000 [thread overview]
Message-ID: <20081106091126.GA25849@srcf.ucam.org> (raw)
In-Reply-To: <1225951972.3989.99.camel@yakui_zhao.sh.intel.com>
On Thu, Nov 06, 2008 at 02:12:52PM +0800, Zhao Yakui wrote:
> On your box after the i2c-i801 driver is loaded, the smbus controller
> will be used by the AML code and i2c-i801 driver. Unfortunately there is
> no synchronization between them. IMO this is the BIOS fault. The SMbus
> will be accessed by the two different modules. But it is exported by
> BIOS.
No, loading i2c-i801 is harmless. The breakage occurs when you attempt
to drive the smbus.
> So the better solution is that:
> a. SMBus is hidden in BIOS. In such case the Linux OS can't detect
> the SMbus controller . Of course it won't try to load the device driver
> for it.
> b. Linux OS won't load the device driver for it.
The solution is for users not to load smbus drivers unless they know for
certain that it's safe to do so, or alternatively for us to refuse to
load i2c drivers if they overlap with ACPI resource allocations.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-11-06 9:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 14:02 ACPI reads wrong temperature Peter Mahlknecht
2008-10-31 14:30 ` Matthew Garrett
2008-10-31 21:09 ` Peter Mahlknecht
2008-11-02 9:25 ` Matthew Garrett
2008-11-02 11:31 ` Peter Mahlknecht
2008-11-03 2:05 ` Zhao Yakui
2008-11-03 9:01 ` Peter Mahlknecht
2008-11-03 14:50 ` Zhao, Yakui
2008-11-03 14:57 ` Matthew Garrett
2008-11-03 17:47 ` Len Brown
2008-11-03 17:48 ` Matthew Garrett
2008-11-06 6:12 ` Zhao Yakui
2008-11-06 9:11 ` Matthew Garrett [this message]
2008-11-12 22:20 ` Thomas Renninger
2008-11-12 22:27 ` Matthew Garrett
2008-11-13 10:24 ` 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=20081106091126.GA25849@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mali100@gmx.net \
--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