From: Tom Evans <tom_usenet@optusnet.com.au>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org, kernel@pengutronix.de, david@protonic.nl
Subject: Re: [PATCH 0/8] RFC: more flexcan cleanups and SW FIFO IRQ offloading
Date: Thu, 3 Sep 2015 09:58:58 +1000 [thread overview]
Message-ID: <55E78D42.1060109@optusnet.com.au> (raw)
In-Reply-To: <1441103522-15593-1-git-send-email-mkl@pengutronix.de>
On 01/09/15 20:31, Marc Kleine-Budde wrote:
> Hello,
>
> this series adds a software FIFO implementation and switches
> the flecan and at91 driver to it. It's intended for CAN cores
> with a higher number of mailboxes.
It is a bit difficult to understand the changed by looking at 20 patches, so
I'm assuming this is the change where what the i.MX6 manuals calls the
"Reception Queue" mode is enabled.
I see "[PATCH 1/8]" renaming "FLEXCAN_MCR_BCC" to "FLEXCAN_MCR_IRMQ" and
"[PATCH 2/8]" adding it to the MCR setting.
Use of the "Reception Queue" is documented in the i.MX6DQ manual in section
"26.6.5 Matching Process" as:
By programming more than one MB with the same ID, received
messages will be queued into the MBs. ARM can examine the
Time Stamp field of the MBs to determine the order in which
the messages arrived.
Is the new code sorting the messages by using the timestamp, or have you found
another way to guarantee reception order?
Tom
next prev parent reply other threads:[~2015-09-02 23:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 10:31 [PATCH 0/8] RFC: more flexcan cleanups and SW FIFO IRQ offloading Marc Kleine-Budde
2015-09-01 10:31 ` [PATCH 1/8] can: flexcan: add missing register definitions Marc Kleine-Budde
2015-09-01 10:31 ` [PATCH 2/8] can: flexcan: activate individual RX masking and initialize reg_rximr Marc Kleine-Budde
2015-09-01 10:31 ` [PATCH 3/8] can: flexcan: add quirk FLEXCAN_QUIRK_ENABLE_EACEN_RRS Marc Kleine-Budde
2015-09-01 10:31 ` [PATCH 4/8] can: flexcan: reg_imask2_default Marc Kleine-Budde
2015-09-01 10:31 ` [PATCH 5/8] can: rx-fifo: introduce software rx-fifo implementation Marc Kleine-Budde
2015-09-01 10:32 ` [PATCH 6/8] can: flexcan: add support for rx-fifo based software FIFO implementation Marc Kleine-Budde
2015-09-01 10:32 ` [PATCH 7/8] can: flexcan: switch imx6 and vf610 to software based fifo Marc Kleine-Budde
2015-09-01 10:32 ` [PATCH 8/8] can: at91_can: switch to rx-fifo implementation Marc Kleine-Budde
2015-09-02 23:58 ` Tom Evans [this message]
2015-09-03 6:32 ` [PATCH 0/8] RFC: more flexcan cleanups and SW FIFO IRQ offloading David Jander
2015-09-03 6:58 ` Marc Kleine-Budde
2015-09-03 8:17 ` Tom Evans
2015-09-03 8:38 ` David Jander
2015-09-03 8:47 ` Marc Kleine-Budde
2015-09-04 3:19 ` Tom Evans
2015-09-03 8:45 ` Marc Kleine-Budde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55E78D42.1060109@optusnet.com.au \
--to=tom_usenet@optusnet.com.au \
--cc=david@protonic.nl \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).