Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
linux
Commits
4b63bd35
Commit
4b63bd35
authored
Jan 12, 2011
by
Len Brown
Browse files
Options
Browse Files
Download
Plain Diff
Merge branch 'ipmi' into release
parents
03b6e6e5
e92b297c
Changes
8
Expand all
Show whitespace changes
Inline
Side-by-side
Showing
8 changed files
with
653 additions
and
4 deletions
+653
-4
Documentation/IPMI.txt
Documentation/IPMI.txt
+27
-0
drivers/acpi/Kconfig
drivers/acpi/Kconfig
+11
-0
drivers/acpi/Makefile
drivers/acpi/Makefile
+1
-0
drivers/acpi/acpi_ipmi.c
drivers/acpi/acpi_ipmi.c
+525
-0
drivers/char/ipmi/ipmi_msghandler.c
drivers/char/ipmi/ipmi_msghandler.c
+27
-0
drivers/char/ipmi/ipmi_si_intf.c
drivers/char/ipmi/ipmi_si_intf.c
+16
-4
include/linux/ipmi.h
include/linux/ipmi.h
+38
-0
include/linux/ipmi_smi.h
include/linux/ipmi_smi.h
+8
-0
No files found.
Documentation/IPMI.txt
View file @
4b63bd35
...
...
@@ -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
--------
...
...
drivers/acpi/Kconfig
View file @
4b63bd35
...
...
@@ -207,6 +207,17 @@ config ACPI_PROCESSOR
To compile this driver as a module, choose M here:
the module will be called processor.
config ACPI_IPMI
tristate "IPMI"
depends on EXPERIMENTAL && IPMI_SI && IPMI_HANDLER
default n
help
This driver enables the ACPI to access the BMC controller. And it
uses the IPMI request/response message to communicate with BMC
controller, which can be found on on the server.
To compile this driver as a module, choose M here:
the module will be called as acpi_ipmi.
config ACPI_HOTPLUG_CPU
bool
...
...
drivers/acpi/Makefile
View file @
4b63bd35
...
...
@@ -69,5 +69,6 @@ processor-y += processor_idle.o processor_thermal.o
processor-$(CONFIG_CPU_FREQ)
+=
processor_perflib.o
obj-$(CONFIG_ACPI_PROCESSOR_AGGREGATOR)
+=
acpi_pad.o
obj-$(CONFIG_ACPI_IPMI)
+=
acpi_ipmi.o
obj-$(CONFIG_ACPI_APEI)
+=
apei/
drivers/acpi/acpi_ipmi.c
0 → 100644
View file @
4b63bd35
This diff is collapsed.
Click to expand it.
drivers/char/ipmi/ipmi_msghandler.c
View file @
4b63bd35
...
...
@@ -970,6 +970,33 @@ int ipmi_create_user(unsigned int if_num,
}
EXPORT_SYMBOL
(
ipmi_create_user
);
int
ipmi_get_smi_info
(
int
if_num
,
struct
ipmi_smi_info
*
data
)
{
int
rv
=
0
;
ipmi_smi_t
intf
;
struct
ipmi_smi_handlers
*
handlers
;
mutex_lock
(
&
ipmi_interfaces_mutex
);
list_for_each_entry_rcu
(
intf
,
&
ipmi_interfaces
,
link
)
{
if
(
intf
->
intf_num
==
if_num
)
goto
found
;
}
/* Not found, return an error */
rv
=
-
EINVAL
;
mutex_unlock
(
&
ipmi_interfaces_mutex
);
return
rv
;
found:
handlers
=
intf
->
handlers
;
rv
=
-
ENOSYS
;
if
(
handlers
->
get_smi_info
)
rv
=
handlers
->
get_smi_info
(
intf
->
send_info
,
data
);
mutex_unlock
(
&
ipmi_interfaces_mutex
);
return
rv
;
}
EXPORT_SYMBOL
(
ipmi_get_smi_info
);
static
void
free_user
(
struct
kref
*
ref
)
{
ipmi_user_t
user
=
container_of
(
ref
,
struct
ipmi_user
,
refcount
);
...
...
drivers/char/ipmi/ipmi_si_intf.c
View file @
4b63bd35
...
...
@@ -57,6 +57,7 @@
#include <asm/irq.h>
#include <linux/interrupt.h>
#include <linux/rcupdate.h>
#include <linux/ipmi.h>
#include <linux/ipmi_smi.h>
#include <asm/io.h>
#include "ipmi_si_sm.h"
...
...
@@ -107,10 +108,6 @@ enum si_type {
};
static
char
*
si_to_str
[]
=
{
"kcs"
,
"smic"
,
"bt"
};
enum
ipmi_addr_src
{
SI_INVALID
=
0
,
SI_HOTMOD
,
SI_HARDCODED
,
SI_SPMI
,
SI_ACPI
,
SI_SMBIOS
,
SI_PCI
,
SI_DEVICETREE
,
SI_DEFAULT
};
static
char
*
ipmi_addr_src_to_str
[]
=
{
NULL
,
"hotmod"
,
"hardcoded"
,
"SPMI"
,
"ACPI"
,
"SMBIOS"
,
"PCI"
,
"device-tree"
,
"default"
};
...
...
@@ -291,6 +288,7 @@ struct smi_info {
struct
task_struct
*
thread
;
struct
list_head
link
;
union
ipmi_smi_info_union
addr_info
;
};
#define smi_inc_stat(smi, stat) \
...
...
@@ -1186,6 +1184,18 @@ static int smi_start_processing(void *send_info,
return
0
;
}
static
int
get_smi_info
(
void
*
send_info
,
struct
ipmi_smi_info
*
data
)
{
struct
smi_info
*
smi
=
send_info
;
data
->
addr_src
=
smi
->
addr_source
;
data
->
dev
=
smi
->
dev
;
data
->
addr_info
=
smi
->
addr_info
;
get_device
(
smi
->
dev
);
return
0
;
}
static
void
set_maintenance_mode
(
void
*
send_info
,
int
enable
)
{
struct
smi_info
*
smi_info
=
send_info
;
...
...
@@ -1197,6 +1207,7 @@ static void set_maintenance_mode(void *send_info, int enable)
static
struct
ipmi_smi_handlers
handlers
=
{
.
owner
=
THIS_MODULE
,
.
start_processing
=
smi_start_processing
,
.
get_smi_info
=
get_smi_info
,
.
sender
=
sender
,
.
request_events
=
request_events
,
.
set_maintenance_mode
=
set_maintenance_mode
,
...
...
@@ -2157,6 +2168,7 @@ static int __devinit ipmi_pnp_probe(struct pnp_dev *dev,
printk
(
KERN_INFO
PFX
"probing via ACPI
\n
"
);
handle
=
acpi_dev
->
handle
;
info
->
addr_info
.
acpi_info
.
acpi_handle
=
handle
;
/* _IFT tells us the interface type: KCS, BT, etc */
status
=
acpi_evaluate_integer
(
handle
,
"_IFT"
,
NULL
,
&
tmp
);
...
...
include/linux/ipmi.h
View file @
4b63bd35
...
...
@@ -454,6 +454,44 @@ unsigned int ipmi_addr_length(int addr_type);
/* Validate that the given IPMI address is valid. */
int
ipmi_validate_addr
(
struct
ipmi_addr
*
addr
,
int
len
);
/*
* How did the IPMI driver find out about the device?
*/
enum
ipmi_addr_src
{
SI_INVALID
=
0
,
SI_HOTMOD
,
SI_HARDCODED
,
SI_SPMI
,
SI_ACPI
,
SI_SMBIOS
,
SI_PCI
,
SI_DEVICETREE
,
SI_DEFAULT
};
union
ipmi_smi_info_union
{
/*
* the acpi_info element is defined for the SI_ACPI
* address type
*/
struct
{
void
*
acpi_handle
;
}
acpi_info
;
};
struct
ipmi_smi_info
{
enum
ipmi_addr_src
addr_src
;
/*
* Base device for the interface. Don't forget to put this when
* you are done.
*/
struct
device
*
dev
;
/*
* The addr_info provides more detailed info for some IPMI
* devices, depending on the addr_src. Currently only SI_ACPI
* info is provided.
*/
union
ipmi_smi_info_union
addr_info
;
};
/* This is to get the private info of ipmi_smi_t */
extern
int
ipmi_get_smi_info
(
int
if_num
,
struct
ipmi_smi_info
*
data
);
#endif
/* __KERNEL__ */
...
...
include/linux/ipmi_smi.h
View file @
4b63bd35
...
...
@@ -39,6 +39,7 @@
#include <linux/module.h>
#include <linux/device.h>
#include <linux/platform_device.h>
#include <linux/ipmi.h>
/* This files describes the interface for IPMI system management interface
drivers to bind into the IPMI message handler. */
...
...
@@ -86,6 +87,13 @@ struct ipmi_smi_handlers {
int
(
*
start_processing
)(
void
*
send_info
,
ipmi_smi_t
new_intf
);
/*
* Get the detailed private info of the low level interface and store
* it into the structure of ipmi_smi_data. For example: the
* ACPI device handle will be returned for the pnp_acpi IPMI device.
*/
int
(
*
get_smi_info
)(
void
*
send_info
,
struct
ipmi_smi_info
*
data
);
/* Called to enqueue an SMI message to be sent. This
operation is not allowed to fail. If an error occurs, it
should report back the error in a received message. It may
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment