Lines Matching full:mid

9 This document outlines the interface between the Linux SCSI mid level and
37 The SCSI mid level isolates an LLD from other layers such as the SCSI
49 documented in Documentation/scsi (e.g. aic7xxx.rst). The SCSI mid-level is
90   a) directly invoking functions supplied by the mid level
92      supplied by the mid level. The mid level will then invoke these
96      by the mid level
98 Those functions in group a) are listed in a section entitled "Mid level
112 that are shared with the mid level and other layers.
128 with the SCSI mid level.
134 registered with sysfs at this point. The SCSI mid level first becomes
138 is a typical sequence of calls between the LLD and the mid level.
139 This example shows the mid level scanning the newly introduced HBA for 3
143     LLD                   mid level                    LLD
159     *** For scsi devices that the mid level tries to scan but do not
172     LLD                      mid level                 LLD
182 by the mid-level.  struct Scsi_Host instances are freed from
187 counting logic is being introduced into the mid level to cope with many
195 An LLD can use this sequence to make the mid level aware of a SCSI device::
198     LLD                   mid level                    LLD
209 probably cause that device to be set offline by the mid level. An LLD that
214     LLD                      mid level                 LLD
222 sdev_configure() callbacks). Such instances are "owned" by the mid-level.
231 were exclusively owned by the mid level. LLDs would not usually need to
253 were exclusively owned by the mid level. See the access functions declared
283 Mid level supplied functions
285 These functions are supplied by the SCSI mid level for use by LLDs.
288 arrange for the SCSI mid level to be loaded and initialized before any LLD
519     *      mid level itself don't need to call this, but there should be
594 should be passed to the mid level's scsi_host_alloc().
796     *      the 'cmd' then it is passed to the SCSI mid level. If the SCSI
797     *      mid level does not recognize it, then the LLD that controls
849     *      On both of these returns, the mid-layer will requeue the I/O
896     *      callback is not invoked within a certain period the SCSI mid
902     *      the mid level queuing a command to an LLD.
923     *      exist but the mid level is just about to scan for it (i.e. send
968     *      Notes: Mid level structures for given device are still in place
1002 		 - primary callback that the mid level uses to inject
1077 back to the mid level. The SCSI mid level will ensure that no more SCSI
1103                    then the mid level will assume the sense_buffer array
1104                    contains a valid SCSI sense buffer; otherwise the mid
1153 operations performed by the mid level use the struct Scsi_Host::host_lock
1170 Either way, when a status of CHECK CONDITION is detected, the mid level
1174 this byte is initialized to 0 before each command) then the mid level will