Lines Matching +full:smbus +full:- +full:timeout +full:- +full:disable
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.
47 this, choose 'IPMI SMBus handler', but be ready to try to do some
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
71 'Disable watchdog shutdown on close'.
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,
108 SMIC, and BT interfaces. Unless you have an SMBus interface or your
111 ipmi_ssif - A driver for accessing BMCs on the SMBus. It uses the
112 I2C kernel driver's SMBus interfaces to send and receive IPMI messages
113 over the SMBus.
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 ----------
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
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
405 The other try... items disable discovery by their corresponding
406 names. These are all enabled by default, set them to zero to disable
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
434 (if set to 0) the kernel IPMI daemon. Normally this is auto-detected
437 want the CPU hit) can disable it.
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
504 The SMBus Driver (SSIF)
505 -----------------------
507 The SMBus driver allows up to 4 SMBus devices to be configured in the
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
531 The tryxxx parameters can be used to disable detecting interfaces
541 alerts_broken does not enable SMBus alert for SSIF. Otherwise SMBus
544 Discovering the IPMI compliant BMC on the SMBus can cause devices on
545 the I2C bus to fail. The SMBus driver writes a "Get Device ID" IPMI
548 recommended that the known I2C address be given to the SMBus driver in
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
610 modprobe ipmi_watchdog timeout=<t> pretimeout=<t> action=<action type>
615 The default is -1, which means to pick the first one registered.
617 The timeout is the number of seconds to the action, and the pretimeout
618 is the amount of seconds before the reset that the pre-timeout panic will
620 that the pretimeout is the time before the final timeout. So if the
621 timeout is 50 seconds and the pretimeout is 10 seconds, then the pretimeout
622 will occur in 40 second (10 seconds before the timeout). The panic_wdt_timeout
623 is the value of timeout which is set on kernel panic, in order to let actions
655 ipmi_watchdog.timeout=<t> ipmi_watchdog.pretimeout=<t>
665 The watchdog will panic and start a 120 second reset timeout if it
666 gets a pre-action. During a panic or a reboot, the watchdog will
682 --------------
684 The OpenIPMI driver supports the ability to put semi-custom and custom
698 * Event Dir | Event Type: 0x6f (Assertion, sensor-specific event info)
709 * Record ID (bytes 0-1): Set by the SEL.
710 * Record type (byte 2): 0xf0 (OEM non-timestamped)
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