From: mkl@pengutronix.de (Marc Kleine-Budde)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data
Date: Thu, 26 Jul 2012 11:14:57 +0200 [thread overview]
Message-ID: <50110A91.2080508@pengutronix.de> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13EA04433@DBDE01.ent.ti.com>
On 07/26/2012 11:03 AM, AnilKumar, Chimata wrote:
> On Thu, Jul 26, 2012 at 14:16:33, Koen Kooi wrote:
>>
>> Op 25 jul. 2012, om 14:23 heeft AnilKumar Ch <anilkumar@ti.com> het volgende geschreven:
>>
>>> Add Bosch D_CAN controller device tree data to AM33XX dtsi file
>>> by adding d_can device node with all the necessary parameters.
>>>
>>> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
>>> ---
>>> arch/arm/boot/dts/am33xx.dtsi | 5 +++++
>>> 1 file changed, 5 insertions(+)
>>>
>>> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
>>> index 9b974dc..2db2ffb 100644
>>> --- a/arch/arm/boot/dts/am33xx.dtsi
>>> +++ b/arch/arm/boot/dts/am33xx.dtsi
>>> @@ -163,5 +163,10 @@
>>> #size-cells = <0>;
>>> ti,hwmods = "i2c3";
>>> };
>>> +
>>> + dcan1: d_can at 481D0000 {
>>> + compatible = "bosch,d_can";
>>> + ti,hwmods = "d_can1";
>>> + };
>>> };
>>
>> I scanned the linux-networking mailinglist and l-o-ml, but I can't find the patchset that actually adds the d_can drivers, could you provide a link to that? I have 2 different CAN capes I'd like to test on beaglebone.
>>
>
> You can find it from linux-next or net-next trees, D_CAN support is added
> to C_CAN driver.
>
> http://git.kernel.org/?p=linux/kernel/git/davem/net-next.git;
> a=commitdiff;h=69927fccd96b15bd228bb82d356a7a2a0cfaeefb
Meanwhile it's in Linus's git tree.
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 |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120726/074c155e/attachment.sig>
next prev parent reply other threads:[~2012-07-26 9:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 12:23 [PATCH v2 0/2] Add D_CAN device tree data to AM335x-EVM AnilKumar Ch
2012-07-25 12:23 ` [PATCH v2 1/2] arm/dts: AM33XX: Add D_CAN device tree data AnilKumar Ch
2012-07-25 12:43 ` Sergei Shtylyov
2012-07-26 8:36 ` Daniel Mack
2012-07-26 13:04 ` Sergei Shtylyov
2012-08-03 9:14 ` Vaibhav Hiremath
2012-07-26 8:46 ` Koen Kooi
2012-07-26 9:03 ` AnilKumar, Chimata
2012-07-26 9:14 ` Marc Kleine-Budde [this message]
2012-07-26 9:35 ` Koen Kooi
2012-08-03 6:28 ` Vaibhav Hiremath
2012-08-07 11:40 ` AnilKumar, Chimata
2012-07-25 12:23 ` [PATCH v2 2/2] arm/dts: AM33XX: Configure pinmuxs for D_CAN1 on AM335x-EVM AnilKumar Ch
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=50110A91.2080508@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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 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).