Lines Matching refs:SAS

1 SAS Layer
4 The SAS Layer is a management infrastructure which manages
5 SAS LLDDs.  It sits between SCSI Core and SAS LLDDs.  The
7 SAM/SPC issues, and a SAS LLDD+sequencer is concerned with
8 phy/OOB/link management, the SAS layer is concerned with:
10       * SAS Phy/Port/HA event management (LLDD generates,
11         SAS Layer processes),
12       * SAS Port management (creation/destruction),
13       * SAS Domain discovery and revalidation,
14       * SAS Domain device management,
16       * Device registration with SCSI Core (SAS) or libata
21 A SAS LLDD is a PCI device driver.  It is concerned with
23 events to the SAS layer.
25 The SAS Layer does most SAS tasks as outlined in the SAS 1.1
28 The sas_ha_struct describes the SAS LLDD to the SAS layer.
29 Most of it is used by the SAS Layer but a few fields need to
35 register your SAS driver with the sysfs SAS tree it creates.
58 are managed by the SAS layer.  So the phys are initialized
60 updated by the SAS layer.
63 and the SAS layer can only read such ones, and vice versa.
70 the SAS Layer.
77 IDENTIFY frame or a FIS frame, _before_ notifying the SAS
79 or provide a different SAS address on that phy/port and this
81 address from the IDENTIFY frame or maybe generate a SAS
99 sas_port this phy is part of.  Set by the SAS Layer.
101 ha -- may be set; the SAS layer sets it anyway.
104 can find your way around faster when the SAS layer calls one
138 sas_addr -- since the SAS layer doesn't want to mess with
141 	 structure) and holds the SAS address of the host
161 called by the LLDD to notify the SAS layer of such events
162 the SAS layer.
173 A SAS LLDD should also implement at least one of the Task
193 A SAS LLDD should implement at least one of those.
247 (2) SAS 1.1 does not define I_T Nexus Reset TMF.
252 Events are _the only way_ a SAS LLDD notifies the SAS layer
254 the SAS layer of anything happening internally or in the SAS
273 A SAS LLDD should be able to generate
276 	- events marked E (expander) if it wants the SAS layer
305 Used to queue a task to the SAS LLDD.  @task is the task to be executed.
312 queuing of any sort and at any level in a SAS LLDD.
331     a) It shows you the physical layout of the SAS domain at
337 viewing the SAS domain:
354 The structure domain_device describes any device in the SAS
355 domain.  It is completely managed by the SAS layer.  A task
356 points to a domain device, this is how the SAS LLDD knows
357 where to send the task(s) to.  A SAS LLDD only reads the
373    is described in the SAS spec.  Leave the CRC field equal 0.