Modify c_can binding documentation according to recent review comments
on device tree data addition patches.
Signed-off-by: AnilKumar Ch <anilkumar@xxxxxx>
---
.../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@481D0000 {
+Step1: SoC common .dtsi file
+
+ d_can1: d_can@481d0000 {
compatible = "bosch,d_can";
- reg = <0x481D0000 0x1000>;
- interrupts = <55 0x4>;
+ reg = <0x481d0000 0x2000>;
+ interrupts = <55>;
interrupt-parent = <&intc>;
+ status = "disabled";
};
(or)
- d_can@481D0000 {
+ d_can1: d_can@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
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
