ipmi.h 25 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704
  1. /*
  2. * ipmi.h
  3. *
  4. * MontaVista IPMI interface
  5. *
  6. * Author: MontaVista Software, Inc.
  7. * Corey Minyard <minyard@mvista.com>
  8. * source@mvista.com
  9. *
  10. * Copyright 2002 MontaVista Software Inc.
  11. *
  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.
  16. *
  17. *
  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.
  28. *
  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.
  32. */
  33. #ifndef __LINUX_IPMI_H
  34. #define __LINUX_IPMI_H
  35. #include <linux/ipmi_msgdefs.h>
  36. #include <linux/compiler.h>
  37. /*
  38. * This file describes an interface to an IPMI driver. You have to
  39. * have a fairly good understanding of IPMI to use this, so go read
  40. * the specs first before actually trying to do anything.
  41. *
  42. * With that said, this driver provides a multi-user interface to the
  43. * IPMI driver, and it allows multiple IPMI physical interfaces below
  44. * the driver. The physical interfaces bind as a lower layer on the
  45. * driver. They appear as interfaces to the application using this
  46. * interface.
  47. *
  48. * Multi-user means that multiple applications may use the driver,
  49. * send commands, receive responses, etc. The driver keeps track of
  50. * commands the user sends and tracks the responses. The responses
  51. * will go back to the application that send the command. If the
  52. * response doesn't come back in time, the driver will return a
  53. * timeout error response to the application. Asynchronous events
  54. * from the BMC event queue will go to all users bound to the driver.
  55. * The incoming event queue in the BMC will automatically be flushed
  56. * if it becomes full and it is queried once a second to see if
  57. * anything is in it. Incoming commands to the driver will get
  58. * delivered as commands.
  59. *
  60. * This driver provides two main interfaces: one for in-kernel
  61. * applications and another for userland applications. The
  62. * capabilities are basically the same for both interface, although
  63. * the interfaces are somewhat different. The stuff in the
  64. * #ifdef KERNEL below is the in-kernel interface. The userland
  65. * interface is defined later in the file. */
  66. /*
  67. * This is an overlay for all the address types, so it's easy to
  68. * determine the actual address type. This is kind of like addresses
  69. * work for sockets.
  70. */
  71. #define IPMI_MAX_ADDR_SIZE 32
  72. struct ipmi_addr
  73. {
  74. /* Try to take these from the "Channel Medium Type" table
  75. in section 6.5 of the IPMI 1.5 manual. */
  76. int addr_type;
  77. short channel;
  78. char data[IPMI_MAX_ADDR_SIZE];
  79. };
  80. /*
  81. * When the address is not used, the type will be set to this value.
  82. * The channel is the BMC's channel number for the channel (usually
  83. * 0), or IPMC_BMC_CHANNEL if communicating directly with the BMC.
  84. */
  85. #define IPMI_SYSTEM_INTERFACE_ADDR_TYPE 0x0c
  86. struct ipmi_system_interface_addr
  87. {
  88. int addr_type;
  89. short channel;
  90. unsigned char lun;
  91. };
  92. /* An IPMB Address. */
  93. #define IPMI_IPMB_ADDR_TYPE 0x01
  94. /* Used for broadcast get device id as described in section 17.9 of the
  95. IPMI 1.5 manual. */
  96. #define IPMI_IPMB_BROADCAST_ADDR_TYPE 0x41
  97. struct ipmi_ipmb_addr
  98. {
  99. int addr_type;
  100. short channel;
  101. unsigned char slave_addr;
  102. unsigned char lun;
  103. };
  104. /*
  105. * A LAN Address. This is an address to/from a LAN interface bridged
  106. * by the BMC, not an address actually out on the LAN.
  107. *
  108. * A concious decision was made here to deviate slightly from the IPMI
  109. * spec. We do not use rqSWID and rsSWID like it shows in the
  110. * message. Instead, we use remote_SWID and local_SWID. This means
  111. * that any message (a request or response) from another device will
  112. * always have exactly the same address. If you didn't do this,
  113. * requests and responses from the same device would have different
  114. * addresses, and that's not too cool.
  115. *
  116. * In this address, the remote_SWID is always the SWID the remote
  117. * message came from, or the SWID we are sending the message to.
  118. * local_SWID is always our SWID. Note that having our SWID in the
  119. * message is a little weird, but this is required.
  120. */
  121. #define IPMI_LAN_ADDR_TYPE 0x04
  122. struct ipmi_lan_addr
  123. {
  124. int addr_type;
  125. short channel;
  126. unsigned char privilege;
  127. unsigned char session_handle;
  128. unsigned char remote_SWID;
  129. unsigned char local_SWID;
  130. unsigned char lun;
  131. };
  132. /*
  133. * Channel for talking directly with the BMC. When using this
  134. * channel, This is for the system interface address type only. FIXME
  135. * - is this right, or should we use -1?
  136. */
  137. #define IPMI_BMC_CHANNEL 0xf
  138. #define IPMI_NUM_CHANNELS 0x10
  139. /*
  140. * Used to signify an "all channel" bitmask. This is more than the
  141. * actual number of channels because this is used in userland and
  142. * will cover us if the number of channels is extended.
  143. */
  144. #define IPMI_CHAN_ALL (~0)
  145. /*
  146. * A raw IPMI message without any addressing. This covers both
  147. * commands and responses. The completion code is always the first
  148. * byte of data in the response (as the spec shows the messages laid
  149. * out).
  150. */
  151. struct ipmi_msg
  152. {
  153. unsigned char netfn;
  154. unsigned char cmd;
  155. unsigned short data_len;
  156. unsigned char __user *data;
  157. };
  158. struct kernel_ipmi_msg
  159. {
  160. unsigned char netfn;
  161. unsigned char cmd;
  162. unsigned short data_len;
  163. unsigned char *data;
  164. };
  165. /*
  166. * Various defines that are useful for IPMI applications.
  167. */
  168. #define IPMI_INVALID_CMD_COMPLETION_CODE 0xC1
  169. #define IPMI_TIMEOUT_COMPLETION_CODE 0xC3
  170. #define IPMI_UNKNOWN_ERR_COMPLETION_CODE 0xff
  171. /*
  172. * Receive types for messages coming from the receive interface. This
  173. * is used for the receive in-kernel interface and in the receive
  174. * IOCTL.
  175. *
  176. * The "IPMI_RESPONSE_RESPNOSE_TYPE" is a little strange sounding, but
  177. * it allows you to get the message results when you send a response
  178. * message.
  179. */
  180. #define IPMI_RESPONSE_RECV_TYPE 1 /* A response to a command */
  181. #define IPMI_ASYNC_EVENT_RECV_TYPE 2 /* Something from the event queue */
  182. #define IPMI_CMD_RECV_TYPE 3 /* A command from somewhere else */
  183. #define IPMI_RESPONSE_RESPONSE_TYPE 4 /* The response for
  184. a sent response, giving any
  185. error status for sending the
  186. response. When you send a
  187. response message, this will
  188. be returned. */
  189. /* Note that async events and received commands do not have a completion
  190. code as the first byte of the incoming data, unlike a response. */
  191. /*
  192. * Modes for ipmi_set_maint_mode() and the userland IOCTL. The AUTO
  193. * setting is the default and means it will be set on certain
  194. * commands. Hard setting it on and off will override automatic
  195. * operation.
  196. */
  197. #define IPMI_MAINTENANCE_MODE_AUTO 0
  198. #define IPMI_MAINTENANCE_MODE_OFF 1
  199. #define IPMI_MAINTENANCE_MODE_ON 2
  200. #ifdef __KERNEL__
  201. /*
  202. * The in-kernel interface.
  203. */
  204. #include <linux/list.h>
  205. #include <linux/module.h>
  206. #include <linux/device.h>
  207. #include <linux/proc_fs.h>
  208. /* Opaque type for a IPMI message user. One of these is needed to
  209. send and receive messages. */
  210. typedef struct ipmi_user *ipmi_user_t;
  211. /*
  212. * Stuff coming from the receive interface comes as one of these.
  213. * They are allocated, the receiver must free them with
  214. * ipmi_free_recv_msg() when done with the message. The link is not
  215. * used after the message is delivered, so the upper layer may use the
  216. * link to build a linked list, if it likes.
  217. */
  218. struct ipmi_recv_msg
  219. {
  220. struct list_head link;
  221. /* The type of message as defined in the "Receive Types"
  222. defines above. */
  223. int recv_type;
  224. ipmi_user_t user;
  225. struct ipmi_addr addr;
  226. long msgid;
  227. struct kernel_ipmi_msg msg;
  228. /* The user_msg_data is the data supplied when a message was
  229. sent, if this is a response to a sent message. If this is
  230. not a response to a sent message, then user_msg_data will
  231. be NULL. If the user above is NULL, then this will be the
  232. intf. */
  233. void *user_msg_data;
  234. /* Call this when done with the message. It will presumably free
  235. the message and do any other necessary cleanup. */
  236. void (*done)(struct ipmi_recv_msg *msg);
  237. /* Place-holder for the data, don't make any assumptions about
  238. the size or existance of this, since it may change. */
  239. unsigned char msg_data[IPMI_MAX_MSG_LENGTH];
  240. };
  241. /* Allocate and free the receive message. */
  242. void ipmi_free_recv_msg(struct ipmi_recv_msg *msg);
  243. struct ipmi_user_hndl
  244. {
  245. /* Routine type to call when a message needs to be routed to
  246. the upper layer. This will be called with some locks held,
  247. the only IPMI routines that can be called are ipmi_request
  248. and the alloc/free operations. The handler_data is the
  249. variable supplied when the receive handler was registered. */
  250. void (*ipmi_recv_hndl)(struct ipmi_recv_msg *msg,
  251. void *user_msg_data);
  252. /* Called when the interface detects a watchdog pre-timeout. If
  253. this is NULL, it will be ignored for the user. */
  254. void (*ipmi_watchdog_pretimeout)(void *handler_data);
  255. };
  256. /* Create a new user of the IPMI layer on the given interface number. */
  257. int ipmi_create_user(unsigned int if_num,
  258. struct ipmi_user_hndl *handler,
  259. void *handler_data,
  260. ipmi_user_t *user);
  261. /* Destroy the given user of the IPMI layer. Note that after this
  262. function returns, the system is guaranteed to not call any
  263. callbacks for the user. Thus as long as you destroy all the users
  264. before you unload a module, you will be safe. And if you destroy
  265. the users before you destroy the callback structures, it should be
  266. safe, too. */
  267. int ipmi_destroy_user(ipmi_user_t user);
  268. /* Get the IPMI version of the BMC we are talking to. */
  269. void ipmi_get_version(ipmi_user_t user,
  270. unsigned char *major,
  271. unsigned char *minor);
  272. /* Set and get the slave address and LUN that we will use for our
  273. source messages. Note that this affects the interface, not just
  274. this user, so it will affect all users of this interface. This is
  275. so some initialization code can come in and do the OEM-specific
  276. things it takes to determine your address (if not the BMC) and set
  277. it for everyone else. Note that each channel can have its own address. */
  278. int ipmi_set_my_address(ipmi_user_t user,
  279. unsigned int channel,
  280. unsigned char address);
  281. int ipmi_get_my_address(ipmi_user_t user,
  282. unsigned int channel,
  283. unsigned char *address);
  284. int ipmi_set_my_LUN(ipmi_user_t user,
  285. unsigned int channel,
  286. unsigned char LUN);
  287. int ipmi_get_my_LUN(ipmi_user_t user,
  288. unsigned int channel,
  289. unsigned char *LUN);
  290. /*
  291. * Like ipmi_request, but lets you specify the number of retries and
  292. * the retry time. The retries is the number of times the message
  293. * will be resent if no reply is received. If set to -1, the default
  294. * value will be used. The retry time is the time in milliseconds
  295. * between retries. If set to zero, the default value will be
  296. * used.
  297. *
  298. * Don't use this unless you *really* have to. It's primarily for the
  299. * IPMI over LAN converter; since the LAN stuff does its own retries,
  300. * it makes no sense to do it here. However, this can be used if you
  301. * have unusual requirements.
  302. */
  303. int ipmi_request_settime(ipmi_user_t user,
  304. struct ipmi_addr *addr,
  305. long msgid,
  306. struct kernel_ipmi_msg *msg,
  307. void *user_msg_data,
  308. int priority,
  309. int max_retries,
  310. unsigned int retry_time_ms);
  311. /*
  312. * Like ipmi_request, but with messages supplied. This will not
  313. * allocate any memory, and the messages may be statically allocated
  314. * (just make sure to do the "done" handling on them). Note that this
  315. * is primarily for the watchdog timer, since it should be able to
  316. * send messages even if no memory is available. This is subject to
  317. * change as the system changes, so don't use it unless you REALLY
  318. * have to.
  319. */
  320. int ipmi_request_supply_msgs(ipmi_user_t user,
  321. struct ipmi_addr *addr,
  322. long msgid,
  323. struct kernel_ipmi_msg *msg,
  324. void *user_msg_data,
  325. void *supplied_smi,
  326. struct ipmi_recv_msg *supplied_recv,
  327. int priority);
  328. /*
  329. * When commands come in to the SMS, the user can register to receive
  330. * them. Only one user can be listening on a specific netfn/cmd/chan tuple
  331. * at a time, you will get an EBUSY error if the command is already
  332. * registered. If a command is received that does not have a user
  333. * registered, the driver will automatically return the proper
  334. * error. Channels are specified as a bitfield, use IPMI_CHAN_ALL to
  335. * mean all channels.
  336. */
  337. int ipmi_register_for_cmd(ipmi_user_t user,
  338. unsigned char netfn,
  339. unsigned char cmd,
  340. unsigned int chans);
  341. int ipmi_unregister_for_cmd(ipmi_user_t user,
  342. unsigned char netfn,
  343. unsigned char cmd,
  344. unsigned int chans);
  345. /*
  346. * Go into a mode where the driver will not autonomously attempt to do
  347. * things with the interface. It will still respond to attentions and
  348. * interrupts, and it will expect that commands will complete. It
  349. * will not automatcially check for flags, events, or things of that
  350. * nature.
  351. *
  352. * This is primarily used for firmware upgrades. The idea is that
  353. * when you go into firmware upgrade mode, you do this operation
  354. * and the driver will not attempt to do anything but what you tell
  355. * it or what the BMC asks for.
  356. *
  357. * Note that if you send a command that resets the BMC, the driver
  358. * will still expect a response from that command. So the BMC should
  359. * reset itself *after* the response is sent. Resetting before the
  360. * response is just silly.
  361. *
  362. * If in auto maintenance mode, the driver will automatically go into
  363. * maintenance mode for 30 seconds if it sees a cold reset, a warm
  364. * reset, or a firmware NetFN. This means that code that uses only
  365. * firmware NetFN commands to do upgrades will work automatically
  366. * without change, assuming it sends a message every 30 seconds or
  367. * less.
  368. *
  369. * See the IPMI_MAINTENANCE_MODE_xxx defines for what the mode means.
  370. */
  371. int ipmi_get_maintenance_mode(ipmi_user_t user);
  372. int ipmi_set_maintenance_mode(ipmi_user_t user, int mode);
  373. /*
  374. * Allow run-to-completion mode to be set for the interface of
  375. * a specific user.
  376. */
  377. void ipmi_user_set_run_to_completion(ipmi_user_t user, int val);
  378. /*
  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.
  383. */
  384. int ipmi_set_gets_events(ipmi_user_t user, int val);
  385. /*
  386. * Called when a new SMI is registered. This will also be called on
  387. * every existing interface when a new watcher is registered with
  388. * ipmi_smi_watcher_register().
  389. */
  390. struct ipmi_smi_watcher
  391. {
  392. struct list_head link;
  393. /* You must set the owner to the current module, if you are in
  394. a module (generally just set it to "THIS_MODULE"). */
  395. struct module *owner;
  396. /* These two are called with read locks held for the interface
  397. the watcher list. So you can add and remove users from the
  398. IPMI interface, send messages, etc., but you cannot add
  399. or remove SMI watchers or SMI interfaces. */
  400. void (*new_smi)(int if_num, struct device *dev);
  401. void (*smi_gone)(int if_num);
  402. };
  403. int ipmi_smi_watcher_register(struct ipmi_smi_watcher *watcher);
  404. int ipmi_smi_watcher_unregister(struct ipmi_smi_watcher *watcher);
  405. /* The following are various helper functions for dealing with IPMI
  406. addresses. */
  407. /* Return the maximum length of an IPMI address given it's type. */
  408. unsigned int ipmi_addr_length(int addr_type);
  409. /* Validate that the given IPMI address is valid. */
  410. int ipmi_validate_addr(struct ipmi_addr *addr, int len);
  411. #endif /* __KERNEL__ */
  412. /*
  413. * The userland interface
  414. */
  415. /*
  416. * The userland interface for the IPMI driver is a standard character
  417. * device, with each instance of an interface registered as a minor
  418. * number under the major character device.
  419. *
  420. * The read and write calls do not work, to get messages in and out
  421. * requires ioctl calls because of the complexity of the data. select
  422. * and poll do work, so you can wait for input using the file
  423. * descriptor, you just can use read to get it.
  424. *
  425. * In general, you send a command down to the interface and receive
  426. * responses back. You can use the msgid value to correlate commands
  427. * and responses, the driver will take care of figuring out which
  428. * incoming messages are for which command and find the proper msgid
  429. * value to report. You will only receive reponses for commands you
  430. * send. Asynchronous events, however, go to all open users, so you
  431. * must be ready to handle these (or ignore them if you don't care).
  432. *
  433. * The address type depends upon the channel type. When talking
  434. * directly to the BMC (IPMC_BMC_CHANNEL), the address is ignored
  435. * (IPMI_UNUSED_ADDR_TYPE). When talking to an IPMB channel, you must
  436. * supply a valid IPMB address with the addr_type set properly.
  437. *
  438. * When talking to normal channels, the driver takes care of the
  439. * details of formatting and sending messages on that channel. You do
  440. * not, for instance, have to format a send command, you just send
  441. * whatever command you want to the channel, the driver will create
  442. * the send command, automatically issue receive command and get even
  443. * commands, and pass those up to the proper user.
  444. */
  445. /* The magic IOCTL value for this interface. */
  446. #define IPMI_IOC_MAGIC 'i'
  447. /* Messages sent to the interface are this format. */
  448. struct ipmi_req
  449. {
  450. unsigned char __user *addr; /* Address to send the message to. */
  451. unsigned int addr_len;
  452. long msgid; /* The sequence number for the message. This
  453. exact value will be reported back in the
  454. response to this request if it is a command.
  455. If it is a response, this will be used as
  456. the sequence value for the response. */
  457. struct ipmi_msg msg;
  458. };
  459. /*
  460. * Send a message to the interfaces. error values are:
  461. * - EFAULT - an address supplied was invalid.
  462. * - EINVAL - The address supplied was not valid, or the command
  463. * was not allowed.
  464. * - EMSGSIZE - The message to was too large.
  465. * - ENOMEM - Buffers could not be allocated for the command.
  466. */
  467. #define IPMICTL_SEND_COMMAND _IOR(IPMI_IOC_MAGIC, 13, \
  468. struct ipmi_req)
  469. /* Messages sent to the interface with timing parameters are this
  470. format. */
  471. struct ipmi_req_settime
  472. {
  473. struct ipmi_req req;
  474. /* See ipmi_request_settime() above for details on these
  475. values. */
  476. int retries;
  477. unsigned int retry_time_ms;
  478. };
  479. /*
  480. * Send a message to the interfaces with timing parameters. error values
  481. * are:
  482. * - EFAULT - an address supplied was invalid.
  483. * - EINVAL - The address supplied was not valid, or the command
  484. * was not allowed.
  485. * - EMSGSIZE - The message to was too large.
  486. * - ENOMEM - Buffers could not be allocated for the command.
  487. */
  488. #define IPMICTL_SEND_COMMAND_SETTIME _IOR(IPMI_IOC_MAGIC, 21, \
  489. struct ipmi_req_settime)
  490. /* Messages received from the interface are this format. */
  491. struct ipmi_recv
  492. {
  493. int recv_type; /* Is this a command, response or an
  494. asyncronous event. */
  495. unsigned char __user *addr; /* Address the message was from is put
  496. here. The caller must supply the
  497. memory. */
  498. unsigned int addr_len; /* The size of the address buffer.
  499. The caller supplies the full buffer
  500. length, this value is updated to
  501. the actual message length when the
  502. message is received. */
  503. long msgid; /* The sequence number specified in the request
  504. if this is a response. If this is a command,
  505. this will be the sequence number from the
  506. command. */
  507. struct ipmi_msg msg; /* The data field must point to a buffer.
  508. The data_size field must be set to the
  509. size of the message buffer. The
  510. caller supplies the full buffer
  511. length, this value is updated to the
  512. actual message length when the message
  513. is received. */
  514. };
  515. /*
  516. * Receive a message. error values:
  517. * - EAGAIN - no messages in the queue.
  518. * - EFAULT - an address supplied was invalid.
  519. * - EINVAL - The address supplied was not valid.
  520. * - EMSGSIZE - The message to was too large to fit into the message buffer,
  521. * the message will be left in the buffer. */
  522. #define IPMICTL_RECEIVE_MSG _IOWR(IPMI_IOC_MAGIC, 12, \
  523. struct ipmi_recv)
  524. /*
  525. * Like RECEIVE_MSG, but if the message won't fit in the buffer, it
  526. * will truncate the contents instead of leaving the data in the
  527. * buffer.
  528. */
  529. #define IPMICTL_RECEIVE_MSG_TRUNC _IOWR(IPMI_IOC_MAGIC, 11, \
  530. struct ipmi_recv)
  531. /* Register to get commands from other entities on this interface. */
  532. struct ipmi_cmdspec
  533. {
  534. unsigned char netfn;
  535. unsigned char cmd;
  536. };
  537. /*
  538. * Register to receive a specific command. error values:
  539. * - EFAULT - an address supplied was invalid.
  540. * - EBUSY - The netfn/cmd supplied was already in use.
  541. * - ENOMEM - could not allocate memory for the entry.
  542. */
  543. #define IPMICTL_REGISTER_FOR_CMD _IOR(IPMI_IOC_MAGIC, 14, \
  544. struct ipmi_cmdspec)
  545. /*
  546. * Unregister a regsitered command. error values:
  547. * - EFAULT - an address supplied was invalid.
  548. * - ENOENT - The netfn/cmd was not found registered for this user.
  549. */
  550. #define IPMICTL_UNREGISTER_FOR_CMD _IOR(IPMI_IOC_MAGIC, 15, \
  551. struct ipmi_cmdspec)
  552. /*
  553. * Register to get commands from other entities on specific channels.
  554. * This way, you can only listen on specific channels, or have messages
  555. * from some channels go to one place and other channels to someplace
  556. * else. The chans field is a bitmask, (1 << channel) for each channel.
  557. * It may be IPMI_CHAN_ALL for all channels.
  558. */
  559. struct ipmi_cmdspec_chans
  560. {
  561. unsigned int netfn;
  562. unsigned int cmd;
  563. unsigned int chans;
  564. };
  565. /*
  566. * Register to receive a specific command on specific channels. error values:
  567. * - EFAULT - an address supplied was invalid.
  568. * - EBUSY - One of the netfn/cmd/chans supplied was already in use.
  569. * - ENOMEM - could not allocate memory for the entry.
  570. */
  571. #define IPMICTL_REGISTER_FOR_CMD_CHANS _IOR(IPMI_IOC_MAGIC, 28, \
  572. struct ipmi_cmdspec_chans)
  573. /*
  574. * Unregister some netfn/cmd/chans. error values:
  575. * - EFAULT - an address supplied was invalid.
  576. * - ENOENT - None of the netfn/cmd/chans were found registered for this user.
  577. */
  578. #define IPMICTL_UNREGISTER_FOR_CMD_CHANS _IOR(IPMI_IOC_MAGIC, 29, \
  579. struct ipmi_cmdspec_chans)
  580. /*
  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.
  585. */
  586. #define IPMICTL_SET_GETS_EVENTS_CMD _IOR(IPMI_IOC_MAGIC, 16, int)
  587. /*
  588. * Set and get the slave address and LUN that we will use for our
  589. * source messages. Note that this affects the interface, not just
  590. * this user, so it will affect all users of this interface. This is
  591. * so some initialization code can come in and do the OEM-specific
  592. * things it takes to determine your address (if not the BMC) and set
  593. * it for everyone else. You should probably leave the LUN alone.
  594. */
  595. struct ipmi_channel_lun_address_set
  596. {
  597. unsigned short channel;
  598. unsigned char value;
  599. };
  600. #define IPMICTL_SET_MY_CHANNEL_ADDRESS_CMD _IOR(IPMI_IOC_MAGIC, 24, struct ipmi_channel_lun_address_set)
  601. #define IPMICTL_GET_MY_CHANNEL_ADDRESS_CMD _IOR(IPMI_IOC_MAGIC, 25, struct ipmi_channel_lun_address_set)
  602. #define IPMICTL_SET_MY_CHANNEL_LUN_CMD _IOR(IPMI_IOC_MAGIC, 26, struct ipmi_channel_lun_address_set)
  603. #define IPMICTL_GET_MY_CHANNEL_LUN_CMD _IOR(IPMI_IOC_MAGIC, 27, struct ipmi_channel_lun_address_set)
  604. /* Legacy interfaces, these only set IPMB 0. */
  605. #define IPMICTL_SET_MY_ADDRESS_CMD _IOR(IPMI_IOC_MAGIC, 17, unsigned int)
  606. #define IPMICTL_GET_MY_ADDRESS_CMD _IOR(IPMI_IOC_MAGIC, 18, unsigned int)
  607. #define IPMICTL_SET_MY_LUN_CMD _IOR(IPMI_IOC_MAGIC, 19, unsigned int)
  608. #define IPMICTL_GET_MY_LUN_CMD _IOR(IPMI_IOC_MAGIC, 20, unsigned int)
  609. /*
  610. * Get/set the default timing values for an interface. You shouldn't
  611. * generally mess with these.
  612. */
  613. struct ipmi_timing_parms
  614. {
  615. int retries;
  616. unsigned int retry_time_ms;
  617. };
  618. #define IPMICTL_SET_TIMING_PARMS_CMD _IOR(IPMI_IOC_MAGIC, 22, \
  619. struct ipmi_timing_parms)
  620. #define IPMICTL_GET_TIMING_PARMS_CMD _IOR(IPMI_IOC_MAGIC, 23, \
  621. struct ipmi_timing_parms)
  622. /*
  623. * Set the maintenance mode. See ipmi_set_maintenance_mode() above
  624. * for a description of what this does.
  625. */
  626. #define IPMICTL_GET_MAINTENANCE_MODE_CMD _IOR(IPMI_IOC_MAGIC, 30, int)
  627. #define IPMICTL_SET_MAINTENANCE_MODE_CMD _IOW(IPMI_IOC_MAGIC, 31, int)
  628. #endif /* __LINUX_IPMI_H */