From: Wolfgang Grandegger <wg@grandegger.com>
To: Akshay Bhat <akshay.bhat@timesys.com>, mkl@pengutronix.de
Cc: linux-can@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Akshay Bhat <nodeax@gmail.com>
Subject: Re: [PATCH v2 2/2] can: spi: hi311x: Add Holt HI-311x CAN driver
Date: Thu, 9 Mar 2017 15:45:15 +0100 [thread overview]
Message-ID: <a9cb37d9-a71e-ce59-c379-d9bde5d8afb9@grandegger.com> (raw)
In-Reply-To: <1447da4a-6a36-38fb-4298-fd7488697d11@timesys.com>
Hello Akshay,
Am 09.03.2017 um 13:34 schrieb Akshay Bhat:
>
>
> On 03/09/2017 04:59 AM, Wolfgang Grandegger wrote:
>> Hello Akshay,
>>
>> unfortunately there are not many CAN controllers for the SPI bus. I just
>> know the MPC251x, which behaves badly (message losses) under Linux,
>> especially at hight bit-rates due to insufficient RX buffering. What is
>> your experience with that driver for the HI-311x?
>>
>
> Hi Wolfgang,
>
> Good question. I have not worked with MPC251x but the HI-311x performs
> much better because HI-3110 features:
> 8 message FIFO (as opposed to 2 buffers on MPC2510)
> 20 MHz SPI interface (as opposed to 2.5 MHz on MPC2510)
>
> As for the real world test results:
>
> With RT patch applied to the kernel running on a i.MX6 Dual processor
> (worst case interrupt latency of 50us as reported by cyclictest), there
> are ZERO packet drops.
> Tested with Kvaser Leaf sending 100 burst messages (back to back) every
> 40ms at a 1M CAN bit rate. 10 million messages were sent by the Kvaser
> leaf and received successfully by the HI-311x driver.
This corresponds to a bus load of approx. 50%, I think?
> Even without the RT patch, I was able to get the packet drop to zero but
> this was by moving the CAN/SPI IRQ threads to CPU1 instead of CPU0.
Vanilla Linux is more critical here due to higher latencies. With 2500
Messages per sec the RX FIFO (8 Messages) fills up within 3.2 ms... and
in a burst even quicker. That's already heavy load.
Wolfgang.
next prev parent reply other threads:[~2017-03-09 14:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 19:22 [PATCH v2 1/2] can: holt_hi311x: document device tree bindings Akshay Bhat
2017-01-17 19:22 ` [PATCH v2 2/2] can: spi: hi311x: Add Holt HI-311x CAN driver Akshay Bhat
2017-03-07 15:31 ` Akshay Bhat
2017-03-09 9:59 ` Wolfgang Grandegger
2017-03-09 12:34 ` Akshay Bhat
2017-03-09 14:45 ` Wolfgang Grandegger [this message]
2017-03-09 15:28 ` Akshay Bhat
2017-03-09 17:36 ` Wolfgang Grandegger
2017-03-13 15:38 ` Akshay Bhat
2017-03-14 12:11 ` Wolfgang Grandegger
2017-03-14 16:20 ` Akshay Bhat
2017-03-14 18:08 ` Wolfgang Grandegger
2017-03-14 21:23 ` Wolfgang Grandegger
2017-03-15 4:44 ` Akshay Bhat
2017-03-15 7:19 ` Wolfgang Grandegger
2017-03-15 9:42 ` Wolfgang Grandegger
2017-03-16 17:06 ` Akshay Bhat
2017-03-16 20:02 ` Wolfgang Grandegger
2017-03-16 22:29 ` Akshay Bhat
2017-03-17 7:39 ` Wolfgang Grandegger
2017-03-17 8:17 ` Wolfgang Grandegger
2017-03-17 16:00 ` Akshay Bhat
2017-03-17 17:04 ` Wolfgang Grandegger
2017-03-17 18:28 ` Akshay Bhat
2017-03-18 12:30 ` Wolfgang Grandegger
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=a9cb37d9-a71e-ce59-c379-d9bde5d8afb9@grandegger.com \
--to=wg@grandegger.com \
--cc=akshay.bhat@timesys.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=nodeax@gmail.com \
/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
all inboxes | Powered by JetHome®