From: anilkumar@ti.com (AnilKumar Ch)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/5] of: Modify c_can binding documentation
Date: Fri, 31 Aug 2012 14:59:21 +0530 [thread overview]
Message-ID: <1346405361-29711-6-git-send-email-anilkumar@ti.com> (raw)
In-Reply-To: <1346405361-29711-1-git-send-email-anilkumar@ti.com>
Modify c_can binding documentation according to recent review comments
on device tree data addition patches.
Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
---
.../devicetree/bindings/net/can/c_can.txt | 25 ++++++++++++++++----
1 file changed, 20 insertions(+), 5 deletions(-)
diff --git a/Documentation/devicetree/bindings/net/can/c_can.txt b/Documentation/devicetree/bindings/net/can/c_can.txt
index a43f083..90a70be 100644
--- a/Documentation/devicetree/bindings/net/can/c_can.txt
+++ b/Documentation/devicetree/bindings/net/can/c_can.txt
@@ -8,6 +8,8 @@ Required properties:
registers map
- interrupts : property with a value describing the interrupt
number
+- status : describes the node status either "disabled" or
+ "okay"
Optional properties:
- interrupt-parent : The parent interrupt controller
@@ -20,18 +22,31 @@ Future plan is to migrate hwmod data base contents into device tree
blob so that, all the required data will be used from device tree dts
file.
-Examples:
+Example:
- d_can at 481D0000 {
+Step1: SoC common .dtsi file
+
+ d_can1: d_can at 481d0000 {
compatible = "bosch,d_can";
- reg = <0x481D0000 0x1000>;
- interrupts = <55 0x4>;
+ reg = <0x481d0000 0x2000>;
+ interrupts = <55>;
interrupt-parent = <&intc>;
+ status = "disabled";
};
(or)
- d_can at 481D0000 {
+ d_can1: d_can at 481d0000 {
compatible = "bosch,d_can";
ti,hwmods = "d_can1";
+ reg = <0x481d0000 0x2000>;
+ interrupts = <55>;
+ interrupt-parent = <&intc>;
+ status = "disabled";
+ };
+
+Step 2: board specific .dts file
+
+ &dcan1 {
+ status = "okay";
};
--
1.7.9.5
next prev parent reply other threads:[~2012-08-31 9:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 9:29 [PATCH v5 0/5] Add device tree data for AM33XX devices AnilKumar Ch
2012-08-31 9:29 ` [PATCH v5 1/5] arm/dts: AM33XX: Add basic pinctrl device tree data AnilKumar Ch
2012-09-05 23:32 ` Tony Lindgren
2012-09-06 6:17 ` AnilKumar, Chimata
2012-08-31 9:29 ` [PATCH v5 2/5] arm/dts: AM33XX: Configure pinmuxs for user leds control on Bone AnilKumar Ch
2012-08-31 9:29 ` [PATCH v5 3/5] arm/dts: AM33XX: Add D_CAN device tree data AnilKumar Ch
2012-08-31 9:29 ` [PATCH 4/5] leds: leds-gpio: adopt pinctrl support AnilKumar Ch
2012-08-31 16:04 ` Tony Lindgren
2012-08-31 17:54 ` AnilKumar, Chimata
2012-08-31 9:29 ` AnilKumar Ch [this message]
2012-09-01 7:05 ` [PATCH 5/5] of: Modify c_can binding documentation AnilKumar, Chimata
2012-09-02 2:02 ` Stephen Warren
2012-09-03 4:35 ` 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=1346405361-29711-6-git-send-email-anilkumar@ti.com \
--to=anilkumar@ti.com \
--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).