| /kernel/linux/linux-5.10/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| D | location.h | 87 * @TOF_RESPONDER_CONFIG_CMD: FTM responder configuration,
111 * @TOF_RESPONDER_STATS: FTM responder statistics notification,
180 * enum iwl_tof_responder_cmd_valid_field - valid fields in the responder cfg
217 * enum iwl_tof_responder_cfg_flags - responder configuration flags
316 * struct iwl_tof_responder_dyn_config_cmd - Dynamic responder settings
348 * struct iwl_tof_responder_dyn_config_cmd - Dynamic responder settings
428 * 1: Initiator interact with Responder machine: need to send the
429 * Initiator Acks with HT 40MHz / 80MHz, since the Responder should
431 * configure the opposite machine to be Responder).
460 * enum iwl_initiator_ap_flags - per responder FTM configuration flags
[all …]
|
| /kernel/linux/linux-5.10/include/scsi/fc/ |
| D | fc_fc2.h | 35 __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 */
|
| /kernel/linux/linux-6.6/include/scsi/fc/ |
| D | fc_fc2.h | 35 __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 */
|
| /kernel/linux/linux-6.6/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| D | location.h | 38 * @TOF_RESPONDER_CONFIG_CMD: FTM responder configuration, one of
65 * @TOF_RESPONDER_STATS: FTM responder statistics notification,
137 * enum iwl_tof_responder_cmd_valid_field - valid fields in the responder cfg
188 * enum iwl_tof_responder_cfg_flags - responder configuration flags
396 * struct iwl_tof_responder_dyn_config_cmd - Dynamic responder settings
428 * struct iwl_tof_responder_dyn_config_cmd - Dynamic responder settings
508 * 1: Initiator interact with Responder machine: need to send the
509 * Initiator Acks with HT 40MHz / 80MHz, since the Responder should
511 * configure the opposite machine to be Responder).
540 * enum iwl_initiator_ap_flags - per responder FTM configuration flags
[all …]
|
| /kernel/linux/linux-5.10/drivers/infiniband/hw/hfi1/ |
| D | opfn.h | 37 * 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
|
| /kernel/linux/linux-6.6/drivers/fsi/ |
| D | Kconfig | 66 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
|
| /kernel/linux/linux-6.6/drivers/infiniband/hw/hfi1/ |
| D | opfn.h | 37 * 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
|
| /kernel/linux/linux-5.10/Documentation/parisc/ |
| D | debugging.rst | 24 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
|
| /kernel/linux/linux-6.6/Documentation/arch/parisc/ |
| D | debugging.rst | 24 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
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/fsi/ |
| D | ibm,i2cr-fsi-master.yaml | 7 title: IBM I2C Responder virtual FSI master
13 The I2C Responder (I2CR) is a an I2C device that's connected to an FSI CFAM
|
| /kernel/linux/linux-5.10/tools/testing/selftests/netfilter/ |
| D | nft_flowtable.sh | 7 # 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:
95 echo " -r responder"
140 echo "ERROR: Check Originator/Responder values (problem during address addition)"
172 # this allows large packets from responder, we need this as long
|
| /kernel/linux/linux-6.6/drivers/net/wireless/ralink/rt2x00/ |
| D | rt2400pci.h | 305 * 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.
|
| /kernel/linux/linux-5.10/drivers/net/wireless/ralink/rt2x00/ |
| D | rt2400pci.h | 305 * 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.
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/qlogic/qed/ |
| D | qed_roce.c | 247 "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()
844 "The responder's qp should be offloaded before requester's\n"); in qed_roce_query_qp()
848 /* Send a query responder ramrod to FW to get RQ-PSN and state */ in qed_roce_query_qp()
1004 /* Send modify responder ramrod */ in qed_roce_modify_qp()
1062 /* Send destroy responder ramrod */ in qed_roce_modify_qp()
[all …]
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/qlogic/qed/ |
| D | qed_roce.c | 247 "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 …]
|
| /kernel/linux/linux-6.6/include/drm/bridge/ |
| D | mhl.h | 213 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 */
|
| /kernel/linux/linux-5.10/include/drm/bridge/ |
| D | mhl.h | 213 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 */
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/cirrus/ |
| D | cs89x0.rst | 473 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.
|
| /kernel/linux/linux-6.6/Documentation/networking/device_drivers/ethernet/cirrus/ |
| D | cs89x0.rst | 473 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.
|
| /kernel/linux/linux-5.10/include/uapi/scsi/fc/ |
| D | fc_fs.h | 36 __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 */
|
| /kernel/linux/linux-6.6/include/uapi/scsi/fc/ |
| D | fc_fs.h | 36 __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 */
|
| /kernel/linux/linux-5.10/drivers/scsi/bfa/ |
| D | bfa_fc.h | 77 u16 rx_id; /* responder exchange ID */
150 FCTL_EC_RESP = 0x800000, /* exchange responder */
404 u32 resp_np:24; /* responder NPortID */
443 #define FC_REC_ESB_OWN_RSP 0x80000000 /* responder owns */
463 u32 resp_id:24; /* N_Port id of exchange responder */
565 u32 rpa_valid:1; /* responder process associator valid */
569 u32 rpa_valid:1; /* responder process associator valid */
597 u32 rpa_valid:1; /* responder process associator valid */
601 u32 rpa_valid:1; /* responder process associator valid */
713 u32 rx_id:16; /* responder exchange ID */
|
| /kernel/linux/linux-6.6/drivers/scsi/bfa/ |
| D | bfa_fc.h | 62 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 */
|
| /kernel/linux/linux-6.6/tools/testing/selftests/netfilter/ |
| D | nft_flowtable.sh | 7 # 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:
96 echo " -r responder"
140 echo "ERROR: Check Originator/Responder values (problem during address addition)"
|
| /kernel/linux/linux-5.10/drivers/net/wireless/intel/iwlwifi/mvm/ |
| D | Makefile | 8 iwlmvm-y += ftm-responder.o ftm-initiator.o
|