scsi_report_opcode(9) [centos man page]

SCSI_REPORT_OPCODE(9)						  SCSI mid layer					     SCSI_REPORT_OPCODE(9)

NAME

       scsi_report_opcode - Find out if a given command opcode is supported

SYNOPSIS

       int scsi_report_opcode(struct scsi_device * sdev, unsigned char * buffer, unsigned int len, unsigned char opcode);

ARGUMENTS

       sdev
	   scsi device to query

       buffer
	   scratch buffer (must be at least 20 bytes long)

       len
	   length of buffer

       opcode
	   opcode for command to look up

DESCRIPTION

       Uses the REPORT SUPPORTED OPERATION CODES to look up the given opcode. Returns -EINVAL if RSOC fails, 0 if the command opcode is
       unsupported and 1 if the device claims to support the command.

AUTHORS

       James Bottomley <James.Bottomley@hansenpartnership.com>
	   Author.

       Rob Landley <rob@landley.net>
	   Author.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						     SCSI_REPORT_OPCODE(9)

FC_REMOTE_PORT_ADD(9)						  SCSI mid layer					     FC_REMOTE_PORT_ADD(9)

NAME

       fc_remote_port_add - notify fc transport of the existence of a remote FC port.

SYNOPSIS

       struct fc_rport * fc_remote_port_add(struct Scsi_Host * shost, int channel, struct fc_rport_identifiers * ids);

ARGUMENTS

       shost
	   scsi host the remote port is connected to.

       channel
	   Channel on shost port connected to.

       ids
	   The world wide names, fc address, and FC4 port roles for the remote port.

DESCRIPTION

       The LLDD calls this routine to notify the transport of the existence of a remote port. The LLDD provides the unique identifiers (wwpn,wwn)
       of the port, it's FC address (port_id), and the FC4 roles that are active for the port.

       For ports that are FCP targets (aka scsi targets), the FC transport maintains consistent target id bindings on behalf of the LLDD. A
       consistent target id binding is an assignment of a target id to a remote port identifier, which persists while the scsi host is attached.
       The remote port can disappear, then later reappear, and it's target id assignment remains the same. This allows for shifts in FC addressing
       (if binding by wwpn or wwnn) with no apparent changes to the scsi subsystem which is based on scsi host number and target id values.
       Bindings are only valid during the attachment of the scsi host. If the host detaches, then later re-attaches, target id bindings may
       change.

       This routine is responsible for returning a remote port structure. The routine will search the list of remote ports it maintains internally
       on behalf of consistent target id mappings. If found, the remote port structure will be reused. Otherwise, a new remote port structure will
       be allocated.

       Whenever a remote port is allocated, a new fc_remote_port class device is created.

       Should not be called from interrupt context.

NOTES

       This routine assumes no locks are held on entry.

AUTHORS

       James Bottomley <James.Bottomley@hansenpartnership.com>
	   Author.

       Rob Landley <rob@landley.net>
	   Author.

COPYRIGHT

Kernel Hackers Manual 2.6.					     July 2010						     FC_REMOTE_PORT_ADD(9)