Commit 05153702 authored by Bin Meng's avatar Bin Meng Committed by Priyanka Jain
Browse files

dt-bindings: net: Update Freescale TSEC to support "queue-group"



At present the Freescale TSEC node DT bindings doc requires a <reg>
property in the TSEC node. But this might not always be the case.
In the upstream Linux kernel, there is no DT bindings doc for it
but the kernel driver tests a subnode of a name prefixed with
"queue-group", as we can see from gfar_of_init():

  for_each_available_child_of_node(np, child) {
      if (!of_node_name_eq(child, "queue-group"))
  ...

in drivers/net/ethernet/freescale/gianfar.c

Update our DT bindings to describe this alternate description.
Signed-off-by: Bin Meng's avatarBin Meng <bmeng.cn@gmail.com>
Reviewed-by: Ramon Fried's avatarRamon Fried <rfried.dev@gmail.com>
Reviewed-by: default avatarVladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Priyanka Jain's avatarPriyanka Jain <priyanka.jain@nxp.com>
parent 408f056e
...@@ -3,12 +3,17 @@ ...@@ -3,12 +3,17 @@
Properties: Properties:
- compatible : Should be "fsl,etsec2" or "gianfar" - compatible : Should be "fsl,etsec2" or "gianfar"
- reg : Offset and length of the register set for the device - reg : Offset and length of the register set for the device. If this is
missing, a subnode with a name prefix "queue-group" must be provided to
provide the <reg> property.
- phy-handle : See ethernet.txt file in the same directory. - phy-handle : See ethernet.txt file in the same directory.
- phy-connection-type : See ethernet.txt file in the same directory. This - phy-connection-type : See ethernet.txt file in the same directory. This
property is only really needed if the connection is of type "rgmii-id", property is only really needed if the connection is of type "rgmii-id",
"rgmii-rxid" and "rgmii-txid" as all other connection types are detected "rgmii-rxid" and "rgmii-txid" as all other connection types are detected
by hardware. by hardware.
- ranges : an <empty> value if subnode "queue-group" is present, specifying
that no address translation is required between them TSEC parent node and
the child "queue-group" node.
Example: Example:
ethernet@24000 { ethernet@24000 {
...@@ -18,6 +23,18 @@ Example: ...@@ -18,6 +23,18 @@ Example:
phy-connection-type = "sgmii"; phy-connection-type = "sgmii";
}; };
An alternate description with "queue-group" subnode example:
ethernet@24000 {
compatible = "fsl,etsec2";
phy-handle = <&phy0>;
phy-connection-type = "sgmii";
ranges;
queue-group {
reg = <0x24000 0x1000>;
};
};
Child nodes of the TSEC controller are typically the individual PHY devices Child nodes of the TSEC controller are typically the individual PHY devices
connected via the MDIO bus (sometimes the MDIO bus controller is separate). connected via the MDIO bus (sometimes the MDIO bus controller is separate).
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment