All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: ykzhao <yakui.zhao@intel.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"openipmi-developer@lists.sourceforge.net"
	<openipmi-developer@lists.sourceforge.net>,
	"lenb@kernel.org" <lenb@kernel.org>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: [PATCH_v8 1/2] IPMI/ACPI: Define acpi_ipmi notifier hook functions
Date: Tue, 27 Jul 2010 22:30:53 -0500	[thread overview]
Message-ID: <4C4FA46D.1090402@acm.org> (raw)
In-Reply-To: <1280279356.13929.139.camel@localhost.localdomain>

On 07/27/2010 08:09 PM, ykzhao wrote:
>
>> I agree that a notifier framework seems like massive overkill for this
>> interface.  I will note that there are already interfaces for
>> registering to receive callbacks when an IPMI device is added or
>> removed.  What's missing is a way to ask "Is this an ACPI PNP device?".
>>      
> Not sure whether the ipmi_smi_watcher is the interfaces you mentioned?
>
> The ipmi_smi_watcher is already used in the second patch in order to
> create the user interface. But now the callback function of new_smi only
> provides very limited info about the IPMI device. In order to assure
> that ACPI can communicate with the IPMI device, I have to compare the
> corresponding device pointer to confirm whether this is what ACPI want
> to communicate. Then I tried the several mechanisms to make it work
> while touch IPMI code/structure as little as possible.
>       >manually discover the pnp device with the pnpid of "IPI0001"
>       >using one notifier in course of loading IPMI pnp device driver.
>       >Merge the opregion code into the PNP IPMI discovery code.
>    
Yes ipmi_smi_watcher is the interface, and you obviously have to use 
that to catch the interfaces as the come and go.

>
>    
>> Since this same function will be needed for IPMI SMBus interfaces, if
>> that ever becomes a reality in the kernel, it seems more reasonable to
>> provide some type of addition to the IPMI interface to be able to store
>> this in the low-level code and retrieve this from the IPMI user
>> interface.  So you can use the standard mechanisms to watch for devices
>> being added, and then query to see if they are PNP at that point.
>>
>> Does that make sense?
>>      
> Yes. If this interface can be available, it will be easier for me to
> write the patch to enable that the ACPI can communicate with the BMC.
>    
I was actually hoping you would provide that interface :).  I'm not sure 
exactly what you need, but it's not that hard, really.  A new function 
in ipmi.h and ipmi_msghandler.c which calls a new function pointer in 
struct ipmi_smi_handlers (in ipmi_smi.h).  ipmi_si.c would tie into that 
new function pointer, and I believe all the data is already available there.

-corey

------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share 
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/

      reply	other threads:[~2010-07-28  3:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 14:46 [PATCH -v8 0/2] IPMI/ACPI: Install the ACPI IPMI opregion yakui.zhao
2010-07-26 14:46 ` [PATCH_v8 1/2] IPMI/ACPI: Define acpi_ipmi notifier hook functions yakui.zhao
2010-07-26 14:46   ` [PATCH_v8 2/2] ACPI: Add the IPMI opregion driver to enable ACPI to access BMC controller yakui.zhao
2010-07-26 16:54     ` Bjorn Helgaas
2010-07-27  0:53       ` ykzhao
2010-07-26 15:11   ` [PATCH_v8 1/2] IPMI/ACPI: Define acpi_ipmi notifier hook functions Matthew Garrett
2010-07-26 15:15   ` Matthew Garrett
2010-07-26 16:52   ` Bjorn Helgaas
2010-07-27  0:35     ` ykzhao
2010-07-27  1:19     ` Corey Minyard
2010-07-27 13:22       ` Matthew Garrett
2010-07-27 14:04         ` Corey Minyard
2010-07-28  1:09       ` ykzhao
2010-07-28  3:30         ` Corey Minyard [this message]

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=4C4FA46D.1090402@acm.org \
    --to=minyard@acm.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=openipmi-developer@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.