Comment on 08-206 rev. 4
craig at expertio.com
Tue Feb 3 20:03:29 PST 2009
* From the T10 Reflector (t10 at t10.org), posted by:
* "Craig Stoops" <craig at expertio.com>
I'd like to differ for the following reasons:
1) Although it is set to ACTIVE when we start the cominit, it doesn't
really matter since SAS PHY is NOT_READY. So I think technically it
doesn't matter if you set ACTIVE then or not until after SP15 when READY
2) On the other hand, in PS_ALIGN0, we do not infact know that the wakeup
will be successful of not. Align exchange could fail, and an OOB sequence
might be needed to recover. Unlike the the other case above, SAS PHY is
still READY in this PS state. The combination of READY and ACTIVE signals
that the Port Layer can request connections, and that we want to know they
will be opened or rejected in a reasonable time, which can't be guaranteed
until we are back to SP15 - A cominit sequence can take a while.
I'd make the arguement that maybe even ACTIVE shouldn't be set in the
first case until we get to SP15, basically advertising a status of NONE.
Any, that's my two cents.
"Your Storage Protocol Verification Experts"
> * From the T10 Reflector (t10 at t10.org), posted by:
> * Gerry.Houlder at seagate.com
> 08-206 creates a SASPhyPwrMgmt state machine variable that can assume
> states of Active, Partial, or Slumber. I presume Active means the
> transmitter is ready to send primitives or signals (i.e., in a condition
> to send anything other than DC Idle).
> The variable is set to active on entry to OOB_COMINIT. This makes sense to
> me, since the transmitter is about to transmit a COMINIT signal on the
> I think this variable should also be set to Active on entry to the
> SAS_PS_ALIGN0 state, since the transmitter is expected to send ALIGN (0)
> primitives at this point. According to current wording, however, the
> variable is not set to active until the transition from SAS_PS_ALIGN1 to
> PHY_Ready. This seems wrong to me.
> I think this variable shall be set to Active upon entry to the
> SAS_PS_ALIGN0 state. Alternatively, it could be set to Active on exiting
> SAS_PS_Phy_Low_Power state since this is the only place that transitions
> the SAS_PS_ALIGN0 state. Then the reference to this variable is not needed
> in clause 188.8.131.52.3 (Transition from Align1 to Phy Ready).
> Comments anyone? If this is agreeable, I'd like to have George incorporate
> this change into the integrated version of the proposal.
> * For T10 Reflector information, send a message with
> * 'info t10' (no quotes) in the message body to majordomo at t10.org
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org
More information about the T10