Skip to contentSkip to conversation

Docs: dt: update binding for Freescale Management Complex

PATCH In review Stuart Yoder 2 participants 7 messages Sep 25, 2015 – Sep 29, 2015 Device tree bindings

lore
Share & tools
lore
#0 lore raw

cover Docs: dt: update binding for Freescale Management Complex

Update the binding for the Freescale Management Complex to include definition of ranges, msi-parent, and dpmac subnodes.

Stuart Yoder (3):
Docs: dt: fsl-mc: update binding to include msi-parent
Docs: dt: fsl-mc update binding to include definition of ranges
Docs: dt: fsl-mc: update binding to define dpmac subnodes

 .../devicetree/bindings/misc/fsl,qoriq-mc.txt      | 81 +++++++++++++++++++++-
 1 file changed, 80 insertions(+), 1 deletion(-)
Signature · 6 lines
2.3.3

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#1 lore raw

PATCH 1/3 Docs: dt: fsl-mc: update binding to include msi-parent

The Freescale Management Complex and all associated objects use message interrupts, and thus an msi-parent is required.

---
 Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt | 6 ++++++
 1 file changed, 6 insertions(+)
Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt +6 -0
index c7a26ca..6aac955 100644
@@ -30,11 +30,17 @@ Required properties:
                         region may not be present in some scenarios, such
                         as in the device tree presented to a virtual machine.
 
+    - msi-parent
+        Value type: <phandle>
+        Definition: Must be present and point to the MSI controller node
+                    handling message interrupts for the MC.
+
 Example:
 
         fsl_mc: fsl-mc@80c000000 {
                 compatible = "fsl,qoriq-mc";
                 reg = <0x00000008 0x0c000000 0 0x40>,    /* MC portal base */
                       <0x00000000 0x08340000 0 0x40000>; /* MC control reg */
+                msi-parent = <&its>;
         };
 
Signature · 1 line
2.3.3
Acked-by on v1 1/3
#2 lore raw

RE: [PATCH 1/3] Docs: dt: fsl-mc: update binding to include msi-parent

Quoted 40 lines

-----Original Message-----
From: Stuart Yoder [mailto:[email protected]]
Sent: Friday, September 25, 2015 4:08 PM
To: [email protected]; [email protected]
Cc: [email protected]; [email protected]; Rivera Jose-B46482; Sharma Bhupesh-B45370; katz Itai-RM05202; Yoder Stuart-
B08248
Subject: [PATCH 1/3] Docs: dt: fsl-mc: update binding to include msi-
parent

The Freescale Management Complex and all associated objects use message interrupts, and thus an msi-parent is required.

---
 Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt | 6 ++++++
 1 file changed, 6 insertions(+)
Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt +0 -0
index c7a26ca..6aac955 100644
@@ -30,11 +30,17 @@ Required properties:
                         region may not be present in some scenarios,

such
as in the device tree presented to a virtual
machine.

Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt +5 -0
+    - msi-parent
+        Value type: <phandle>
+        Definition: Must be present and point to the MSI controller node
+                    handling message interrupts for the MC.
+
 Example:
 
         fsl_mc: fsl-mc@80c000000 {
                 compatible = "fsl,qoriq-mc";
                 reg = <0x00000008 0x0c000000 0 0x40>,    /* MC portal

base */

Quoted 7 lines
                       <0x00000000 0x08340000 0 0x40000>; /* MC control
reg */
+                msi-parent = <&its>;
         };

--
2.3.3

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

#3 lore raw

PATCH 2/3 Docs: dt: fsl-mc update binding to include definition of ranges

In reply to Stuart Yoder

Define a ranges property to specify the mapping between the MC address space and the system address space.

---
 .../devicetree/bindings/misc/fsl,qoriq-mc.txt      | 30 +++++++++++++++++++++-
 1 file changed, 29 insertions(+), 1 deletion(-)
Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt +29 -1
index 6aac955..848975f 100644
@@ -35,6 +35,26 @@ Required properties:
         Definition: Must be present and point to the MSI controller node
                     handling message interrupts for the MC.
 
