All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: bruce bushby <bruce.bushby@gmail.com>
Cc: Linux-CAN <linux-can@vger.kernel.org>
Subject: Re: [Socketcan-users] AM335x CAN/D_CAN
Date: Tue, 22 May 2012 21:01:06 +0200	[thread overview]
Message-ID: <4FBBE272.5020807@grandegger.com> (raw)
In-Reply-To: <CAHvj1qbb9YJSBLZc1bG6MpEJcjPUtr+37wn3iJUNm_OmpH2SgA@mail.gmail.com>

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.

> http://www.spinics.net/lists/linux-omap/msg67538.html
> Does D_CAN have anything to do with mcp2515?

No, nothing apart from the fact that both are CAN controllers. The
mcp2515 is connected via SPI bus and from another company.

> In order to connect the am335x CAN line to a CAN bus, would I need to
> add a CAN transceiver?

Hardware-wise, yes.

> Is the am335x an "in memory CAN" ... ie I wouldn't need to worry about
> SPI bus performance?

Right. On the AM335x, the D_CAN controller is integrated into the SOC.
There is no SPI involved.

> Any explanations and help much appreciated!

Hope it's useful.

Wolfgang.

       reply	other threads:[~2012-05-22 19:01 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 ` Wolfgang Grandegger [this message]
2012-05-23  6:56   ` [Socketcan-users] AM335x CAN/D_CAN AnilKumar, Chimata
2012-05-23  7:01     ` Wolfgang Grandegger
2012-05-23  7:05       ` Marc Kleine-Budde
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=4FBBE272.5020807@grandegger.com \
    --to=wg@grandegger.com \
    --cc=bruce.bushby@gmail.com \
    --cc=linux-can@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.