Functional Description
5.16.12.2 Message Format
Messages shall be constructed with a one Dword header that describes the message to
be sent followed by the actual message contents. The first Dword shall be constructed
as follows:
Bit
Description
31:28 Reserved
Message Type (MTYPE): Specifies the type of the message.
The message types are:
0h = LED
27:24 1h = SAF-TE
2h = SES-2
3h = SGPIO (register based interface)
All other values reserved
Data Size (DSIZE): Specifies the data size in bytes. If the message (enclosure
services command) has a data buffer that is associated with it that is transferred, the
23:16 size of that data buffer is specified in this field. If there is no separate data buffer, this
field shall have a value of ‘0’. The data directly follows the message in the message
buffer. For ICH10, this value should always be ‘0’.
Message Size (MSIZE): Specifies the size of the message in bytes. The message size
does not include the one Dword header. A value of ‘0’ is invalid. For ICH10, the message
size is always 4 bytes.
15:8
7:0
Reserved
The SAF-TE, SES-2, and SGPIO message formats are defined in the corresponding
specifications, respectively. The LED message type is defined in Section 5.16.12.3. It is
the responsibility of software to ensure the content of the message format is correct. If
the message type is not programmed as 'LED' for this controller, the controller shall not
take any action to update its LEDs. Note that for LED message type, the message size
is always consisted of 4 bytes.
5.16.12.3 LED Message Type
The LED message type specifies the status of up to three LEDs. Typically, the usage for
these LEDs is activity, fault, and locate. Not all implementations necessarily contain all
LEDs (for example, some implementations may not have a locate LED). The message
identifies the HBA port number that the slot status applies to. The format of the LED
message type is defined in Table 5-42. The LEDs shall retain their values until there is a
following update for that particular slot.
186
Datasheet