Lines Matching +full:ipmb +full:- +full:dev
12 standardized database for field-replaceable units (FRUs) and a watchdog
25 -------------
32 No matter what, you must pick 'IPMI top-level message handler' to use
35 The message handler does not provide any user-level interfaces.
50 these enabled and let the drivers auto-detect what is present.
61 "The SMBus Driver" on how to hand-configure your system.
65 the kernel, then via a kernel command-line option you can have the
74 'IPMI Poweroff' to do this. The driver will auto-detect if the system
89 ------------
96 ipmi_msghandler - This is the central piece of software for the IPMI
103 ipmi_devintf - This provides a userland IOCTL interface for the IPMI
107 ipmi_si - A driver for various system interfaces. This supports KCS,
111 ipmi_ssif - A driver for accessing BMCs on the SMBus. It uses the
115 ipmi_powernv - A driver for access BMCs on POWERNV systems.
117 ipmi_watchdog - IPMI requires systems to have a very capable watchdog
121 ipmi_poweroff - Some systems support the ability to be turned off via
124 bt-bmc - This is not part of the main driver, but instead a driver for
125 accessing a BMC-side interface of a BT interface. It is used on BMCs
133 linux/ipmi.h - Contains the user interface and IOCTL interface for IPMI.
135 linux/ipmi_smi.h - Contains the interface for system management interfaces
138 linux/ipmi_msgdefs.h - General definitions for base IPMI messaging.
142 ----------
169 Messages that are destined to go out on the IPMB bus going through the
184 There is also an IPMB direct address for a situation where the sender
185 is directly on an IPMB bus and doesn't have to go through the BMC.
187 IPMB using the IPMI_IPMB_DIRECT_ADDR_TYPE with the following format::
203 --------
221 offsets a little easier :-).
248 /* Place-holder for the data, don't make any assumptions about
258 -------------------------------------------
295 To send a message from kernel-land, the ipmi_request_settime() call does
297 self-explanatory. However, it takes a "msgid" parameter. This is NOT
320 When you send a command (which is defined by the lowest-order bit of
321 the netfn per the IPMI spec) on the IPMB bus, the driver will
323 command. If the response is not received in the IPMI-specified 5
346 commands that other things on the IPMB bus have sent you). To receive
351 "val" to non-zero. Any events that have been received by the driver
373 -------------------------------
386 -------------
413 If you specify addrs as non-zero for an interface, the driver will
417 If you specify ports as non-zero for an interface, the driver will
420 If you specify irqs as non-zero for an interface, the driver will
429 locations and they may not be in 8-bit registers. These parameters
439 data used by IPMI is 8-bits wide, but it may be inside a larger
452 (if set to 0) the kernel IPMI daemon. Normally this is auto-detected
479 interface to help speed things up. This is a low-priority kernel
492 tuned to your needs. Maybe, someday, auto-tuning will be added, but
493 that's not a simple thing and even the auto-tuning would need to be
499 write-only parameter. You write a string to this interface. The string
514 ipmb=<ipmb slave addr>
523 -----------------------
540 name of the adapter, as shown in /sys/bus/i2c/devices/i2c-<n>/name.
541 It is *NOT* i2c-<n> itself. Also, the comparison is done ignoring
582 The I2C driver does not support non-blocking access or polling, so
584 time, or other panic-related IPMI functions without special kernel
591 The IPMI IPMB Driver
592 --------------------
594 This driver is for supporting a system that sits on an IPMB bus; it
600 ipmb direct addressing. You can receive commands from other MCs on
607 ipmi_ipmb.retry_time_ms=<Time between retries on IPMB>
614 echo ipmi-ipmb <addr> > /sys/class/i2c-dev/i2c-<n>/device/new_device
620 Command bridging to other IPMB busses through this interface does not
623 host drivers, not something on the IPMB bus.
625 A BMC may have multiple IPMB busses, which bus your device sits on
628 channels being 0-7 and try the IPMB channels.
631 ------------
634 --------------------------------------------------
644 struct device *dev;
655 Note that the dev pointer is included in the above structure, and
657 on the dev pointer.
661 --------
663 A watchdog timer is provided that implements the Linux-standard
672 The default is -1, which means to pick the first one registered.
675 is the amount of seconds before the reset that the pre-timeout panic will
723 gets a pre-action. During a panic or a reboot, the watchdog will
739 --------------
741 The OpenIPMI driver supports the ability to put semi-custom and custom
755 * Event Dir | Event Type: 0x6f (Assertion, sensor-specific event info)
766 * Record ID (bytes 0-1): Set by the SEL.
767 * Record type (byte 2): 0xf0 (OEM non-timestamped)
786 --------
795 either be zero (do a power down) or non-zero (do a power cycle, power
799 in /proc/sys/dev/ipmi/poweroff_powercycle. Note that if the system
803 code should use. The default is -1, which means to pick the first one