mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 10:59:07 +0100	[thread overview]
Message-ID: <6df4a9ae-eaba-6f3f-9c23-ae269548b005@grandegger.com> (raw)
In-Reply-To: <2197294b-e6cf-6c56-1419-3a4f95c29db7@timesys.com>

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?

Thanks,

Wolfgang.

Am 07.03.2017 um 16:31 schrieb Akshay Bhat:
>
>
> On 01/17/2017 02:22 PM, Akshay Bhat wrote:
>> This patch adds support for the Holt HI-311x CAN controller. The HI311x
>> CAN controller is capable of transmitting and receiving standard data
>> frames, extended data frames and remote frames. The HI311x interfaces
>> with the host over SPI.
>>
>> Datasheet: www.holtic.com/documents/371-hi-3110_v-rev-jpdf.do
>>
>> Signed-off-by: Akshay Bhat <nodeax@gmail.com>
>> ---
>>
>
>
> Hi Marc,
>
> Wanted to check if this patch can be included in the next kernel release
> (4.12).
>
> Thanks,
> Akshay
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>

  reply	other threads:[~2017-03-09 10:08 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 [this message]
2017-03-09 12:34       ` Akshay Bhat
2017-03-09 14:45         ` Wolfgang Grandegger
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=6df4a9ae-eaba-6f3f-9c23-ae269548b005@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®