Lines Matching refs:mid

7 This document outlines the interface between the Linux SCSI mid level and
35 The SCSI mid level isolates an LLD from other layers such as the SCSI
47 Many LLDs are documented there (e.g. aic7xxx.txt). The SCSI mid-level is
87   a) directly invoking functions supplied by the mid level
89      supplied by the mid level. The mid level will then invoke these
93      by the mid level
109 that are shared with the mid level and other layers.
130 with the SCSI mid level.
136 registered with sysfs at this point. The SCSI mid level first becomes
140 is a typical sequence of calls between the LLD and the mid level.
141 This example shows the mid level scanning the newly introduced HBA for 3 
145 LLD                   mid level                    LLD
164 *** For scsi devices that the mid level tries to scan but do not
174 LLD                      mid level                 LLD
185 by the mid-level.  struct Scsi_Host instances are freed from
190 counting logic is being introduced into the mid level to cope with many
198 An LLD can use this sequence to make the mid level aware of a SCSI device:
201 LLD                   mid level                    LLD
213 probably cause that device to be set offline by the mid level. An LLD that
218 LLD                      mid level                 LLD
227 slave_configure() callbacks). Such instances are "owned" by the mid-level.
254 LLD                      mid level                 LLD
274 The mid level invokes scsi_change_queue_depth() with "cmd_per_lun" for that
278 *** For scsi devices that the mid level tries to scan but do not
283 LLD                      mid level                 LLD
309 were exclusively owned by the mid level. LLDs would not usually need to
325 were exclusively owned by the mid level. See the access functions declared
361 These functions are supplied by the SCSI mid level for use by LLDs.
364 arrange for the SCSI mid level to be loaded and initialized before any LLD
638  *      mid level itself don't need to call this, but there should be 
730 should be passed to the mid level's scsi_host_alloc() [or scsi_register() /
798  *      Notes: First function called from the SCSI mid level on this
963  *      the 'cmd' then it is passed to the SCSI mid level. If the SCSI
964  *      mid level does not recognize it, then the LLD that controls
1016  *      On both of these returns, the mid-layer will requeue the I/O
1063  *      callback is not invoked within a certain period the SCSI mid
1069  *      the mid level queuing a command to an LLD.
1111  *      exist but the mid level is just about to scan for it (i.e. send
1184    (*queuecommand)() - primary callback that the mid level uses to inject
1221     use_clustering - 1=>SCSI commands in mid level's queue can be merged,
1255 back to the mid level. The SCSI mid level will ensure that no more SCSI
1291                    then the mid level will assume the sense_buffer array
1292                    contains a valid SCSI sense buffer; otherwise the mid
1335 operations performed by the mid level use the struct Scsi_Host::host_lock
1351 Either way, when a status of CHECK CONDITION is detected, the mid level
1355 this byte is initialized to 0 before each command) then the mid level will