From: "Cai, Crane" <crane.cai@amd.com>
To: ykzhao <yakui.zhao@intel.com>
Cc: Crane Cai <crane.cai@amd.com>,
"lenb@kernel.org" <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI: add driver for SMBus Control Method Interface
Date: Thu, 16 Jul 2009 09:23:10 +0800 [thread overview]
Message-ID: <20090716012310.GA5806@crane-desktop> (raw)
In-Reply-To: <1247651002.4113.9.camel@localhost.localdomain>
On Wed, Jul 15, 2009 at 05:43:22PM +0800, ykzhao wrote:
> On Wed, 2009-07-15 at 14:02 +0800, Crane Cai wrote:
>> This driver supports the SMBus Control Method Interface. It needs BIOS declare
>> ACPI control methods via SMBus Control Method Interface Spec.
> It seems that SM bus control is realized in BIOS. And OS can use the
> given control method interface to access it.
> Will this controller be accessed directly directly BIOS?
Controller accessed by ACPI control method, the control method is called by OS.
> If it can be accessed by BIOS, how to resolve the conflict between BIOS
> and OS?
About conflicts see next question's answer.
>
> In fact we see the conflict on some boxes. The SMbus controller will be
> accessed by BIOS. If the corresponding driver is loaded for the SMBUS
> controller, there exists the potential risk. In such case we will hide
> the SMbus controller or not load the device driver for it.
About conflicts,
CMI driver access SMBus host controller via ACPI control methods. Its related
resource will be declared in ACPI region. Its controll methods will be insured
by BIOS.
Native PCI interface SMBus host controller driver such as i2c-piix4.c, its
resource is in PCI region. Its access methods is in its driver.
So, CMI driver & native PCI interface driver use different resouces and methods
to access SMBus host controller. 2 different devices controlled by 2 different
drivers and no conflicts exists.
>
> Thanks.
--
Best Regards,
- Crane
next prev parent reply other threads:[~2009-07-16 1:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 6:02 [PATCH] ACPI: add driver for SMBus Control Method Interface Crane Cai
2009-07-15 9:43 ` ykzhao
2009-07-15 14:00 ` Matthew Garrett
2009-07-16 0:46 ` ykzhao
2009-07-16 1:05 ` Matthew Garrett
2009-07-16 1:23 ` Cai, Crane [this message]
2009-07-27 3:05 ` Cai, Crane
2009-07-27 12:10 ` Matthew Garrett
2009-07-27 23:45 ` Cai, Crane
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=20090716012310.GA5806@crane-desktop \
--to=crane.cai@amd.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).