SAS Notify (Enable Spinup)

Elliott, Robert (Server Storage) elliott at
Fri Nov 19 18:17:59 PST 2004

* From the T10 Reflector (t10 at, posted by:
* "Elliott, Robert (Server Storage)" <elliott at>
> * From the T10 Reflector (t10 at, posted by:
> * Gil Romo <gil.romo at>
> *
> SAS initiator and expander ports transmit NOTIFY (E/S) 
> primitives to SAS target 
> ports, as described in SAS1.1 subclause
> Here are a few questions:
> Is it permissible for a wide port to transmit a primitive on 
> each physical link?

Yes.  The recipient should treat it equally no matter which
phy it arrives on (if it has more than one phy).

> The primitive is transmitted after the link reset sequence is 
> complete.  I don't see reception of this primitive covered in 
> the SAS link layer description.  

It's not mentioned in the link, port, or transport layer state
machines.  It doesn't affect their normal operation so would
be more of a nuisance than a help.  

> Is there a confirmation that informs the application layer of 
> detection of this primitive?

The SA_PC state machine (application layer power conditions) 
mentions reception of it, just using words like "a NOTIFY
(ENABLE SPINUP) is detected."
> Are there any recommendations for transmission frequency (ie, 
> how often does the target device expect to receive the 
> primitive)?

That's system dependent, not target device dependent.

After power on, the frequency affects how long drive spinup
will take.  After initial spinup, the frequency affects how 
long the START STOP UNIT command will take to be processed
when it is used to enter/exit the Stopped power condition.

> Thanks,
> Gil
> ------------
> Gilbert Romo
> ASIC Engineer
> QLogic Corporation, Aliso Viejo, California
> Office: 949-389-6266
> E-mail: gil.romo at

Rob Elliott, elliott at
Hewlett-Packard Industry Standard Server Storage Advanced Technology

* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at

More information about the T10 mailing list