Specifications

SATA-IO Confidential 30
o NOTE – ensure there is no conflict with a device initiated request
o NOTE – a host vendor may provide a vendor unique tool for initiating the power management
requests as to ensure the test does complete as necessary.
• Issue COMWAKE and wait for complete wake of host
• This requirement must be verified on 10 total sequences within the trace.
• Device : Confirm Partial wake sequence completion and COMWAKE timing of being within 10us of
COMWAKE receipt from host (use trace to analyze timings)
Pass/Fail Criteria
• Host : Confirm Partial wake sequence completion and ALIGN timing of being within 10us of COMWAKE
receipt from device/emulator/tool (use trace to analyze timings)
o NOTE : In the case that no host initiated request was completed, the pass/fail result will be N/A.
• Since a single result is reported, the worst-case result out of all 10 cases must be reported (i.e. largest value).
2.5.2. IPM-02 : Slumber State exit latency (host-initiated)
2.5.2.1. Device/Host Expected Behavior
See section 8.1 of Serial ATA Revision 2.6.
The product exit latency (i.e. COMWAKE response) from the slumber state shall start within 10 milliseconds of
COMWAKE receipt from the initiator of the wake sequence.
A method for testing the exit latency of a device is for host software to initiate a COMWAKE on the interface. After
initiating the request, the host would record the time until the W bit is set to one within the DIAG field of the SError
register.
• Setup bus analyzer (or scope) for tracing of bus activity & begin tracing
Measurement Requirements (Device)
• Check Word 76 bit 9 in IDENTIFY DEVICE or IDENTIFY PACKET DEVICE (set to one)
o If the above is true, then run the following test (HIPM)
 Issue PMREQ_S and receive device response
 Issue COMWAKE and wait for complete wake of device
• This requirement must be verified on 10 total sequences within the trace.
• Setup bus analyzer (or scope) for tracing of bus activity & begin tracing
Measurement Requirements (Host)
• Wait for a Slumber IPM request from the host
o NOTE – there is no guaranteed method for causing the host to send a request, some common ATA
(or vendor specific) methods which may cause a request from the host are:
 Leave the system idle and monitor for an Slumber IPM request for 10 seconds
o NOTE – ensure there is no conflict with a device initiated request
o NOTE – a host vendor may provide a vendor unique tool for initiating the power management
requests as to ensure the test does complete as necessary.
• Issue COMWAKE and wait for complete wake of host
• This requirement must be verified on 10 total sequences within the trace.
• Device : Confirm Slumber wake sequence completion and COMWAKE timing of being within 10ms of
COMWAKE receipt from host (use trace to analyze timings)
Pass/Fail Criteria
• Host : Confirm Slumber wake sequence completion and ALIGN timing of being within 10ms of COMWAKE
receipt from device/emulator/tool (use trace to analyze timings)
o NOTE : In the case that no host initiated request was completed, the pass/fail result will be N/A.
• Since a single result is reported, the worst-case result out of all 10 cases must be reported (i.e. largest value).