Home
last modified time | relevance | path

Searched refs:ival2 (Results 1 – 3 of 3) sorted by relevance

/Linux-v6.1/net/can/
Dbcm.c108 struct bcm_timeval ival1, ival2; member
158 (msg_head->ival2.tv_sec < 0) || in bcm_is_invalid_tv()
159 (msg_head->ival2.tv_sec > BCM_TIMER_SEC_MAX) || in bcm_is_invalid_tv()
160 (msg_head->ival2.tv_usec < 0) || in bcm_is_invalid_tv()
161 (msg_head->ival2.tv_usec >= USEC_PER_SEC)) in bcm_is_invalid_tv()
416 msg_head.ival2 = op->ival2; in bcm_tx_timeout_handler()
454 head.ival2 = op->ival2; in bcm_rx_changed()
576 msg_head.ival2 = op->ival2; in bcm_rx_timeout_handler()
848 msg_head->ival2 = op->ival2; in bcm_read_op()
1004 op->ival2 = msg_head->ival2; in bcm_tx_setup()
[all …]
/Linux-v6.1/include/uapi/linux/can/
Dbcm.h71 struct bcm_timeval ival1, ival2; member
/Linux-v6.1/Documentation/networking/
Dcan.rst740 struct timeval ival1, ival2; /* count and subsequent interval */
843 Set the values of ival1, ival2 and count
846 Start the timer with the actual values of ival1, ival2
888 'ival1', then continuing to send at another given interval 'ival2'. When
889 only one timer is needed 'count' is set to zero and only 'ival2' is used.
923 The timer values ival1 or ival2 may be set to non-zero values at RX_SETUP.
931 ival2:
932 Throttle the received message rate down to the value of ival2. This
934 CAN frame is stateless as state changes within the ival2 periode may get