Home
last modified time | relevance | path

Searched full:responder (Results 1 – 25 of 71) sorted by relevance

123

/linux/include/scsi/fc/
H A Dfc_fc2.h35 __be16 ssb_rx_id; /* responder's exchange ID */
49 #define SSB_ST_RESP (1 << 15) /* sequence responder */
76 __be16 esb_rx_id; /* responder exchange ID */
78 __be32 esb_resp_fid; /* fabric ID of responder */
94 #define ESB_ST_RESP (1 << 31) /* responder to exchange */
108 #define ESB_ST_RX_ID_INVL (1 << 22) /* responder XID invalid */
/linux/drivers/infiniband/hw/hfi1/
H A Dopfn.h37 * receives a request with Bit 24 of BTH1 set. The responder QP
40 * existing requests on the responder QP side have been sent.
42 * keep a copy of the responder QP's parameters, and return a
43 * response packet with its own local parameters. The responder
/linux/drivers/fsi/
H A DKconfig66 tristate "IBM I2C Responder virtual FSI master"
70 behind an IBM I2C Responder (I2CR) chip. The I2CR is an I2C device
98 tristate "IBM I2C Responder SCOM driver"
101 This option enables an I2C Responder based SCOM device driver. The
H A Di2cr-scom.c153 MODULE_DESCRIPTION("IBM I2C Responder SCOM driver");
/linux/Documentation/arch/parisc/
H A Ddebugging.rst24 the System Responder/Requestor addresses. The System Requestor
26 the I/O range); the System Responder address is the address real-mode
29 Typical values for the System Responder address are addresses larger
/linux/Documentation/devicetree/bindings/fsi/
H A Dibm,i2cr-fsi-master.yaml7 title: IBM I2C Responder virtual FSI master
13 The I2C Responder (I2CR) is a an I2C device that's connected to an FSI CFAM
/linux/drivers/net/wireless/ralink/rt2x00/
H A Drt2400pci.h305 * AUTORESPONDER: Enable auto responder which include ack & cts.
351 * TXCSR7: Auto responder control register.
352 * AR_POWERMANAGEMENT: Auto responder power management bit.
425 * ARCSR0: Auto Responder PLCP config register 0.
426 * ARCSR0_AR_BBP_DATA#: Auto responder BBP register # data.
427 * ARCSR0_AR_BBP_ID#: Auto responder BBP register # Id.
436 * ARCSR1: Auto Responder PLCP config register 1.
437 * ARCSR0_AR_BBP_DATA#: Auto responder BBP register # data.
438 * ARCSR0_AR_BBP_ID#: Auto responder BBP register # Id.
H A Drt2500pci.h382 * AUTORESPONDER: Enable auto responder which include ack & cts.
428 * TXCSR7: Auto responder control register.
429 * AR_POWERMANAGEMENT: Auto responder power management bit.
526 * ARCSR1: Auto Responder PLCP config register 1.
527 * AR_BBP_DATA#: Auto responder BBP register # data.
528 * AR_BBP_ID#: Auto responder BBP register # Id.
/linux/drivers/net/ethernet/qlogic/qed/
H A Dqed_roce.c247 "qed create responder failed: cannot allocate memory (irq). rc = %d\n", in qed_roce_sp_create_responder()
352 DP_NOTICE(p_hwfn, "create responder - failed, rc = %d\n", rc); in qed_roce_sp_create_responder()
573 DP_VERBOSE(p_hwfn, QED_MSG_RDMA, "Modify responder, rc = %d\n", rc); in qed_roce_sp_modify_responder()
684 /* If a responder was never offload, we need to free the cids in qed_roce_sp_destroy_qp_responder()
718 "qed destroy responder failed: cannot allocate memory (ramrod). rc = %d\n", in qed_roce_sp_destroy_qp_responder()
740 DP_VERBOSE(p_hwfn, QED_MSG_RDMA, "Destroy responder, rc = %d\n", rc); in qed_roce_sp_destroy_qp_responder()
843 "The responder's qp should be offloaded before requester's\n"); in qed_roce_query_qp()
847 /* Send a query responder ramrod to FW to get RQ-PSN and state */ in qed_roce_query_qp()
1003 /* Send modify responder ramrod */ in qed_roce_modify_qp()
1061 /* Send destroy responder ramrod */ in qed_roce_modify_qp()
[all …]
H A Dqed_rdma.h140 /* responder */
/linux/include/drm/bridge/
H A Dmhl.h213 MHL_WRITE_BURST = 0x6C, /* Write 1-16 bytes to responder's scratchpad */
260 #define MHL_RAPK_BUSY 0x03 /* Responder too busy to respond */
273 /* Responder busy. Initiator may retry message */
283 /* Responder busy. Initiator may retry message */
/linux/Documentation/networking/device_drivers/ethernet/cirrus/
H A Dcs89x0.rst473 configured as a Responder and the other PC is configured as an Initiator.
474 Once the Initiator is started, it sends data frames to the Responder which
485 connection to act as the Responder. Run the CS8900/20 Setup Utility
486 and select 'Diagnostics -> Network Test -> Responder' from the main
487 menu. Hit ENTER to start the Responder.
495 You may stop the test on the Initiator at any time while allowing the Responder
498 Responder.
/linux/include/uapi/scsi/fc/
H A Dfc_fs.h36 __be16 fh_rx_id; /* responder exchange ID */
208 #define FC_FC_EX_CTX (1 << 23) /* sent by responder to exchange */
209 #define FC_FC_SEQ_CTX (1 << 22) /* sent by responder to sequence */
306 FC_RJT_RX_ID = 0x0c, /* invalid responder exchange ID */
/linux/drivers/scsi/bfa/
H A Dbfa_fc.h62 u16 rx_id; /* responder exchange ID */
135 FCTL_EC_RESP = 0x800000, /* exchange responder */
389 u32 resp_np:24; /* responder NPortID */
428 #define FC_REC_ESB_OWN_RSP 0x80000000 /* responder owns */
448 u32 resp_id:24; /* N_Port id of exchange responder */
550 u32 rpa_valid:1; /* responder process associator valid */
554 u32 rpa_valid:1; /* responder process associator valid */
582 u32 rpa_valid:1; /* responder process associator valid */
586 u32 rpa_valid:1; /* responder process associator valid */
698 u32 rx_id:16; /* responder exchange ID */
/linux/drivers/net/wireless/intel/iwlwifi/mvm/
H A Dftm-responder.c93 /* Up to 2 R2I STS are allowed on the responder */ in iwl_mvm_ftm_responder_set_ndp()
167 IWL_ERR(mvm, "Failed to set responder bandwidth\n"); in iwl_mvm_ftm_responder_cmd()
346 IWL_ERR(mvm, "Cannot start responder, not in AP mode\n"); in iwl_mvm_ftm_start_responder()
H A DMakefile9 iwlmvm-y += ftm-responder.o ftm-initiator.o
/linux/tools/testing/selftests/net/netfilter/
H A Dnft_flowtable.sh7 # Originator (MTU 9000) <-Router1-> MTU 1500 <-Router2-> Responder (MTU 2000)
10 # and responder, i.e. TCPMSS announced values are too large and will still
13 # You can check with different Orgininator/Link/Responder MTU eg:
84 echo " -r responder"
139 echo "ERROR: Check Originator/Responder values (problem during address addition)"
/linux/net/can/j1939/
H A Dj1939-priv.h272 * responder should send ETP.CM_CTS and originator
277 * this counter can be set back if responder node
/linux/Documentation/peci/
H A Dpeci.rst14 a PECI responder.
/linux/include/acpi/
H A Dpcc.h60 /* Initiator Responder Communications Channel Flags */
/linux/include/linux/
H A Dpeci.h99 * a response received from PECI responder (RX).
/linux/Documentation/infiniband/
H A Dtag_matching.rst37 corresponding buffer is posted, the responder will use the information from
/linux/include/uapi/linux/
H A Dgsmmux.h34 * @initiator: Initiator or responder
/linux/drivers/target/tcm_fc/
H A Dtfc_cmd.c208 /* Only if it is 'Exchange Responder' */ in ft_write_pending()
210 /* Target is 'exchange responder' and sending XFER_READY in ft_write_pending()
/linux/drivers/net/wireless/intel/iwlwifi/fw/api/
H A Ddhc.h198 * @negotiation_type: if the responder wants to doze outside the TWT SP

123