From: Marc Kleine-Budde <mkl-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: AnilKumar Ch <anilkumar-l0cyMroinI0@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
rpurdie-Fm38FmjxZ/leoWH0uzbU5w@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-leds-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
bryan.wu-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [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-l0cyMroinI0@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1644 bytes --]
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-l0cyMroinI0@public.gmane.org>
> ---
> 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@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@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 |
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
[-- Attachment #2: Type: text/plain, Size: 192 bytes --]
_______________________________________________
devicetree-discuss mailing list
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
WARNING: multiple messages have this Message-ID (diff)
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: 18+ 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 ` 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 11:40 ` AnilKumar Ch
2012-09-05 23:35 ` Tony Lindgren
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-05 11:40 ` AnilKumar Ch
2012-09-06 20:58 ` Tony Lindgren
2012-09-06 20:58 ` Tony Lindgren
[not found] ` <20120906205811.GO1303-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2012-09-07 3:23 ` AnilKumar, Chimata
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 11:41 ` AnilKumar Ch
[not found] ` <1346845260-10978-4-git-send-email-anilkumar-l0cyMroinI0@public.gmane.org>
2012-09-05 13:46 ` Marc Kleine-Budde [this message]
2012-09-05 13:46 ` Marc Kleine-Budde
[not found] ` <504757D2.90601-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-09-06 8:09 ` AnilKumar, Chimata
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-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=anilkumar-l0cyMroinI0@public.gmane.org \
--cc=bryan.wu-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-leds-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rpurdie-Fm38FmjxZ/leoWH0uzbU5w@public.gmane.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.