+    - ranges
+        Value type: <prop-encoded-array>
+        Definition: A standard property.  Defines the mapping between the child
+                    MC address space and the parent system address space.
+
+                    The MC address space is defined by 3 components:
+                       <region type> <offset hi> <offset lo>
+
+                    Valid values for region type are
+                       0x0 - MC portals
+                       0x1 - QBMAN portals
+
+    - #address-cells
+        Value type: <u32>
+        Definition: Must be 3.  (see definition in 'ranges' property)
+
+    - #size-cells
+        Value type: <u32>
+        Definition: Must be 1.
+
 Example:
 
         fsl_mc: fsl-mc@80c000000 {
@@ -42,5 +62,13 @@ Example:
                 reg = <0x00000008 0x0c000000 0 0x40>,    /* MC portal base */
                       <0x00000000 0x08340000 0 0x40000>; /* MC control reg */
                 msi-parent = <&its>;
-        };
+                #address-cells = <3>;
+                #size-cells = <1>;
 
+                /*
+                 * Region type 0x0 - MC portals
+                 * Region type 0x1 - QBMAN portals
+                 */
+                ranges = <0x0 0x0 0x0 0x8 0x0c000000 0x4000000
+                          0x1 0x0 0x0 0x8 0x18000000 0x8000000>;
+        };
Signature · 6 lines
2.3.3

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Acked-by on v1 2/3
#4 lore raw

RE: [PATCH 2/3] Docs: dt: fsl-mc update binding to include definition of ranges

Quoted 71 lines

-----Original Message-----
From: Stuart Yoder [mailto:[email protected]]
Sent: Friday, September 25, 2015 4:08 PM
To: [email protected]; [email protected]
Cc: [email protected]; [email protected]; Rivera Jose-B46482; Sharma Bhupesh-B45370; katz Itai-RM05202; Yoder Stuart-
B08248
Subject: [PATCH 2/3] Docs: dt: fsl-mc update binding to include
definition of ranges

Define a ranges property to specify the mapping between the MC address space and the system address space.

---
 .../devicetree/bindings/misc/fsl,qoriq-mc.txt      | 30
+++++++++++++++++++++-
 1 file changed, 29 insertions(+), 1 deletion(-)
Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt +3 -0
index 6aac955..848975f 100644
@@ -35,6 +35,26 @@ Required properties:
         Definition: Must be present and point to the MSI controller node
                     handling message interrupts for the MC.
 
+    - ranges
+        Value type: <prop-encoded-array>
+        Definition: A standard property.  Defines the mapping between

the child
+ MC address space and the parent system address
space.

Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt +16 -0
+
+                    The MC address space is defined by 3 components:
+                       <region type> <offset hi> <offset lo>
+
+                    Valid values for region type are
+                       0x0 - MC portals
+                       0x1 - QBMAN portals
+
+    - #address-cells
+        Value type: <u32>
+        Definition: Must be 3.  (see definition in 'ranges' property)
+
+    - #size-cells
+        Value type: <u32>
+        Definition: Must be 1.
+
 Example:
 
         fsl_mc: fsl-mc@80c000000 {
@@ -42,5 +62,13 @@ Example:
                 reg = <0x00000008 0x0c000000 0 0x40>,    /* MC portal

base */

                       <0x00000000 0x08340000 0 0x40000>; /* MC control
reg */
                 msi-parent = <&its>;
Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt +9 -2
-        };
+                #address-cells = <3>;
+                #size-cells = <1>;
 
+                /*
+                 * Region type 0x0 - MC portals
+                 * Region type 0x1 - QBMAN portals
+                 */
+                ranges = <0x0 0x0 0x0 0x8 0x0c000000 0x4000000
+                          0x1 0x0 0x0 0x8 0x18000000 0x8000000>;
+        };
--
Quoted 1 line

2.3.3

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

#5 lore raw

PATCH 3/3 Docs: dt: fsl-mc: update binding to define dpmac subnodes

In reply to Stuart Yoder

The fsl-mc node may optionally have dpmac sub-nodes that describe the relationship between the Ethernet MACs which belong to the MC and the Ethernet PHYs on the system board.

---
 .../devicetree/bindings/misc/fsl,qoriq-mc.txt      | 45 ++++++++++++++++++++++
 1 file changed, 45 insertions(+)
Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt +45 -0
index 848975f..6611a7c 100644
@@ -55,6 +55,40 @@ Required properties:
         Value type: <u32>
         Definition: Must be 1.
 
