Home
last modified time | relevance | path

Searched full:ipmb (Results 1 – 25 of 28) sorted by relevance

12

/Linux-v6.1/Documentation/driver-api/
Dipmb.rst2 IPMB Driver for a Satellite MC
5 The Intelligent Platform Management Bus or IPMB, is an
9 IPMB is also associated with the messaging protocol through the
10 IPMB bus.
12 The devices using the IPMB are usually management
17 When an IPMB is implemented in the system, the BMC serves as
18 a controller to give system software access to the IPMB. The BMC
20 Controller or Satellite MC) via IPMB and the device
23 For more information on IPMB and the format of an IPMB message,
24 refer to the IPMB and IPMI specifications.
[all …]
Dipmi.rst169 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::
324 the netfn per the IPMI spec) on the IPMB bus, the driver will
349 commands that other things on the IPMB bus have sent you). To receive
517 ipmb=<ipmb slave addr>
594 The IPMI IPMB Driver
597 This driver is for supporting a system that sits on an IPMB bus; it
603 ipmb direct addressing. You can receive commands from other MCs on
[all …]
Dindex.rst42 ipmb
/Linux-v6.1/Documentation/devicetree/bindings/ipmi/
Dipmi-ipmb.yaml4 $id: http://devicetree.org/schemas/ipmi/ipmi-ipmb.yaml#
7 title: IPMI IPMB device bindings
9 description: IPMI IPMB device bindings
17 - ipmi-ipmb
28 description: The address of the BMC on the IPMB bus. Defaults to 0x20.
43 lets you use two devices on the IPMB, one for master and one for slave,
59 ipmi-ipmb@40 {
60 compatible = "ipmi-ipmb";
/Linux-v6.1/arch/arm/boot/dts/
Daspeed-bmc-facebook-yosemitev2.dts123 //Host1 IPMB bus
127 compatible = "ipmb-dev";
134 //Host2 IPMB bus
138 compatible = "ipmb-dev";
145 //Host3 IPMB bus
149 compatible = "ipmb-dev";
156 //Host4 IPMB bus
160 compatible = "ipmb-dev";
217 compatible = "ipmb-dev";
Daspeed-bmc-facebook-tiogapass.dts439 compatible = "ipmb-dev";
530 compatible = "ipmb-dev";
Daspeed-bmc-quanta-s6q.dts452 ipmb@10 {
453 compatible = "ipmb-dev";
Daspeed-bmc-inventec-transformers.dts118 compatible = "ipmb-dev";
Daspeed-bmc-tyan-s8036.dts224 /* Directly connected to IPMB HDR. */
Daspeed-bmc-inspur-nf5280m6.dts244 /* IPMB */
Daspeed-bmc-tyan-s7106.dts259 * - IPMB pin header
Daspeed-bmc-bytedance-g220a.dts462 compatible = "ipmb-dev";
/Linux-v6.1/drivers/char/ipmi/
DKconfig45 by default, generate IPMI OEM type f0 events holding the IPMB
79 tristate 'IPMI IPMB interface'
82 Provides a driver for a system running right on the IPMB bus.
83 It supports normal system interface messages to a BMC on the IPMB
85 IPMB direct messages. This module requires I2C support.
173 tristate 'IPMB Interface handler'
179 the IPMB interface. This module requires I2C support.
Dipmb_dev_int.c4 * IPMB driver to receive a request and send a response
230 * Verify if message has proper ipmb header with minimum length
243 * The IPMB protocol only supports I2C Writes so there is no need
245 * This i2c callback function only monitors IPMB request messages
271 * Since the first byte in the IPMB message is the in ipmb_slave_cb()
273 * of the IPMB driver to format the message properly. in ipmb_slave_cb()
322 "%s%d", "ipmb-", in ipmb_probe()
353 { "ipmb-dev", 0 },
366 .name = "ipmb-dev",
376 MODULE_DESCRIPTION("IPMB driver");
Dipmi_ipmb.c4 * Driver to talk to a remote management controller on IPMB.
22 #define DEVICE_NAME "ipmi-ipmb"
177 * The IPMB protocol only supports i2c writes so there is no need to
223 * response with channel 0. This will always be ipmb in ipmi_ipmb_send_response()
494 strscpy(binfo.type, "ipmb-slave", I2C_NAME_SIZE); in ipmi_ipmb_probe()
582 MODULE_DESCRIPTION("IPMI IPMB driver");
Dipmi_si_hotmod.c31 * ipmb=<ipmb addr>
169 rv = check_hotmod_int_op(curr, o, "ipmb", &h->slave_addr); in parse_hotmod_str()
Dipmi_msghandler.c351 /* Commands we sent out to the IPMB bus. */
354 /* Commands sent on the IPMB that had errors on the SEND CMD */
373 /* Responses I have sent to the IPMB bus. */
385 /* Commands we sent out to the IPMB bus. */
388 /* Commands sent on the IPMB that had errors on the SEND CMD */
400 /* Responses I have sent to the IPMB bus. */
427 /* Retransmissions on IPMB that failed. */
490 * sequence numbers for IPMB messages that go out of the
568 * If we are doing maintenance on something on IPMB, extend
1796 /* Format the IPMB header data. */ in format_ipmb_msg()
[all …]
Dipmi_si_hardcode.c57 …"Set the default IPMB slave address for the controller. Normally this is 0x20, but can be overrid…
Dipmi_poweroff.c334 * Get IPMI ipmb address in ipmi_poweroff_cpi1()
364 * Setup IPMB address target instead of local target in ipmi_poweroff_cpi1()
/Linux-v6.1/include/linux/
Dipmi_smi.h48 * * IPMB (over a IPMB to another MC)
67 * In IPMB mode, we are acting as an IPMB device. Commands will be in
80 * This is similar to the format defined in the IPMB manual section
84 * IPMB messages can be commands and responses in both directions.
Dipmi.h343 /* Helper function for computing the IPMB checksum of some data. */
/Linux-v6.1/include/uapi/linux/
Dipmi.h71 /* An IPMB Address. */
84 * Used for messages received directly from an IPMB that have not gone
85 * through a MC. This is for systems that sit right on an IPMB so
230 * (IPMI_UNUSED_ADDR_TYPE). When talking to an IPMB channel, you must
231 * supply a valid IPMB address with the addr_type set properly.
417 /* Legacy interfaces, these only set IPMB 0. */
/Linux-v6.1/Documentation/devicetree/bindings/i2c/
Dnuvoton,npcm7xx-i2c.yaml12 (i.e. IPMB mode). HW FIFO for TX and RX are supported.
/Linux-v6.1/Documentation/translations/zh_CN/driver-api/
Dindex.rst57 * ipmb
/Linux-v6.1/drivers/acpi/
Dacpi_ipmi.c65 * In fact it can also be IPMB type. But we will have to
278 * the addr type should be changed to IPMB. Then we will have to parse in acpi_format_ipmi_request()
279 * the IPMI request message buffer to get the IPMB address. in acpi_format_ipmi_request()

12