Lines Matching refs:command

163 I/O command completed without error (this is called 'Fast Posting'
206 Fibre Channel) to a SCSI device. It's assumed that each SCSI command is
230  + A SCSI command queueing entry point (isp_start)
248 down DMA mappings for a SCSI command, provide a pointer to firmware to
254  + A SCSI command completion handoff point (isp_done)
267 	XS_T            Platform SCSI transaction type (i.e., command for HBA)
290 boards initialization and command transactions may help.
331 will call when it has a SCSI command to run.
334 it needs to to prepare this command for execution in the core module. This
336 a complete marshalling/demarshalling of this platform's SCSI command
339 Channel loop state would preclude successful starting of the command).
342 command. This core module tries to allocate request queue space for
343 this command. It also calls through the machine dependent vector
344 function to make sure any DMA mapping for this command is done.
350 DMA addresses for any command may in fact consume more Request Queue
364 active command. When you send a command to the QLogic firmware, a portion
368 handle to find the command you were waiting on. It should be noted that
374 of the interrupt is, and if it is for a completing command. That is,
375 it'll determine the handle and fetch the pointer to the command out of
378 pointer to the completing command. This would then be the glue layer that
379 informs the SCSI subsystem for this platform that a command is complete.
402 queue entry element defining a new command arriving from an initiator.
411 Queue and handled very much like an initiator mode command (i.e., calling
413 command, no more need occur. But often this handles only part of the
414 requested command, so the QLogic firmware will rewrite the response
416 target mode handler will respond to that, and so on until the command
455 for disabling it's usage on a per-command basis.
467 sending a command (Initialize Control Block) that establishes Node
484 Clearly, no command should be attempted prior to FW_READY state is
552 is indexed directly via the Target ID for the command (XS_TGT(xs)).
554 If there is a valid entry for this Target ID, the command is started
555 (with the stored 'Loop ID'). If not the command is completed with