Lines Matching +full:device +full:- +full:specific

1 /*-
2  * SPDX-License-Identifier: BSD-2-Clause OR GPL-2.0
9  * Copyright(c) 2008 - 2011 Intel Corporation. All rights reserved.
22  * Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
28  * Copyright(c) 2008 - 2011 Intel Corporation. All rights reserved.
61 - Nathan Marushak
64 - Richard Boyd
68 This document provides design information relating to the SAS specific
79 developer to code for a specific task.  The developer is not encumbered
81 example, if a specific event can only occur when the object is in a specific
99 Some of the SAS framework objects contain sub-state machines.  These
100 sub-state machines are started upon entrance to the super-state and stopped
101 upon exit of the super-state.
105 be sure to follow the link to that specific object/file definition for
115 The following use case diagram depicts the high-level user interactions with
117 in the system.  The low-level design section will contain detailed use cases
124 - The Framework user also called the OS Specific Driver initiates activities in
126 - The SCI Core calls back into the Framework as a result of an operation either
127 started by the OS Specific Driver or by the Framework itself.
134 This section delineates the high-level class organization for the SCIF_SAS
136 low-level design sections.  Furthermore, additional classes not germane to
138 low-level design sections.
158 - scif_sas_library.h
159 - scif_sas_library.c
173 - scif_sas_controller.h
174 - scif_sas_controller.c
175 - scif_sas_controller_state_handlers.c
176 - scif_sas_controller_states.c
191 - scif_sas_domain.h
192 - scif_sas_domain.c
193 - scif_sas_domain_state_handlers.c
194 - scif_sas_domain_states.c
196 @section scif_sas_remote_device SCIF SAS Remote Device
206 associated with this object.  Methods, data, and functionality specific to a
208 object/file.  SSP specific remote device functionality is covered by the base
211 - scif_sas_remote_device.h
212 - scif_sas_smp_remote_device.h
213 - scif_sas_stp_remote_device.h
214 - scif_sas_remote_device.c
215 - scif_sas_remote_device_state_handlers.c
216 - scif_sas_remote_device_states.c
217 - scif_sas_remote_device_starting_substate_handlers.c
218 - scif_sas_remote_device_starting_substates.c
219 - scif_sas_remote_device_ready_substate_handlers.c
220 - scif_sas_remote_device_ready_substates.c
221 - scif_sas_smp_remote_device.c
222 - scif_sas_stp_remote_device.c
224 The SCIF_SAS_REMOTE_DEVICE object has sub-state machines defined for
225 the READY and STARTING super-states.  For more information on the
226 super-state machine please refer to SCI_BASE_REMOTE_DEVICE_STATES
229 In the SCIF_SAS_REMOTE_DEVICE_STARTING_SUBSTATES sub-state machine,
230 the remote device currently has to wait for the core to
231 return an indication that the remote device has successfully started
232 and become ready.  If all goes well, then the remote device will
235 For more information on the starting sub-state machine states please refer
239 … latex State_Machine_Diagram__STARTING_SUB-STATE__STARTING_SUB-STATE.eps "SCIF SAS Remote Device S…
240 …e html State_Machine_Diagram__STARTING_SUB-STATE__STARTING_SUB-STATE.jpg "SCIF SAS Remote Device S…
242 In the SCIF_SAS_REMOTE_DEVICE_READY_SUBSTATES sub-state machine,
243 the remote device currently only allows new host IO requests during the
247 For more information on the ready sub-state machine states please refer
251 @image latex State_Machine_Diagram__READY_SUB-STATE__READY_SUB-STATE.eps "SCIF SAS Remote Device Re…
252 @image html State_Machine_Diagram__READY_SUB-STATE__READY_SUB-STATE.jpg "SCIF SAS Remote Device Rea…
266 - scif_sas_request.h
267 - scif_sas_request.c
281 - scif_sas_io_request.h
282 - scif_sas_smp_io_request.h
283 - scif_sas_stp_io_request.h
284 - scif_sas_sati_binding.h
285 - scif_sas_io_request.c
286 - scif_sas_io_request_state_handlers.c
287 - scif_sas_io_request_states.c
288 - scif_sas_smp_io_request.c
289 - scif_sas_stp_io_request.c
303 - scif_sas_task_request.h
304 - scif_sas_stp_task_request.h
305 - scif_sas_task_request.c
306 - scif_sas_task_request_state_handlers.c
307 - scif_sas_task_request_states.c
308 - scif_sas_stp_task_request.c
314 smp request for expander device discover process, or stp request for NCQ
326 - scif_sas_internal_io_request.h
327 - scif_sas_internal_io_request.c
328 - scif_sas_controller.h
330 @section scif_sas_smp_remote_device SCIF SAS SMP REMOTE DEVICE
332 The SCIF SAS SMP REMOTE DEVICE object represents the expander device and fulfills
335 SATA device is discovered and in spinup_hold condition. The SCIF SAS SMP REMOTE DEVICE
336 object also fulfills expander attached device Target Reset (Phy Control) activity.
342 - scif_sas_smp_remote_device.h
343 - scif_sas_smp_remote_device.c
344 - scif_sas_smp_request.h
345 - scif_sas_smp_request.c