Lines Matching +full:local +full:- +full:timer +full:- +full:stop
12 standardized database for field-replaceable units (FRUs) and a watchdog
13 timer.
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.
63 IPMI defines a standard watchdog timer. You can enable this with the
64 'IPMI Watchdog Timer' config option. If you compile the driver into
65 the kernel, then via a kernel command-line option you can have the
66 watchdog timer start as soon as it initializes. It also have a lot
70 Cards' menu, enable 'Watchdog Timer Support', and enable the option
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
118 timer. This driver implements the standard Linux watchdog timer
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 ----------
186 --------
204 offsets a little easier :-).
231 /* Place-holder for the data, don't make any assumptions about
241 -------------------------------------------
280 To send a message from kernel-land, the ipmi_request_settime() call does
282 self-explanatory. However, it takes a "msgid" parameter. This is NOT
306 When you send a command (which is defined by the lowest-order bit of
309 command. If the response is not receive in the IPMI-specified 5
322 (the watchdog timer uses this, for instance). You supply your own
337 "val" to non-zero. Any events that have been received by the driver
355 -------------------------------
368 -------------
395 If you specify addrs as non-zero for an interface, the driver will
399 If you specify ports as non-zero for an interface, the driver will
402 If you specify irqs as non-zero for an interface, the driver will
411 locations and they may not be in 8-bit registers. These parameters
421 data used by IPMI is 8-bits wide, but it may be inside a larger
429 The slave_addrs specifies the IPMI address of the local BMC. This is
434 (if set to 0) the kernel IPMI daemon. Normally this is auto-detected
461 interface to help speed things up. This is a low-priority kernel
474 tuned to your needs. Maybe, someday, auto-tuning will be added, but
475 that's not a simple thing and even the auto-tuning would need to be
481 write-only parameter. You write a string to this interface. The string
505 -----------------------
522 name of the adapter, as shown in /sys/class/i2c-adapter/i2c-<n>/name.
523 It is *NOT* i2c-<n> itself. Also, the comparison is done ignoring
537 The slave_addrs specifies the IPMI address of the local BMC. This is
564 The I2C driver does not support non-blocking access or polling, so
566 time, or other panic-related IPMI functions without special kernel
574 ------------
577 --------------------------------------------------
604 --------
606 A watchdog timer is provided that implements the Linux-standard
607 watchdog timer interface. It has three module parameters that can be
614 ifnum_to_use specifies which interface the watchdog timer should use.
615 The default is -1, which means to pick the first one registered.
618 is the amount of seconds before the reset that the pre-timeout panic will
627 specifies what to do when the timer times out, and defaults to
645 If start_now is set to 1, the watchdog timer will start running as
648 If nowayout is set to 1, the watchdog timer will not stop when the
666 gets a pre-action. During a panic or a reboot, the watchdog will
667 start a 120 timer if it is running to make sure the reboot occurs.
675 Once you open the watchdog timer, you must write a 'V' character to the
676 device to close it, or the timer will not stop. This is a new semantic
682 --------------
684 The OpenIPMI driver supports the ability to put semi-custom and custom
696 * Sensor Type: 0x20 (OS critical stop sensor)
698 * Event Dir | Event Type: 0x6f (Assertion, sensor-specific event info)
699 * Event Data 1: 0xa1 (Runtime stop in OEM bytes 2 and 3)
704 always sent to the local management controller. It will handle routing
709 * Record ID (bytes 0-1): Set by the SEL.
710 * Record type (byte 2): 0xf0 (OEM non-timestamped)
719 will first query the capabilities of the local management controller.
720 If it has an SEL, then they will be stored in the SEL of the local
721 management controller. If not, and the local management controller is
722 an event generator, the event receiver from the local management
729 --------
738 either be zero (do a power down) or non-zero (do a power cycle, power
746 code should use. The default is -1, which means to pick the first one