Specifications

SATA-IO Confidential 29
o Check for non-zero value of Word 47 bits 7:0
o Issue Set Multiple command to change the block size from the value reported in Word 47 bits 7:0
o Check value of Word 59 bits 8:0
o Verify correct block size is set due to Set Multiple command
o Issue COMRESET and complete OOB sequence
o Check value of Word 59 bits 8:0
• Verify that IDENTIFY DEVICE Word 59 bits 8:0 contains the same value following COMRESET
Pass/Fail Criteria
2.5. Interface Power Management
The Serial ATA Interface Power Management (IPM) test requirements are determined by the requirements of the
feature as defined in Serial ATA Revision 2.6.
Some of the test requirements listed in this section require that support for device initiating interface power
management and/or host initiating interface power management is claimed by the product for verification of the
Expected Behavior. Support for device initiating interface power management can be verified by reading Word 78 bit
3 set to one in IDENTIFY DEVICE or IDENTIFY PACKET DEVICE data. Support for host initiating interface power
management can be verified by reading Word 76 bit 9 set to one in IDENTIFY DEVICE or IDENTIFY PACKET
DEVICE data. For each test requirement, there will be a note outlining whether support for device initiating interface
power management and/or host initiating interface power management is a requirement for testing said test
requirement.
A product may claim support for both device initiating interface power management (DIPM) requests and receipt of
host initiating power management (HIPM) requests. It is not required to support both types of requests.
If a host intends to be validated for Interface Power Management (IPM) support through the Interoperability Tests, it
must be pre-configured (BIOS, driver, utility) to automatically send SET FEATURES to enable DIPM requests
following device detection and to configure the host in such a way that is may accept DIPM requests. This is because
there are limitations to how hosts may be validated for a feature, and DIPM requests are a key requirement for any
IPM validation on a host. If a host only supports HIPM, there is no way to validate this support and it will not be
verified for Interop Testing.
2.5.1. IPM-01 : Partial State exit latency (host-initiated)
2.5.1.1. Device/Host Expected Behavior
See section 8.1 of Serial ATA Revision 2.6.
The device and host exit latency (i.e. COMWAKE response) from the partial state shall start within 10 microseconds
of COMWAKE receipt from the initiator of the wake sequence.
• 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_P and receive device response
 Issue COMWAKE and wait for complete wake of device
o 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 Partial 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 (up to 10 seconds)