4 * MontaVista IPMI interface
6 * Author: MontaVista Software, Inc.
7 * Corey Minyard <minyard@mvista.com>
10 * Copyright 2002 MontaVista Software Inc.
12 * This program is free software; you can redistribute it and/or modify it
13 * under the terms of the GNU General Public License as published by the
14 * Free Software Foundation; either version 2 of the License, or (at your
15 * option) any later version.
18 * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED
19 * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
20 * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
21 * IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
22 * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
23 * BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
24 * OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
25 * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
26 * TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
27 * USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
29 * You should have received a copy of the GNU General Public License along
30 * with this program; if not, write to the Free Software Foundation, Inc.,
31 * 675 Mass Ave, Cambridge, MA 02139, USA.
34 #ifndef __LINUX_IPMI_H
35 #define __LINUX_IPMI_H
37 #include <linux/ipmi_msgdefs.h>
38 #include <linux/compiler.h>
41 * This file describes an interface to an IPMI driver. You have to
42 * have a fairly good understanding of IPMI to use this, so go read
43 * the specs first before actually trying to do anything.
45 * With that said, this driver provides a multi-user interface to the
46 * IPMI driver, and it allows multiple IPMI physical interfaces below
47 * the driver. The physical interfaces bind as a lower layer on the
48 * driver. They appear as interfaces to the application using this
51 * Multi-user means that multiple applications may use the driver,
52 * send commands, receive responses, etc. The driver keeps track of
53 * commands the user sends and tracks the responses. The responses
54 * will go back to the application that send the command. If the
55 * response doesn't come back in time, the driver will return a
56 * timeout error response to the application. Asynchronous events
57 * from the BMC event queue will go to all users bound to the driver.
58 * The incoming event queue in the BMC will automatically be flushed
59 * if it becomes full and it is queried once a second to see if
60 * anything is in it. Incoming commands to the driver will get
61 * delivered as commands.
63 * This driver provides two main interfaces: one for in-kernel
64 * applications and another for userland applications. The
65 * capabilities are basically the same for both interface, although
66 * the interfaces are somewhat different. The stuff in the
67 * #ifdef KERNEL below is the in-kernel interface. The userland
68 * interface is defined later in the file. */
73 * This is an overlay for all the address types, so it's easy to
74 * determine the actual address type. This is kind of like addresses
77 #define IPMI_MAX_ADDR_SIZE 32
80 /* Try to take these from the "Channel Medium Type" table
81 in section 6.5 of the IPMI 1.5 manual. */
84 char data[IPMI_MAX_ADDR_SIZE];
88 * When the address is not used, the type will be set to this value.
89 * The channel is the BMC's channel number for the channel (usually
90 * 0), or IPMC_BMC_CHANNEL if communicating directly with the BMC.
92 #define IPMI_SYSTEM_INTERFACE_ADDR_TYPE 0x0c
93 struct ipmi_system_interface_addr
100 /* An IPMB Address. */
101 #define IPMI_IPMB_ADDR_TYPE 0x01
102 /* Used for broadcast get device id as described in section 17.9 of the
104 #define IPMI_IPMB_BROADCAST_ADDR_TYPE 0x41
105 struct ipmi_ipmb_addr
109 unsigned char slave_addr;
114 * A LAN Address. This is an address to/from a LAN interface bridged
115 * by the BMC, not an address actually out on the LAN.
117 * A concious decision was made here to deviate slightly from the IPMI
118 * spec. We do not use rqSWID and rsSWID like it shows in the
119 * message. Instead, we use remote_SWID and local_SWID. This means
120 * that any message (a request or response) from another device will
121 * always have exactly the same address. If you didn't do this,
122 * requests and responses from the same device would have different
123 * addresses, and that's not too cool.
125 * In this address, the remote_SWID is always the SWID the remote
126 * message came from, or the SWID we are sending the message to.
127 * local_SWID is always our SWID. Note that having our SWID in the
128 * message is a little weird, but this is required.
130 #define IPMI_LAN_ADDR_TYPE 0x04
135 unsigned char privilege;
136 unsigned char session_handle;
137 unsigned char remote_SWID;
138 unsigned char local_SWID;
144 * Channel for talking directly with the BMC. When using this
145 * channel, This is for the system interface address type only. FIXME
146 * - is this right, or should we use -1?
148 #define IPMI_BMC_CHANNEL 0xf
149 #define IPMI_NUM_CHANNELS 0x10
153 * A raw IPMI message without any addressing. This covers both
154 * commands and responses. The completion code is always the first
155 * byte of data in the response (as the spec shows the messages laid
162 unsigned short data_len;
163 unsigned char __user *data;
166 struct kernel_ipmi_msg
170 unsigned short data_len;
175 * Various defines that are useful for IPMI applications.
177 #define IPMI_INVALID_CMD_COMPLETION_CODE 0xC1
178 #define IPMI_TIMEOUT_COMPLETION_CODE 0xC3
179 #define IPMI_UNKNOWN_ERR_COMPLETION_CODE 0xff
183 * Receive types for messages coming from the receive interface. This
184 * is used for the receive in-kernel interface and in the receive
187 * The "IPMI_RESPONSE_RESPNOSE_TYPE" is a little strange sounding, but
188 * it allows you to get the message results when you send a response
191 #define IPMI_RESPONSE_RECV_TYPE 1 /* A response to a command */
192 #define IPMI_ASYNC_EVENT_RECV_TYPE 2 /* Something from the event queue */
193 #define IPMI_CMD_RECV_TYPE 3 /* A command from somewhere else */
194 #define IPMI_RESPONSE_RESPONSE_TYPE 4 /* The response for
195 a sent response, giving any
196 error status for sending the
197 response. When you send a
198 response message, this will
200 /* Note that async events and received commands do not have a completion
201 code as the first byte of the incoming data, unlike a response. */
208 * The in-kernel interface.
210 #include <linux/list.h>
211 #include <linux/module.h>
213 #ifdef CONFIG_PROC_FS
214 #include <linux/proc_fs.h>
215 extern struct proc_dir_entry *proc_ipmi_root;
216 #endif /* CONFIG_PROC_FS */
218 /* Opaque type for a IPMI message user. One of these is needed to
219 send and receive messages. */
220 typedef struct ipmi_user *ipmi_user_t;
223 * Stuff coming from the receive interface comes as one of these.
224 * They are allocated, the receiver must free them with
225 * ipmi_free_recv_msg() when done with the message. The link is not
226 * used after the message is delivered, so the upper layer may use the
227 * link to build a linked list, if it likes.
231 struct list_head link;
233 /* The type of message as defined in the "Receive Types"
238 struct ipmi_addr addr;
240 struct kernel_ipmi_msg msg;
242 /* The user_msg_data is the data supplied when a message was
243 sent, if this is a response to a sent message. If this is
244 not a response to a sent message, then user_msg_data will
245 be NULL. If the user above is NULL, then this will be the
249 /* Call this when done with the message. It will presumably free
250 the message and do any other necessary cleanup. */
251 void (*done)(struct ipmi_recv_msg *msg);
253 /* Place-holder for the data, don't make any assumptions about
254 the size or existance of this, since it may change. */
255 unsigned char msg_data[IPMI_MAX_MSG_LENGTH];
258 /* Allocate and free the receive message. */
259 static inline void ipmi_free_recv_msg(struct ipmi_recv_msg *msg)
264 struct ipmi_user_hndl
266 /* Routine type to call when a message needs to be routed to
267 the upper layer. This will be called with some locks held,
268 the only IPMI routines that can be called are ipmi_request
269 and the alloc/free operations. The handler_data is the
270 variable supplied when the receive handler was registered. */
271 void (*ipmi_recv_hndl)(struct ipmi_recv_msg *msg,
272 void *user_msg_data);
274 /* Called when the interface detects a watchdog pre-timeout. If
275 this is NULL, it will be ignored for the user. */
276 void (*ipmi_watchdog_pretimeout)(void *handler_data);
279 /* Create a new user of the IPMI layer on the given interface number. */
280 int ipmi_create_user(unsigned int if_num,
281 struct ipmi_user_hndl *handler,
285 /* Destroy the given user of the IPMI layer. Note that after this
286 function returns, the system is guaranteed to not call any
287 callbacks for the user. Thus as long as you destroy all the users
288 before you unload a module, you will be safe. And if you destroy
289 the users before you destroy the callback structures, it should be
291 int ipmi_destroy_user(ipmi_user_t user);
293 /* Get the IPMI version of the BMC we are talking to. */
294 void ipmi_get_version(ipmi_user_t user,
295 unsigned char *major,
296 unsigned char *minor);
298 /* Set and get the slave address and LUN that we will use for our
299 source messages. Note that this affects the interface, not just
300 this user, so it will affect all users of this interface. This is
301 so some initialization code can come in and do the OEM-specific
302 things it takes to determine your address (if not the BMC) and set
303 it for everyone else. Note that each channel can have its own address. */
304 int ipmi_set_my_address(ipmi_user_t user,
305 unsigned int channel,
306 unsigned char address);
307 int ipmi_get_my_address(ipmi_user_t user,
308 unsigned int channel,
309 unsigned char *address);
310 int ipmi_set_my_LUN(ipmi_user_t user,
311 unsigned int channel,
313 int ipmi_get_my_LUN(ipmi_user_t user,
314 unsigned int channel,
318 * Like ipmi_request, but lets you specify the number of retries and
319 * the retry time. The retries is the number of times the message
320 * will be resent if no reply is received. If set to -1, the default
321 * value will be used. The retry time is the time in milliseconds
322 * between retries. If set to zero, the default value will be
325 * Don't use this unless you *really* have to. It's primarily for the
326 * IPMI over LAN converter; since the LAN stuff does its own retries,
327 * it makes no sense to do it here. However, this can be used if you
328 * have unusual requirements.
330 int ipmi_request_settime(ipmi_user_t user,
331 struct ipmi_addr *addr,
333 struct kernel_ipmi_msg *msg,
337 unsigned int retry_time_ms);
340 * Like ipmi_request, but with messages supplied. This will not
341 * allocate any memory, and the messages may be statically allocated
342 * (just make sure to do the "done" handling on them). Note that this
343 * is primarily for the watchdog timer, since it should be able to
344 * send messages even if no memory is available. This is subject to
345 * change as the system changes, so don't use it unless you REALLY
348 int ipmi_request_supply_msgs(ipmi_user_t user,
349 struct ipmi_addr *addr,
351 struct kernel_ipmi_msg *msg,
354 struct ipmi_recv_msg *supplied_recv,
358 * When commands come in to the SMS, the user can register to receive
359 * them. Only one user can be listening on a specific netfn/cmd pair
360 * at a time, you will get an EBUSY error if the command is already
361 * registered. If a command is received that does not have a user
362 * registered, the driver will automatically return the proper
365 int ipmi_register_for_cmd(ipmi_user_t user,
368 int ipmi_unregister_for_cmd(ipmi_user_t user,
373 * Allow run-to-completion mode to be set for the interface of
376 void ipmi_user_set_run_to_completion(ipmi_user_t user, int val);
379 * When the user is created, it will not receive IPMI events by
380 * default. The user must set this to TRUE to get incoming events.
381 * The first user that sets this to TRUE will receive all events that
382 * have been queued while no one was waiting for events.
384 int ipmi_set_gets_events(ipmi_user_t user, int val);
387 * Called when a new SMI is registered. This will also be called on
388 * every existing interface when a new watcher is registered with
389 * ipmi_smi_watcher_register().
391 struct ipmi_smi_watcher
393 struct list_head link;
395 /* You must set the owner to the current module, if you are in
396 a module (generally just set it to "THIS_MODULE"). */
397 struct module *owner;
399 /* These two are called with read locks held for the interface
400 the watcher list. So you can add and remove users from the
401 IPMI interface, send messages, etc., but you cannot add
402 or remove SMI watchers or SMI interfaces. */
403 void (*new_smi)(int if_num);
404 void (*smi_gone)(int if_num);
407 int ipmi_smi_watcher_register(struct ipmi_smi_watcher *watcher);
408 int ipmi_smi_watcher_unregister(struct ipmi_smi_watcher *watcher);
410 /* The following are various helper functions for dealing with IPMI
413 /* Return the maximum length of an IPMI address given it's type. */
414 unsigned int ipmi_addr_length(int addr_type);
416 /* Validate that the given IPMI address is valid. */
417 int ipmi_validate_addr(struct ipmi_addr *addr, int len);
419 #endif /* __KERNEL__ */
423 * The userland interface
427 * The userland interface for the IPMI driver is a standard character
428 * device, with each instance of an interface registered as a minor
429 * number under the major character device.
431 * The read and write calls do not work, to get messages in and out
432 * requires ioctl calls because of the complexity of the data. select
433 * and poll do work, so you can wait for input using the file
434 * descriptor, you just can use read to get it.
436 * In general, you send a command down to the interface and receive
437 * responses back. You can use the msgid value to correlate commands
438 * and responses, the driver will take care of figuring out which
439 * incoming messages are for which command and find the proper msgid
440 * value to report. You will only receive reponses for commands you
441 * send. Asynchronous events, however, go to all open users, so you
442 * must be ready to handle these (or ignore them if you don't care).
444 * The address type depends upon the channel type. When talking
445 * directly to the BMC (IPMC_BMC_CHANNEL), the address is ignored
446 * (IPMI_UNUSED_ADDR_TYPE). When talking to an IPMB channel, you must
447 * supply a valid IPMB address with the addr_type set properly.
449 * When talking to normal channels, the driver takes care of the
450 * details of formatting and sending messages on that channel. You do
451 * not, for instance, have to format a send command, you just send
452 * whatever command you want to the channel, the driver will create
453 * the send command, automatically issue receive command and get even
454 * commands, and pass those up to the proper user.
458 /* The magic IOCTL value for this interface. */
459 #define IPMI_IOC_MAGIC 'i'
462 /* Messages sent to the interface are this format. */
465 unsigned char __user *addr; /* Address to send the message to. */
466 unsigned int addr_len;
468 long msgid; /* The sequence number for the message. This
469 exact value will be reported back in the
470 response to this request if it is a command.
471 If it is a response, this will be used as
472 the sequence value for the response. */
477 * Send a message to the interfaces. error values are:
478 * - EFAULT - an address supplied was invalid.
479 * - EINVAL - The address supplied was not valid, or the command
481 * - EMSGSIZE - The message to was too large.
482 * - ENOMEM - Buffers could not be allocated for the command.
484 #define IPMICTL_SEND_COMMAND _IOR(IPMI_IOC_MAGIC, 13, \
487 /* Messages sent to the interface with timing parameters are this
489 struct ipmi_req_settime
493 /* See ipmi_request_settime() above for details on these
496 unsigned int retry_time_ms;
499 * Send a message to the interfaces with timing parameters. error values
501 * - EFAULT - an address supplied was invalid.
502 * - EINVAL - The address supplied was not valid, or the command
504 * - EMSGSIZE - The message to was too large.
505 * - ENOMEM - Buffers could not be allocated for the command.
507 #define IPMICTL_SEND_COMMAND_SETTIME _IOR(IPMI_IOC_MAGIC, 21, \
508 struct ipmi_req_settime)
510 /* Messages received from the interface are this format. */
513 int recv_type; /* Is this a command, response or an
514 asyncronous event. */
516 unsigned char __user *addr; /* Address the message was from is put
517 here. The caller must supply the
519 unsigned int addr_len; /* The size of the address buffer.
520 The caller supplies the full buffer
521 length, this value is updated to
522 the actual message length when the
523 message is received. */
525 long msgid; /* The sequence number specified in the request
526 if this is a response. If this is a command,
527 this will be the sequence number from the
530 struct ipmi_msg msg; /* The data field must point to a buffer.
531 The data_size field must be set to the
532 size of the message buffer. The
533 caller supplies the full buffer
534 length, this value is updated to the
535 actual message length when the message
540 * Receive a message. error values:
541 * - EAGAIN - no messages in the queue.
542 * - EFAULT - an address supplied was invalid.
543 * - EINVAL - The address supplied was not valid.
544 * - EMSGSIZE - The message to was too large to fit into the message buffer,
545 * the message will be left in the buffer. */
546 #define IPMICTL_RECEIVE_MSG _IOWR(IPMI_IOC_MAGIC, 12, \
550 * Like RECEIVE_MSG, but if the message won't fit in the buffer, it
551 * will truncate the contents instead of leaving the data in the
554 #define IPMICTL_RECEIVE_MSG_TRUNC _IOWR(IPMI_IOC_MAGIC, 11, \
557 /* Register to get commands from other entities on this interface. */
565 * Register to receive a specific command. error values:
566 * - EFAULT - an address supplied was invalid.
567 * - EBUSY - The netfn/cmd supplied was already in use.
568 * - ENOMEM - could not allocate memory for the entry.
570 #define IPMICTL_REGISTER_FOR_CMD _IOR(IPMI_IOC_MAGIC, 14, \
573 * Unregister a regsitered command. error values:
574 * - EFAULT - an address supplied was invalid.
575 * - ENOENT - The netfn/cmd was not found registered for this user.
577 #define IPMICTL_UNREGISTER_FOR_CMD _IOR(IPMI_IOC_MAGIC, 15, \
581 * Set whether this interface receives events. Note that the first
582 * user registered for events will get all pending events for the
583 * interface. error values:
584 * - EFAULT - an address supplied was invalid.
586 #define IPMICTL_SET_GETS_EVENTS_CMD _IOR(IPMI_IOC_MAGIC, 16, int)
589 * Set and get the slave address and LUN that we will use for our
590 * source messages. Note that this affects the interface, not just
591 * this user, so it will affect all users of this interface. This is
592 * so some initialization code can come in and do the OEM-specific
593 * things it takes to determine your address (if not the BMC) and set
594 * it for everyone else. You should probably leave the LUN alone.
596 struct ipmi_channel_lun_address_set
598 unsigned short channel;
601 #define IPMICTL_SET_MY_CHANNEL_ADDRESS_CMD _IOR(IPMI_IOC_MAGIC, 24, struct ipmi_channel_lun_address_set)
602 #define IPMICTL_GET_MY_CHANNEL_ADDRESS_CMD _IOR(IPMI_IOC_MAGIC, 25, struct ipmi_channel_lun_address_set)
603 #define IPMICTL_SET_MY_CHANNEL_LUN_CMD _IOR(IPMI_IOC_MAGIC, 26, struct ipmi_channel_lun_address_set)
604 #define IPMICTL_GET_MY_CHANNEL_LUN_CMD _IOR(IPMI_IOC_MAGIC, 27, struct ipmi_channel_lun_address_set)
605 /* Legacy interfaces, these only set IPMB 0. */
606 #define IPMICTL_SET_MY_ADDRESS_CMD _IOR(IPMI_IOC_MAGIC, 17, unsigned int)
607 #define IPMICTL_GET_MY_ADDRESS_CMD _IOR(IPMI_IOC_MAGIC, 18, unsigned int)
608 #define IPMICTL_SET_MY_LUN_CMD _IOR(IPMI_IOC_MAGIC, 19, unsigned int)
609 #define IPMICTL_GET_MY_LUN_CMD _IOR(IPMI_IOC_MAGIC, 20, unsigned int)
612 * Get/set the default timing values for an interface. You shouldn't
613 * generally mess with these.
615 struct ipmi_timing_parms
618 unsigned int retry_time_ms;
620 #define IPMICTL_SET_TIMING_PARMS_CMD _IOR(IPMI_IOC_MAGIC, 22, \
621 struct ipmi_timing_parms)
622 #define IPMICTL_GET_TIMING_PARMS_CMD _IOR(IPMI_IOC_MAGIC, 23, \
623 struct ipmi_timing_parms)
625 #endif /* __LINUX_IPMI_H */