+Sub-nodes:
+
+        The fsl-mc node may optionally have dpmac sub-nodes that describe
+        the relationship between the Ethernet MACs which belong to the MC
+        and the Ethernet PHYs on the system board.
+
+        The dpmac nodes must be under a node named "dpmacs" which contains
+        the following properties:
+
+            - #address-cells
+              Value type: <u32>
+              Definition: Must be present if dpmac sub-nodes are defined and must
+                          have a value of 1.
+
+            - #size-cells
+              Value type: <u32>
+              Definition: Must be present if dpmac sub-nodes are defined and must
+                          have a value of 0.
+
+        These nodes must have the following properties:
+
+            - compatible
+              Value type: <string>
+              Definition: Must be "fsl,qoriq-mc-dpmac".
+
+            - reg
+              Value type: <prop-encoded-array>
+              Definition: Specifies the id of the dpmac.
+
+            - phy-handle
+              Value type: <phandle>
+              Definition: Specifies the phandle to the PHY device node associated
+                          with the this dpmac.
+
 Example:
 
         fsl_mc: fsl-mc@80c000000 {
@@ -71,4 +105,15 @@ Example:
                  */
                 ranges = <0x0 0x0 0x0 0x8 0x0c000000 0x4000000
                           0x1 0x0 0x0 0x8 0x18000000 0x8000000>;
+
+                dpmacs {
+                    #address-cells = <1>;
+                    #size-cells = <0>;
+
+                    dpmac@1 {
+                        compatible = "fsl,qoriq-mc-dpmac";
+                        reg = <1>;
+                        phy-handle = <&mdio0_phy0>;
+                    }
+                }
         };
Signature · 1 line
2.3.3
Acked-by on v1 3/3
#6 lore raw

RE: [PATCH 3/3] Docs: dt: fsl-mc: update binding to define dpmac subnodes

Quoted 89 lines

-----Original Message-----
From: Stuart Yoder [mailto:[email protected]]
Sent: Friday, September 25, 2015 4:08 PM
To: [email protected]; [email protected]
Cc: [email protected]; [email protected]; Rivera Jose-B46482; Sharma Bhupesh-B45370; katz Itai-RM05202; Yoder Stuart- B08248
Subject: [PATCH 3/3] Docs: dt: fsl-mc: update binding to define dpmac subnodes

The fsl-mc node may optionally have dpmac sub-nodes that describe the relationship between the Ethernet MACs which belong to the MC and the Ethernet PHYs on the system board.

---
 .../devicetree/bindings/misc/fsl,qoriq-mc.txt      | 45
++++++++++++++++++++++
 1 file changed, 45 insertions(+)
Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt +3 -0
index 848975f..6611a7c 100644
@@ -55,6 +55,40 @@ Required properties:
         Value type: <u32>
         Definition: Must be 1.
 
+Sub-nodes:
+
+        The fsl-mc node may optionally have dpmac sub-nodes that

describe
+ the relationship between the Ethernet MACs which belong to the
MC

Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt +3 -0
+        and the Ethernet PHYs on the system board.
+
+        The dpmac nodes must be under a node named "dpmacs" which

contains

Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt +5 -0
+        the following properties:
+
+            - #address-cells
+              Value type: <u32>
+              Definition: Must be present if dpmac sub-nodes are defined

and must

Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt +5 -0
+                          have a value of 1.
+
+            - #size-cells
+              Value type: <u32>
+              Definition: Must be present if dpmac sub-nodes are defined

and must

Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt +15 -0
+                          have a value of 0.
+
+        These nodes must have the following properties:
+
+            - compatible
+              Value type: <string>
+              Definition: Must be "fsl,qoriq-mc-dpmac".
+
+            - reg
+              Value type: <prop-encoded-array>
+              Definition: Specifies the id of the dpmac.
+
+            - phy-handle
+              Value type: <phandle>
+              Definition: Specifies the phandle to the PHY device node

associated

Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt +13 -1
+                          with the this dpmac.
+
 Example:
 
         fsl_mc: fsl-mc@80c000000 {
@@ -71,4 +105,15 @@ Example:
                  */
                 ranges = <0x0 0x0 0x0 0x8 0x0c000000 0x4000000
                           0x1 0x0 0x0 0x8 0x18000000 0x8000000>;
+
+                dpmacs {
+                    #address-cells = <1>;
+                    #size-cells = <0>;
+
+                    dpmac@1 {
+                        compatible = "fsl,qoriq-mc-dpmac";
+                        reg = <1>;
+                        phy-handle = <&mdio0_phy0>;
+                    }
+                }
         };
--
Quoted 1 line

2.3.3