Re-arm Sensor Events
更新时间: 2026/08/06
在Gitcode上查看源码

Re-arm Sensor Events

Change History

openUBMC VersionRevision DateDescription
25.062025/06/26Initial draft: add command details

Basic Information

Function Description

Re-arrange the sensor events.

Privilege

BasicSetting

Command Information

Request Information

ByteData Field
NetFnS/E 04h
CMD2Ah
1sensor number (FFh=reserved)
2[7]-0b=re-arm all event status from this sensor. If 0, following parameter
bytes are ignored, but should still be written as 0, if sent.
[6:0]-reserved. Write as 000_0000b.
(3)*For sensors with threshold based events:
[7]-1b=re-arm assertion event for upper non-critical going high
[6]-1b=re-arm assertion event for upper non-critical going low
[5]-1b=re-arm assertion event for lower non-recoverable going high
[4]-1b=re-arm assertion event for lower non-recoverable going low
[3]-1b=re-arm assertion event for lower critical going high
[2]-1b=re-arm assertion event for lower critical going low
[1]-1b=re-arm assertion event for lower non-critical going high
[0]-1b=re-arm assertion event for lower non-critical going low
For sensors with discrete events:
[7]-1b=re-arm assertion event for state bit 7
[6]-1b=re-arm assertion event for state bit 6
[5]-1b=re-arm assertion event for state bit 5
[4]-1b=re-arm assertion event for state bit 4
[3]-1b=re-arm assertion event for state bit 3
[2]-1b=re-arm assertion event for state bit 2
[1]-1b=re-arm assertion event for state bit 1
[0]-1b=re-arm assertion event for state bit 0
(4)*For sensors with threshold based events:
[7:4]-reserved. Write as 0000b.
[3]-1b=re-arm assertion event for upper non-recoverable going high
[2]-1b=re-arm assertion event for upper non-recoverable going low
[1]-1b=re-arm assertion event for upper critical going high
[0]-1b=re-arm assertion event for upper critical going low
For sensors with discrete events:
(00h otherwise)
[7]-reserved. Ignore on read.
[6]-1b=re-arm assertion event for state bit 14
[5]-1b=re-arm assertion event for state bit 13
[4]-1b=re-arm assertion event for state bit 12
[3]-1b=re-arm assertion event for state bit 11
[2]-1b=re-arm assertion event for state bit 10
[1]-1b=re-arm assertion event for state bit 9
[0]-1b=re-arm assertion event for state bit 8
(5)*For sensors with threshold based events:
[7]-1b=re-arm deassertion event for upper non-critical going high
[6]-1b=re-arm deassertion event for upper non-critical going low
[5]-1b=re-arm deassertion event for lower non-recoverable going high
[4]-1b=re-arm deassertion event for lower non-recoverable going low
[3]-1b=re-arm deassertion event for lower critical going high
[2]-1b=re-arm deassertion event for lower critical going low
[1]-1b=re-arm deassertion event for lower non-critical going high
[0]-1b=re-arm deassertion event for lower non-critical going low
For sensors with discrete events:
(00h otherwise)
[7]-1b=re-arm deassertion event for state bit 7
[6]-1b=re-arm deassertion event for state bit 6
[5]-1b=re-arm deassertion event for state bit 5
[4]-1b=re-arm deassertion event for state bit 4
[3]-1b=re-arm deassertion event for state bit 3
[2]-1b=re-arm deassertion event for state bit 2
[1]-1b=re-arm deassertion event for state bit 1
[0]-1b=re-arm deassertion event for state bit 0
(6)*For sensors with threshold based events:
[7:4]-reserved. Write as 0000b.
[3]-1b=re-arm deassertion event for upper non-recoverable going high
[2]-1b=re-arm deassertion event for upper non-recoverable going low
[1]-1b=re-arm deassertion event for upper critical going high
[0]-1b=re-arm deassertion event for upper critical going low
For sensors with discrete events:
(00h otherwise)
[7]-reserved. Ignore on read.
[6]-1b=re-arm deassertion event for state bit 14
[5]-1b=re-arm deassertion event for state bit 13
[4]-1b=re-arm deassertion event for state bit 12
[3]-1b=re-arm deassertion event for state bit 11
[2]-1b=re-arm deassertion event for state bit 10
[1]-1b=re-arm deassertion event for state bit 9
[0]-1b=re-arm deassertion event for state bit 8
* Note: The content in parentheses indicates that the content may not exist.
*=Devices must accept a variable number of request data bytes (2 to 6). This requirement is to allow a reduction in the number of data bytes that must be transferred. The receiver shall treat data bytes that are not explicitly transmitted as if they were written as '00h'.

Response Information

ByteData Field
1Completion Code

Command Example

Reconfigure sensor events.

Request:

bash
ipmicmd -k "0f 00 04 2a 01 00" smi 0

Response:

text
0f

Back to Index