Lines Matching refs:SAS

4 SAS Layer
7 The SAS Layer is a management infrastructure which manages
8 SAS LLDDs.  It sits between SCSI Core and SAS LLDDs.  The
10 SAM/SPC issues, and a SAS LLDD+sequencer is concerned with
11 phy/OOB/link management, the SAS layer is concerned with:
13       * SAS Phy/Port/HA event management (LLDD generates,
14         SAS Layer processes),
15       * SAS Port management (creation/destruction),
16       * SAS Domain discovery and revalidation,
17       * SAS Domain device management,
19       * Device registration with SCSI Core (SAS) or libata
24 A SAS LLDD is a PCI device driver.  It is concerned with
26 events to the SAS layer.
28 The SAS Layer does most SAS tasks as outlined in the SAS 1.1
31 The sas_ha_struct describes the SAS LLDD to the SAS layer.
32 Most of it is used by the SAS Layer but a few fields need to
38 register your SAS driver with the sysfs SAS tree it creates.
66 are managed by the SAS layer.  So the phys are initialized
68 updated by the SAS layer.
71 and the SAS layer can only read such ones, and vice versa.
85       the SAS Layer.
94       IDENTIFY frame or a FIS frame, _before_ notifying the SAS
96       or provide a different SAS address on that phy/port and this
98       address from the IDENTIFY frame or maybe generate a SAS
119       sas_port this phy is part of.  Set by the SAS Layer.
122     - may be set; the SAS layer sets it anyway.
126       can find your way around faster when the SAS layer calls one
168        - since the SAS layer doesn't want to mess with
171 	 structure) and holds the SAS address of the host
204 A SAS LLDD should also implement at least one of the Task
223 A SAS LLDD should implement at least one of those.
277 (2) SAS 1.1 does not define I_T Nexus Reset TMF.
282 Events are **the only way** a SAS LLDD notifies the SAS layer
284 the SAS layer of anything happening internally or in the SAS
305 A SAS LLDD should be able to generate
309 	- events marked E (expander) if it wants the SAS layer
354 Used to queue a task to the SAS LLDD.  @task is the task to be executed.
361 queuing of any sort and at any level in a SAS LLDD.
385     a) It shows you the physical layout of the SAS domain at
391 viewing the SAS domain:
409 The structure domain_device describes any device in the SAS
410 domain.  It is completely managed by the SAS layer.  A task
411 points to a domain device, this is how the SAS LLDD knows
412 where to send the task(s) to.  A SAS LLDD only reads the
428    is described in the SAS spec.  Leave the CRC field equal 0.