From: mkl@pengutronix.de (Marc Kleine-Budde)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND v5 3/3] arm/dts: AM33XX: Add D_CAN device tree data
Date: Wed, 05 Sep 2012 15:46:58 +0200 [thread overview]
Message-ID: <504757D2.90601@pengutronix.de> (raw)
In-Reply-To: <1346845260-10978-4-git-send-email-anilkumar@ti.com>
On 09/05/2012 01:41 PM, AnilKumar Ch wrote:
> Add Bosch D_CAN controller device tree data to AM33XX dtsi
> file by adding d_can device nodes with all the necessary
> parameters.
>
> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
> ---
> arch/arm/boot/dts/am33xx.dtsi | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> index bf5f713..ab744d6 100644
> --- a/arch/arm/boot/dts/am33xx.dtsi
> +++ b/arch/arm/boot/dts/am33xx.dtsi
> @@ -177,5 +177,23 @@
> compatible = "ti,omap3-wdt";
> ti,hwmods = "wd_timer2";
> };
> +
> + dcan0: d_can at 481cc000 {
> + compatible = "bosch,d_can";
On imx/mxs we also add a compatible for the current hardware, this may
look like this:
compatible = "ti,am33xx-can", "bosch,d_can";
But I don't know if this is a generic policy or just an imx/mxs thing :)
Marc
> + ti,hwmods = "d_can0";
> + reg = <0x481cc000 0x2000>;
> + interrupts = <52>;
> + interrupt-parent = <&intc>;
> + status = "disabled";
> + };
> +
> + dcan1: d_can at 481d0000 {
> + compatible = "bosch,d_can";
> + ti,hwmods = "d_can1";
> + reg = <0x481d0000 0x2000>;
> + interrupts = <55>;
> + interrupt-parent = <&intc>;
> + status = "disabled";
> + };
> };
> };
>
--
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: 259 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120905/e976f849/attachment.sig>
next prev parent reply other threads:[~2012-09-05 13:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 11:40 [PATCH v6 0/3] arm/dts: Add device tree data for AM33XX devices AnilKumar Ch
2012-09-05 11:40 ` [PATCH RESEND v5 1/3] arm/dts: AM33XX: Add basic pinctrl device tree data AnilKumar Ch
2012-09-05 23:35 ` Tony Lindgren
2012-09-05 11:40 ` [PATCH v6 2/3] arm/dts: AM33XX: Configure pinmuxs for user leds control on Bone AnilKumar Ch
2012-09-06 20:58 ` Tony Lindgren
2012-09-07 3:23 ` AnilKumar, Chimata
2012-09-05 11:41 ` [PATCH RESEND v5 3/3] arm/dts: AM33XX: Add D_CAN device tree data AnilKumar Ch
2012-09-05 13:46 ` Marc Kleine-Budde [this message]
2012-09-06 8:09 ` AnilKumar, Chimata
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=504757D2.90601@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).