From: ykzhao <yakui.zhao@intel.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Corey Minyard <minyard@acm.org>, Bela Lubkin <blubkin@vmware.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
Myron Stowe <myron.stowe@hp.com>,
"openipmi-developer@lists.sourceforge.net"
<openipmi-developer@lists.sourceforge.net>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH v1 0/5] IPMI devices from ACPI namespace
Date: Wed, 18 Nov 2009 10:29:49 +0800 [thread overview]
Message-ID: <1258511389.3813.54.camel@localhost.localdomain> (raw)
In-Reply-To: <20091118000427.14214.14043.stgit@bob.kio>
On Wed, 2009-11-18 at 08:05 +0800, Bjorn Helgaas wrote:
> Here's a sample of how I think the ACPI namespace device detection should
> be done. I think this is almost functionally equivalent to your "Locate
> the IPMI system interface in ACPI namespace" patch.
>
> The difference I'm aware of is that your patch doesn't call acpi_register_gsi()
> for IRQs from the device _CRS, so I don't think those interrupts would work.
> (I can't test this because I don't have a box that reports an IRQ in _CRS.)
> PNPACPI takes care of this GSI registration for us.
>
> Patches 3 & 4 are not really related to the main point here, but I left
> them in because without 4, we'll report both SPMI and ACPI namespace
> devices as being from "ACPI".
Hi, Bjorn
Thanks for your work.
In this patch set the IPMI system interface will be detected by
using pnp device driver. In theory it is ok to detect the IPMI system
interface by using pnp device driver.
But we will have to consider the following two problems:
a. how to detect the IPMI system interface defined in ACPI table if
the pnp subsystem is disabled? For example: by adding the boot option of
"pnpacpi=off". Why does this need to depend on two subsystems(ACPI and
pnp)?
b. There exist several exceptions about the _CRS for the IPMI system
interface defined in ACPI table. Maybe there exist two IO/memory address
definition for the IPMI system interface and the memory type is declared
before IO type. In such case we can't know which should be selected.
At the same time in order to enable the communication between the ACPI
AML code and IPMI subsystem, too strict dependency is added.
In such case if the ACPI IPMI driver is not selected, the IPMI
subsystem can't be compiled correctly.
thanks.
Yakui
>
> ---
>
> Bjorn Helgaas (5):
> PNPACPI: save struct acpi_device, not just acpi_handle
> PNP: add interface to retrieve ACPI device from a PNPACPI device
> ipmi: remove unused PCI probe code
> ipmi: refer to table as "SPMI", not "ACPI"
> ipmi: add PNP discovery (ACPI namespace via PNPACPI)
>
>
> drivers/char/ipmi/ipmi_si_intf.c | 118 +++++++++++++++++++++++++++++++++++---
> drivers/pnp/pnpacpi/core.c | 19 ++++--
> drivers/pnp/pnpacpi/rsparser.c | 9 ++-
> include/linux/pnp.h | 13 ++++
> 4 files changed, 141 insertions(+), 18 deletions(-)
>
next prev parent reply other threads:[~2009-11-18 2:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 0:05 [PATCH v1 0/5] IPMI devices from ACPI namespace Bjorn Helgaas
2009-11-18 0:05 ` [PATCH v1 1/5] PNPACPI: save struct acpi_device, not just acpi_handle Bjorn Helgaas
2009-11-18 0:05 ` [PATCH v1 2/5] PNP: add interface to retrieve ACPI device from a PNPACPI device Bjorn Helgaas
2009-11-18 0:05 ` [PATCH v1 3/5] ipmi: remove unused PCI probe code Bjorn Helgaas
2009-12-01 23:18 ` [PATCH v1 3/5] ipmi: remove unused PCI probe coded Corey Minyard
2009-12-02 19:53 ` Bjorn Helgaas
2009-12-02 21:04 ` Bela Lubkin
2009-12-02 21:36 ` Corey Minyard
2009-12-02 21:42 ` Bjorn Helgaas
2009-12-16 20:53 ` Bjorn Helgaas
2009-12-02 21:34 ` Corey Minyard
2009-11-18 0:05 ` [PATCH v1 4/5] ipmi: refer to table as "SPMI", not "ACPI" Bjorn Helgaas
2009-11-18 0:05 ` [PATCH v1 5/5] ipmi: add PNP discovery (ACPI namespace via PNPACPI) Bjorn Helgaas
2009-11-27 7:50 ` ykzhao
2009-11-18 2:29 ` ykzhao [this message]
2009-11-18 16:29 ` [PATCH v1 0/5] IPMI devices from ACPI namespace Bjorn Helgaas
2009-12-01 21:40 ` Bjorn Helgaas
2009-12-11 6:29 ` Len Brown
2009-12-11 13:36 ` Corey Minyard
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=1258511389.3813.54.camel@localhost.localdomain \
--to=yakui.zhao@intel.com \
--cc=bjorn.helgaas@hp.com \
--cc=blubkin@vmware.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=minyard@acm.org \
--cc=myron.stowe@hp.com \
--cc=openipmi-developer@lists.sourceforge.net \
/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