From patchwork Fri Oct 22 09:10:40 2010 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Zhao, Yakui" X-Patchwork-Id: 273541 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by demeter1.kernel.org (8.14.4/8.14.3) with ESMTP id o9M9Fi9U026153 for ; Fri, 22 Oct 2010 09:15:45 GMT Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753492Ab0JVJPo (ORCPT ); Fri, 22 Oct 2010 05:15:44 -0400 Received: from mga14.intel.com ([143.182.124.37]:27822 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753704Ab0JVJPo (ORCPT ); Fri, 22 Oct 2010 05:15:44 -0400 Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga102.ch.intel.com with ESMTP; 22 Oct 2010 02:15:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.58,222,1286175600"; d="scan'208";a="339186975" Received: from yakui_zhao.sh.intel.com (HELO localhost.localdomain) ([10.239.36.9]) by azsmga001.ch.intel.com with ESMTP; 22 Oct 2010 02:15:42 -0700 From: yakui.zhao@intel.com To: openipmi-developer@lists.sourceforge.net, linux-acpi@vger.kernel.org Cc: minyard@acm.org, lenb@kernel.org, Zhao Yakui Subject: [RFC PATCH 3/4] IPMI: Add the document description of ipmi_get_smi_info Date: Fri, 22 Oct 2010 17:10:40 +0800 Message-Id: <1287738641-11490-4-git-send-email-yakui.zhao@intel.com> X-Mailer: git-send-email 1.5.4.5 In-Reply-To: <1287738641-11490-3-git-send-email-yakui.zhao@intel.com> References: <1287738641-11490-1-git-send-email-yakui.zhao@intel.com> <1287738641-11490-2-git-send-email-yakui.zhao@intel.com> <1287738641-11490-3-git-send-email-yakui.zhao@intel.com> Sender: linux-acpi-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.3 (demeter1.kernel.org [140.211.167.41]); Fri, 22 Oct 2010 09:15:45 +0000 (UTC) diff --git a/Documentation/IPMI.txt b/Documentation/IPMI.txt index 69dd29e..0b8aecc 100644 --- a/Documentation/IPMI.txt +++ b/Documentation/IPMI.txt @@ -533,6 +533,43 @@ completion during sending a panic event. Other Pieces ------------ +Get the detailed info related with the IPMI device +-------- +The IPMI smi_watcher will be used to catch the IPMI interface as they come or go. +In order to communicate with the correct IPMI device, it should be confirmed + whether it is what we wanted especially on the system with multiple IPMI +devices. But the new_smi callback function of smi_watcher provides very +limited info(only the interface number and dev pointer) and there is no +detailed info about the low level interface. For example: which mechansim +registers the IPMI interface(ACPI, PCI, DMI and so on). + The function of ipmi_get_smi_info is added to get the +detailed info of IPMI device. The following is the struct definition of +ipmi_smi_info(Now only ACPI info is defined. If the info is required for +other IPMI device type, please add it) . + struct ipmi_smi_info{ + enum ipmi_addr_src addr_src; + struct device *dev; + union { + /* + * Now only SI_ACPI info is provided. If the info is required + * for other type, please add it + */ +#ifdef CONFIG_ACPI + struct { + void *acpi_handle; + } acpi_info; +#endif + } smi_info; +}; + + The following is the definition of ipmi_get_smi_info. + extern int ipmi_get_smi_info(int if_num, enum ipmi_addr_src type, + struct ipmi_smi_info **data); + It is noted that the returned smi_data is not the dynamically +allocated memory. It is only the pointer of the corresponding info stored +in IPMI device. In such case the caller don't try to free the corresponding +memory. + Watchdog --------