From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Wolfgang Grandegger <wg@grandegger.com>
Cc: AnilKumar Ch <anilkumar@ti.com>,
socketcan@hartkopp.net, m.kleine-budde@pengutronix.de,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
anantgole@ti.com, nsekhar@ti.com
Subject: Re: [PATCH] ARM: OMAP: AM33XX: CAN: d_can: Add support for Bosch D_CAN controller
Date: Tue, 03 Apr 2012 14:49:48 +0200 [thread overview]
Message-ID: <4F7AF1EC.1060802@pengutronix.de> (raw)
In-Reply-To: <4F7AF0C7.7020506@grandegger.com>
[-- Attachment #1: Type: text/plain, Size: 1826 bytes --]
On 04/03/2012 02:44 PM, Wolfgang Grandegger wrote:
> On 04/03/2012 02:32 PM, AnilKumar Ch wrote:
>> This patch adds the support for Bosch D_CAN controller.
>>
>> Bosch D_CAN controller is a full-CAN implementation compliant to
>> CAN protocol version 2.0 part A and B. Bosch D_CAN user manual
>> can be obtained from: http://www.semiconductors.bosch.de/media/
>> en/pdf/ipmodules_1/can/d_can_users_manual_111.pdf
>>
>> D_CAN device is used on many SoCs like AM335x, DM8148 and DM813x
>> EVMs from TI, D_CAN details on AM335x can be accessed from:
>> http://www.ti.com/lit/ug/spruh73c/spruh73c.pdf
>>
>> D_CAN can be configurable for 16, 32, 64 and 128 message objects.
>> The driver implementation is based on 64 message objects.
>>
>> Following are the design choices made while writing the controller
>> driver:
>> 1. Interface Register set IF0 has be used for receive and IF1 is
>> used for transmit message objects.
>> 2. Out of the total Message objects available, half of it are kept
>> aside for RX purposes and the rest for TX purposes.
>> 3. NAPI implementation is such that both the TX and RX paths
>> functions in polling mode.
>>
>> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
>
> Please explain why this CAN controller cannot be handled by the existing
> C_CAN driver, eventually with some extensions. The register layout seems
> almost identical, at least.
ACK.
Have a look at the recent at91_can driver. It has been improved to work
with a flexible number of message objects.
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-04-03 12:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 12:32 [PATCH] ARM: OMAP: AM33XX: CAN: d_can: Add support for Bosch D_CAN controller AnilKumar Ch
2012-04-03 12:39 ` AnilKumar, Chimata
2012-04-03 15:54 ` Oliver Hartkopp
2012-04-03 18:07 ` AnilKumar, Chimata
2012-04-03 12:44 ` Wolfgang Grandegger
2012-04-03 12:49 ` Marc Kleine-Budde [this message]
2012-04-03 13:41 ` AnilKumar, Chimata
2012-04-03 13:49 ` Marc Kleine-Budde
2012-04-03 14:29 ` AnilKumar, Chimata
2012-04-03 15:33 ` Marc Kleine-Budde
2012-04-03 15:58 ` AnilKumar, Chimata
2012-04-04 3:43 ` Bhupesh SHARMA
2012-04-04 16:21 ` 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=4F7AF1EC.1060802@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=anantgole@ti.com \
--cc=anilkumar@ti.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=m.kleine-budde@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=socketcan@hartkopp.net \
--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).