Table of Contents
Advertisement
Table 7-23. Device Specific Completion Code (CC) Definition
Completion
Code
0x40
CC: 0x80
CC: 0x81
CC: 0x82
CC: 0x83-8F
CC: 0x90
CC: 0x91
CC: 0x92-9F
Note:
The codes explicitly defined in
algorithms. Reserved or undefined codes may also be generated by a PECI client
device, and the originating agent must be capable of tolerating any code. The Pass/Fail
mask defined in
based on this information. Refer to
recommendations.
7.1.8
Originator Responses
The simplest policy that an originator may employ in response to receipt of a failing
completion code is to retry the request. However, certain completion codes or FCS
responses are indicative of an error in command encoding and a retry will not result in
a different response from the client. Furthermore, the message originator must have a
response policy in the event of successive failure responses. Refer to
originator response guidelines.
Refer to the definition of each command in
possible command codes or FCS responses for a given command. The following
response policy definition is generic, and more advanced response policies may be
employed at the discretion of the originator developer.
Table 7-24. Originator Response Guidelines
Response
Bad FCS
Abort FCS
CC: 0x8x
CC: 0x9x
None (all 0's)
CC: 0x4x
Good FCS
94
Command Passed
Response timeout. The processor was not able to generate the required response in a timely
fashion. Retry is appropriate.
Response timeout. The processor was not able to allocate resources for servicing this
command. Retry is appropriate.
The processor hardware resources required to service this command are in a low power
state. Retry may be appropriate after modification of PECI wake mode behavior if
appropriate.
Reserved
Unknown/Invalid Request
PECI control hardware, firmware or associated logic error. The processor is unable to process
the request.
Reserved
Table 7-23
Table 7-22
applies to all codes, and general response policies may be
Section 7.1.8
After 1 Attempt
Retry
Fail with PECI client device error.
Fail with PECI client device error if command was not invalid or
Retry
malformed.
The PECI client has failed in its attempts to generate a response.
Retry
Notify application layer.
Abandon any further
n/a
attempts and notify
application layer
Fail with PECI client device error. Client may not be alive or may be
Force bus idle (drive
low) for 1mS and retry
otherwise unresponsive (for example, it could be in RESET).
Pass
n/a
Pass
n/a
Description
may be useful in PECI originator response
for originator response policies and
Section 7.1.2
for a specific definition of
After 3 Attempts
Thermal/Mechanical Specifications and Design Guide
PECI Interface
Table 7-23
for
Advertisement
Table of Contents
