Query regarding device's behavior for START STOP UNIT command

Mistry, Munjal Munjal_Mistry at mentor.com
Mon Jul 20 07:02:24 PDT 2015


Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1507201_f.htm">HTML-formatted message</a>

Hello,
I have few queries regarding device's behavior for START STOP UNIT command in
different power state transition. Below are the scenarios. Please suggest the
correct behavior for it.
Scenario 1: Device is in "Wait_Standby" state (PC6) and it receives START
STOP UNIT command with request to enter in "Active" state (PC1) with
"IMMED=0". In that case, what could be the behavior of the device?
(1) It will wait to enter "Standby" state (PC3) and then send it's response
with "GOOD" status. Then it transit to "Wait_Active" state (PC4) and then
move to "Active" state (PC1) followed by sending response with "GOOD" status.
(2) It will send "BUSY" response for "Active" state (PC1) transition command
and continue to execute "Wait_Standby" state (PC6) transition. Once it
reached to "Standby" state (PC3), it drives "GOOD" response for it.
Scenario 2: Device is in "Wait_Standby" state (PC6) and it receives START
STOP UNIT command with request to enter in "Idle" state (PC2) with "IMMED=1"
which is an erroneous case. In this case, what could be the behavior of the
device?
(1) It will send "CHECK CONDITION" response for newer command and continue
the execution of power transition from "Wait_Standby" state to "Standby"
state. Once it reach to the "Standby" state, it sends "GOOD" response.
(2) Once it reaches to "Standby" state, it will send "GOOD" response followed
by sending "CHECK CONDITION" response for command which request to "Idle"
state.
Request you to help me to find best possible solution for the above
scenarios.
Thank you.
--
Warm Regards;
Munjal Mistry



More information about the T10 mailing list