linux-toradex.git/drivers/net/can/rx-offload.c, branch v5.0 Linux kernel for Apalis and Colibri modules can: rx-offload: rename can_rx_offload_irq_queue_err_skb() to can_rx_offload_queue_tail() 2018-11-09T16:33:32+00:00 Oleksij Rempel o.rempel@pengutronix.de 2018-09-18T09:40:40+00:00 4530ec36bb1e0d24f41c33229694adacda3d5d89 This function has nothing todo with error. Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de> Cc: linux-stable <stable@vger.kernel.org> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de> 
This function has nothing todo with error.

Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: linux-stable <stable@vger.kernel.org>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
can: rx-offload: introduce can_rx_offload_get_echo_skb() and can_rx_offload_queue_sorted() functions 2018-11-09T16:20:49+00:00 Oleksij Rempel o.rempel@pengutronix.de 2018-09-18T09:40:38+00:00 55059f2b7f868cd43b3ad30e28e18347e1b46ace Current CAN framework can't guarantee proper/chronological order of RX and TX-ECHO messages. To make this possible, drivers should use this functions instead of can_get_echo_skb(). Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de> Cc: linux-stable <stable@vger.kernel.org> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de> 
Current CAN framework can't guarantee proper/chronological order
of RX and TX-ECHO messages. To make this possible, drivers should use
this functions instead of can_get_echo_skb().

Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: linux-stable <stable@vger.kernel.org>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
can: Remove SKB list assumptions in rx-offload.c 2018-09-10T17:06:54+00:00 David S. Miller davem@davemloft.net 2018-08-22T23:43:34+00:00 6effee6840af7d1adfde296f987b3d3213b3037d Eliminate code which assumes that SKBs and skb_queue_head objects can be cast to eachother during list processing. Signed-off-by: David S. Miller <davem@davemloft.net> 
Eliminate code which assumes that SKBs and skb_queue_head objects
can be cast to eachother during list processing.

Signed-off-by: David S. Miller <davem@davemloft.net>
can: rx-offload: can_rx_offload_add_timestamp: remove duplicate semicolon at return statement 2018-01-05T10:12:08+00:00 Marc Kleine-Budde mkl@pengutronix.de 2017-12-06T13:19:08+00:00 41e0a3fd5121706d209e6f469a0a4c4847ad37c0 This patch removes the duplicate semicolon at the end of the return statement. Suggested-by: Oleksij Rempel <o.rempel@pengutronix.de> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de> 
This patch removes the duplicate semicolon at the end of the return
statement.

Suggested-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
can: rx-offload: Add support for timestamp based irq offloading 2017-02-06T14:13:24+00:00 Marc Kleine-Budde mkl@pengutronix.de 2014-09-23T13:28:21+00:00 3abbac0b5dd3e3b3dfb30a4885cdde5c20e1cb83 Some CAN controllers don't implement a FIFO in hardware, but fill their mailboxes in a particular order (from lowest to highest or highest to lowest). This makes problems to read the frames in the correct order from the hardware, as new frames might be filled into just read (low) mailboxes. This gets worse, when following new frames are received into not read (higher) mailboxes. On the bright side some these CAN controllers put a timestamp on each received CAN frame. This patch adds support to offload CAN frames in interrupt context, order them by timestamp and then transmitted in a NAPI context. Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de> 
Some CAN controllers don't implement a FIFO in hardware, but fill their
mailboxes in a particular order (from lowest to highest or highest to lowest).
This makes problems to read the frames in the correct order from the hardware,
as new frames might be filled into just read (low) mailboxes. This gets worse,
when following new frames are received into not read (higher) mailboxes.

On the bright side some these CAN controllers put a timestamp on each received
CAN frame. This patch adds support to offload CAN frames in interrupt context,
order them by timestamp and then transmitted in a NAPI context.

Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
can: rx-offload: Add support for HW fifo based irq offloading 2017-02-06T14:13:23+00:00 David Jander david@protonic.nl 2014-10-10T15:30:10+00:00 d254586c34538c0014280806c5d4795697cf21e5 Some CAN controllers have a usable FIFO already but can still benefit from off-loading the CAN controller FIFO. The CAN frames of the FIFO are read and put into a skb queue during interrupt and then transmitted in a NAPI context. Signed-off-by: David Jander <david@protonic.nl> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de> 
Some CAN controllers have a usable FIFO already but can still benefit
from off-loading the CAN controller FIFO. The CAN frames of the FIFO are
read and put into a skb queue during interrupt and then transmitted in a
NAPI context.

Signed-off-by: David Jander <david@protonic.nl>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>