Searched refs:RTR (Results 1 – 7 of 7) sorted by relevance
10 On/off RTR frames reception19 and i.MX53 SOCs) only receive RTR frames if the controller is27 As reception of RTR frames is part of the CAN standard, all flexcan28 cores come up in a mode where RTR reception is possible.30 With the "rx-rtr" private flag the ability to receive RTR frames can31 be waived at the expense of losing the ability to receive RTR35 Receive RTR frames. (default)37 The CAN controller can and will receive RTR frames.39 On some IP cores the controller cannot receive RTR frames in the45 Waive ability to receive RTR frames. (not supported on all IP cores)[all …]
13 …d, uint8_t sgid_idx, uint32_t dqpn, uint32_t rq_psn) "RC QP 0x%x switch to RTR, subnet = 0x%"PRIx6…14 rdma_backend_ud_qp_state_rtr(uint32_t qpn, uint32_t qkey) "UD QP 0x%x switch to RTR, qkey=0x%x"
202 Sending RTR frames is not supported and will be dropped silently.204 Receiving RTR with DLC 8 will appear to be a regular frame with226 The length of outgoing RTR frames cannot be set. In fact, some228 send RTR frames at all.258 on incoming data, as well as distinction of RTR frame lengths.319 We need this to tell the "length" of RTR frames.
38 sending of RTR frames, and cyclic CAN messages without permanent user
84 enum {START = 0, STOP, TO_GOOD, TO_BAD, RCR_GOOD, RCR_BAD, RCA, RCN, RTR, RTA, enumerator533 ppp_cp_event(dev, pid, RTR, 0, cp->id, 0, NULL); in ppp_rx()
149 FIELD(TXFIFO_ID, RTR, 0, 1)167 FIELD(TXHPB_ID, RTR, 0, 1)185 FIELD(RXFIFO_ID, RTR, 0, 1)
237 canid_t can_id; /* 32 bit CAN_ID + EFF/RTR/ERR flags */414 canid_t can_id; /* 32 bit CAN_ID + EFF/RTR/ERR flags */878 Send reply for RTR-request (placed in op->frames[0]).