David Jander
2014-08-27 09:58:04 UTC
This patch series actually fixes 3 related issues, greatly improving
resilence under high latency conditions (e.g. non-real-time kernels).
This reduces the likelyhood of receive underruns when many back-to-back
messages are received at high bitrates.
The first patch is actually a fix to a bug that causes overruns being missed.
The second patch swaps the use of the RX FIFO for using the whole MB area
as a receive buffer and off-loading this buffer area directly in the IRQ-
handler.
The last patch is part of the implementation of errata ERR005829 for the
flexcan peripheral in i.MX6 SoCs. The first steps of this errata workaround
are implicitely included in patch 2 already.
David Jander (3):
can: flexcan.c: Correctly initialize mailboxes
can: flexcan.c: Re-write receive path to use MB queue instead of FIFO
can: flexcan.c: Implement last step of workaround for errata ERR005829
--
To unsubscribe from this list: send the line "unsubscribe linux-can" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
resilence under high latency conditions (e.g. non-real-time kernels).
This reduces the likelyhood of receive underruns when many back-to-back
messages are received at high bitrates.
The first patch is actually a fix to a bug that causes overruns being missed.
The second patch swaps the use of the RX FIFO for using the whole MB area
as a receive buffer and off-loading this buffer area directly in the IRQ-
handler.
The last patch is part of the implementation of errata ERR005829 for the
flexcan peripheral in i.MX6 SoCs. The first steps of this errata workaround
are implicitely included in patch 2 already.
David Jander (3):
can: flexcan.c: Correctly initialize mailboxes
can: flexcan.c: Re-write receive path to use MB queue instead of FIFO
can: flexcan.c: Implement last step of workaround for errata ERR005829
--
To unsubscribe from this list: send the line "unsubscribe linux-can" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html