Skip to content

Commit b81a817

Browse files
committed
ipmi: Add docs for the IPMI IPMB driver
Describe how to use the IPMI IPMB driver, including it's quirks. Signed-off-by: Corey Minyard <[email protected]> Tested-by: Andrew Manley <[email protected]> Reviewed-by: Andrew Manley <[email protected]>
1 parent ddf5873 commit b81a817

File tree

1 file changed

+39
-0
lines changed

1 file changed

+39
-0
lines changed

Documentation/driver-api/ipmi.rst

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -591,6 +591,45 @@ web page.
591591
The driver supports a hot add and remove of interfaces through the I2C
592592
sysfs interface.
593593

594+
The IPMI IPMB Driver
595+
--------------------
596+
597+
This driver is for supporting a system that sits on an IPMB bus; it
598+
allows the interface to look like a normal IPMI interface. Sending
599+
system interface addressed messages to it will cause the message to go
600+
to the registered BMC on the system (default at IPMI address 0x20).
601+
602+
It also allows you to directly address other MCs on the bus using the
603+
ipmb direct addressing. You can receive commands from other MCs on
604+
the bus and they will be handled through the normal received command
605+
mechanism described above.
606+
607+
Parameters are::
608+
609+
ipmi_ipmb.bmcaddr=<address to use for system interface addresses messages>
610+
ipmi_ipmb.retry_time_ms=<Time between retries on IPMB>
611+
ipmi_ipmb.max_retries=<Number of times to retry a message>
612+
613+
Loading the module will not result in the driver automatcially
614+
starting unless there is device tree information setting it up. If
615+
you want to instantiate one of these by hand, do::
616+
617+
echo ipmi-ipmb <addr> > /sys/class/i2c-dev/i2c-<n>/device/new_device
618+
619+
Note that the address you give here is the I2C address, not the IPMI
620+
address. So if you want your MC address to be 0x60, you put 0x30
621+
here. See the I2C driver info for more details.
622+
623+
Command bridging to other IPMB busses through this interface does not
624+
work. The receive message queue is not implemented, by design. There
625+
is only one receive message queue on a BMC, and that is meant for the
626+
host drivers, not something on the IPMB bus.
627+
628+
A BMC may have multiple IPMB busses, which bus your device sits on
629+
depends on how the system is wired. You can fetch the channels with
630+
"ipmitool channel info <n>" where <n> is the channel, with the
631+
channels being 0-7 and try the IPMB channels.
632+
594633
Other Pieces
595634
------------
596635

0 commit comments

Comments
 (0)