diff options
author | Len Brown <len.brown@intel.com> | 2011-01-12 05:03:13 -0500 |
---|---|---|
committer | Len Brown <len.brown@intel.com> | 2011-01-12 05:03:13 -0500 |
commit | 4b63bd35eb4e7959b0f7be17634689d34311524b (patch) | |
tree | 2dad174e4ef8cbe5ef86541a8496b5f97dcf35d1 /Documentation | |
parent | 03b6e6e58d9dd5f3068288653810db3c15fde929 (diff) | |
parent | e92b297cc72ade7a58eaec7e01c906d856f8ab6e (diff) | |
download | linux-4b63bd35eb4e7959b0f7be17634689d34311524b.tar.gz linux-4b63bd35eb4e7959b0f7be17634689d34311524b.tar.bz2 linux-4b63bd35eb4e7959b0f7be17634689d34311524b.zip |
Merge branch 'ipmi' into release
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/IPMI.txt | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/Documentation/IPMI.txt b/Documentation/IPMI.txt index 69dd29ed824e..b2bea15137d2 100644 --- a/Documentation/IPMI.txt +++ b/Documentation/IPMI.txt @@ -533,6 +533,33 @@ completion during sending a panic event. Other Pieces ------------ +Get the detailed info related with the IPMI device +-------------------------------------------------- + +Some users need more detailed information about a device, like where +the address came from or the raw base device for the IPMI interface. +You can use the IPMI smi_watcher to catch the IPMI interfaces as they +come or go, and to grab the information, you can use the function +ipmi_get_smi_info(), which returns the following structure: + +struct ipmi_smi_info { + enum ipmi_addr_src addr_src; + struct device *dev; + union { + struct { + void *acpi_handle; + } acpi_info; + } addr_info; +}; + +Currently special info for only for SI_ACPI address sources is +returned. Others may be added as necessary. + +Note that the dev pointer is included in the above structure, and +assuming ipmi_smi_get_info returns success, you must call put_device +on the dev pointer. + + Watchdog -------- |