From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Wolfgang Grandegger <wg@grandegger.com>
Cc: "AnilKumar, Chimata" <anilkumar@ti.com>,
bruce bushby <bruce.bushby@gmail.com>,
Linux-CAN <linux-can@vger.kernel.org>
Subject: Re: [Socketcan-users] AM335x CAN/D_CAN
Date: Wed, 23 May 2012 09:05:09 +0200 [thread overview]
Message-ID: <4FBC8C25.3050107@pengutronix.de> (raw)
In-Reply-To: <4FBC8B5D.7000302@grandegger.com>
[-- Attachment #1: Type: text/plain, Size: 1947 bytes --]
On 05/23/2012 09:01 AM, Wolfgang Grandegger wrote:
> On 05/23/2012 08:56 AM, AnilKumar, Chimata wrote:
>> Hi Wolfgang,
>>
>> On Wed, May 23, 2012 at 00:31:06, Wolfgang Grandegger wrote:
>>> Hello,
>>>
>>> I switched the discussion to the new Linux-CAN mailing list.
>>>
>>> On 05/22/2012 05:50 PM, bruce bushby wrote:
>>>> Greetings
>>>>
>>>> I'm hoping a list member would be so kind as to offer some basic
>>>> explanations of how one would use the CAN bus provided by AM335x. I
>>>> understand Linux, but struggle with electronics.
>>>>
>>>> I have read this discussion: http://comments.gmane.org/gmane.linux.can/1142
>>>> What is the difference between C_CAN and D_CAN?
>>>
>>> As I see it, the D_CAN is a more advanced variant of the C_CAN
>>> controller. See also:
>>>
>>> http://www.semiconductors.bosch.de/en/ipmodules/can/canipmodules/c_can/c_can.asp
>>> http://www.semiconductors.bosch.de/en/ipmodules/can/canipmodules/d_can/d_can.asp
>>>
>>> Patches to add D_CAN support to the Linux-CAN C_CAN driver have been
>>> posted recently for mainline inclusion and are currently reviewed.
>>
>> Is there a possibility of pushing my driver into 3.5 kernel?
>
> Yes, I think we should push it forward, even if the C_CAN part remains
> untested for the moment. IIRC, the patch series is already in a good
> shape. I personally do also not have a board with a C_CAN controller at
> hand. Marc, what is your opinion?
I don't have any of the *_CAN hardware. But the driver looks quite good.
I'm quite busy at the moment, but currently we've the merge window. I'll
do a review now, anyway. Wolfgang can I have your Acked-by?
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-05-23 7:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHvj1qbb9YJSBLZc1bG6MpEJcjPUtr+37wn3iJUNm_OmpH2SgA@mail.gmail.com>
2012-05-22 19:01 ` [Socketcan-users] AM335x CAN/D_CAN Wolfgang Grandegger
2012-05-23 6:56 ` AnilKumar, Chimata
2012-05-23 7:01 ` Wolfgang Grandegger
2012-05-23 7:05 ` Marc Kleine-Budde [this message]
2012-05-23 8:06 ` Wolfgang Grandegger
2012-05-23 8:27 ` AnilKumar, Chimata
2012-05-23 8:40 ` Wolfgang Grandegger
2012-05-23 8:07 ` Robert Schwebel
2012-05-23 8:08 ` Marc Kleine-Budde
2012-05-23 8:10 ` Robert Schwebel
2012-06-19 7:58 ` bruce bushby
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=4FBC8C25.3050107@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=anilkumar@ti.com \
--cc=bruce.bushby@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=wg@grandegger.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;
as well as URLs for NNTP newsgroup(s).