Skip to contentSkip to conversation

drivers: net: cpsw: Add reading of DT phy-handle node

PATCH Superseded Dan Murphy 5 participants 33 messages Apr 15, 2016 – Apr 28, 2016

Subsystems (4)

v6 of 8 Superseded Latest is v8 →

lore
Share & tools
lore

Dan Murphy

author
#0 lore raw

PATCH v6 1/7 drivers: net: cpsw: Add reading of DT phy-handle node

Add the ability to read the phy-handle node of the cpsw slave. Upon reading this handle the phy-id can be stored based on the reg node in the DT.

The phy-handle also needs to be stored and passed to the phy to access any phy data that is available.

---

v6 - Fix build error when DM_ETH is not defined and updated phy_handle error handling - https://patchwork.ozlabs.org/patch/608763/

 drivers/net/cpsw.c | 20 ++++++++++++++++++--
 include/cpsw.h     |  1 +
 2 files changed, 19 insertions(+), 2 deletions(-)
drivers/net/cpsw.c +18 -2
index 7104754..3d6f0ce 100644
@@ -965,6 +965,11 @@ static int cpsw_phy_init(struct cpsw_priv *priv, struct cpsw_slave *slave)
 	phydev->supported &= supported;
 	phydev->advertising = phydev->supported;
 
+#ifdef CONFIG_DM_ETH
+	if (slave->data->phy_of_handle)
+		phydev->dev->of_offset = slave->data->phy_of_handle;
+#endif
+
 	priv->phydev = phydev;
 	phy_config(phydev);
 
@@ -1217,8 +1222,19 @@ static int cpsw_eth_ofdata_to_platdata(struct udevice *dev)
 			if (phy_mode)
 				priv->data.slave_data[slave_index].phy_if =
 					phy_get_interface_by_name(phy_mode);
-			fdtdec_get_int_array(fdt, subnode, "phy_id", phy_id, 2);
-			priv->data.slave_data[slave_index].phy_addr = phy_id[1];
+
+			priv->data.slave_data[slave_index].phy_of_handle =
+				fdtdec_lookup_phandle(fdt, subnode, "phy-handle");
+
+			if (priv->data.slave_data[slave_index].phy_of_handle >= 0) {
+				priv->data.slave_data[slave_index].phy_addr =
+					fdtdec_get_int(gd->fdt_blob,
+						priv->data.slave_data[slave_index].phy_of_handle,
+						"reg", -1);
+			} else {
+				fdtdec_get_int_array(fdt, subnode, "phy_id", phy_id, 2);
+				priv->data.slave_data[slave_index].phy_addr = phy_id[1];
+			}
 			slave_index++;
 		}
 
include/cpsw.h +1 -0
index cf1d30b..ff95cd8 100644
@@ -21,6 +21,7 @@ struct cpsw_slave_data {
 	u32		sliver_reg_ofs;
 	int		phy_addr;
 	int		phy_if;
+	int		phy_of_handle;
 };
 
 enum {
Signature · 1 line
2.8.1.116.g7b0d47b
author
#1 lore raw

PATCH v6 1/7 drivers: net: cpsw: Add reading of DT phy-handle node

Bump?

Quoted 66 lines · Dan Murphy

Add the ability to read the phy-handle node of the cpsw slave. Upon reading this handle the phy-id can be stored based on the reg node in the DT.

The phy-handle also needs to be stored and passed to the phy to access any phy data that is available.

---

v6 - Fix build error when DM_ETH is not defined and updated phy_handle error handling - https://patchwork.ozlabs.org/patch/608763/

 drivers/net/cpsw.c | 20 ++++++++++++++++++--
 include/cpsw.h     |  1 +
 2 files changed, 19 insertions(+), 2 deletions(-)
drivers/net/cpsw.c +18 -2
index 7104754..3d6f0ce 100644
@@ -965,6 +965,11 @@ static int cpsw_phy_init(struct cpsw_priv *priv, struct cpsw_slave *slave)
 	phydev->supported &= supported;
 	phydev->advertising = phydev->supported;
 
+#ifdef CONFIG_DM_ETH
+	if (slave->data->phy_of_handle)
+		phydev->dev->of_offset = slave->data->phy_of_handle;
+#endif
+
 	priv->phydev = phydev;
 	phy_config(phydev);
 
@@ -1217,8 +1222,19 @@ static int cpsw_eth_ofdata_to_platdata(struct udevice *dev)
 			if (phy_mode)
 				priv->data.slave_data[slave_index].phy_if =
 					phy_get_interface_by_name(phy_mode);
-			fdtdec_get_int_array(fdt, subnode, "phy_id", phy_id, 2);
-			priv->data.slave_data[slave_index].phy_addr = phy_id[1];
+
+			priv->data.slave_data[slave_index].phy_of_handle =
+				fdtdec_lookup_phandle(fdt, subnode, "phy-handle");
+
+			if (priv->data.slave_data[slave_index].phy_of_handle >= 0) {
+				priv->data.slave_data[slave_index].phy_addr =
+					fdtdec_get_int(gd->fdt_blob,
+						priv->data.slave_data[slave_index].phy_of_handle,
+						"reg", -1);
+			} else {
+				fdtdec_get_int_array(fdt, subnode, "phy_id", phy_id, 2);
+				priv->data.slave_data[slave_index].phy_addr = phy_id[1];
+			}
 			slave_index++;
 		}
 
include/cpsw.h +1 -0
index cf1d30b..ff95cd8 100644
@@ -21,6 +21,7 @@ struct cpsw_slave_data {
 	u32		sliver_reg_ofs;
 	int		phy_addr;
 	int		phy_if;
+	int		phy_of_handle;
 };
 
 enum {
Signature · 2 lines
------------------
Dan Murphy
author
#2 lore raw

PATCH v6 2/7 net: zynq_gem: Add the passing of the phy-handle node

In reply to Dan Murphy

Add the ability to pass the phy-handle node offset to the phy driver. This allows the phy driver to access the DT subnode's data and parse accordingly.

---

v6 - No changes - https://patchwork.ozlabs.org/patch/608769/

 drivers/net/zynq_gem.c | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)
drivers/net/zynq_gem.c +10 -5
index aec8077..f9b22c4 100644
@@ -179,6 +179,7 @@ struct zynq_gem_priv {
 	struct zynq_gem_regs *iobase;
 	phy_interface_t interface;
 	struct phy_device *phydev;
+	int phy_of_handle;
 	struct mii_dev *bus;
 };
 
@@ -352,6 +353,10 @@ static int zynq_phy_init(struct udevice *dev)
 	priv->phydev->supported = supported | ADVERTISED_Pause |
 				  ADVERTISED_Asym_Pause;
 	priv->phydev->advertising = priv->phydev->supported;
+
+	if (priv->phy_of_handle > 0)
+		priv->phydev->dev->of_offset = priv->phy_of_handle;
+
 	phy_config(priv->phydev);
 
 	return 0;
@@ -675,7 +680,6 @@ static int zynq_gem_ofdata_to_platdata(struct udevice *dev)
 {
 	struct eth_pdata *pdata = dev_get_platdata(dev);
 	struct zynq_gem_priv *priv = dev_get_priv(dev);
-	int offset = 0;
 	const char *phy_mode;
 
 	pdata->iobase = (phys_addr_t)dev_get_addr(dev);
@@ -684,10 +688,11 @@ static int zynq_gem_ofdata_to_platdata(struct udevice *dev)
 	priv->emio = 0;
 	priv->phyaddr = -1;
 
-	offset = fdtdec_lookup_phandle(gd->fdt_blob, dev->of_offset,
-				       "phy-handle");
-	if (offset > 0)
-		priv->phyaddr = fdtdec_get_int(gd->fdt_blob, offset, "reg", -1);
+	priv->phy_of_handle = fdtdec_lookup_phandle(gd->fdt_blob,
+					dev->of_offset, "phy-handle");
+	if (priv->phy_of_handle > 0)
+		priv->phyaddr = fdtdec_get_int(gd->fdt_blob,
+					priv->phy_of_handle, "reg", -1);
 
 	phy_mode = fdt_getprop(gd->fdt_blob, dev->of_offset, "phy-mode", NULL);
 	if (phy_mode)
Signature · 1 line
2.8.1.116.g7b0d47b
author
#3 lore raw

PATCH v6 2/7 net: zynq_gem: Add the passing of the phy-handle node

Bump?

Quoted 60 lines · Dan Murphy

Add the ability to pass the phy-handle node offset to the phy driver. This allows the phy driver to access the DT subnode's data and parse accordingly.

---

v6 - No changes - https://patchwork.ozlabs.org/patch/608769/

 drivers/net/zynq_gem.c | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)
drivers/net/zynq_gem.c +10 -5
index aec8077..f9b22c4 100644
@@ -179,6 +179,7 @@ struct zynq_gem_priv {
 	struct zynq_gem_regs *iobase;
 	phy_interface_t interface;
 	struct phy_device *phydev;
+	int phy_of_handle;
 	struct mii_dev *bus;
 };
 
@@ -352,6 +353,10 @@ static int zynq_phy_init(struct udevice *dev)
 	priv->phydev->supported = supported | ADVERTISED_Pause |
 				  ADVERTISED_Asym_Pause;
 	priv->phydev->advertising = priv->phydev->supported;
+
+	if (priv->phy_of_handle > 0)
+		priv->phydev->dev->of_offset = priv->phy_of_handle;
+
 	phy_config(priv->phydev);
 
 	return 0;
@@ -675,7 +680,6 @@ static int zynq_gem_ofdata_to_platdata(struct udevice *dev)
 {
 	struct eth_pdata *pdata = dev_get_platdata(dev);
 	struct zynq_gem_priv *priv = dev_get_priv(dev);
-	int offset = 0;
 	const char *phy_mode;
 
 	pdata->iobase = (phys_addr_t)dev_get_addr(dev);
@@ -684,10 +688,11 @@ static int zynq_gem_ofdata_to_platdata(struct udevice *dev)
 	priv->emio = 0;
 	priv->phyaddr = -1;
 
-	offset = fdtdec_lookup_phandle(gd->fdt_blob, dev->of_offset,
-				       "phy-handle");
-	if (offset > 0)
-		priv->phyaddr = fdtdec_get_int(gd->fdt_blob, offset, "reg", -1);
+	priv->phy_of_handle = fdtdec_lookup_phandle(gd->fdt_blob,
+					dev->of_offset, "phy-handle");
+	if (priv->phy_of_handle > 0)
+		priv->phyaddr = fdtdec_get_int(gd->fdt_blob,
+					priv->phy_of_handle, "reg", -1);
 
 	phy_mode = fdt_getprop(gd->fdt_blob, dev->of_offset, "phy-mode", NULL);
 	if (phy_mode)
Signature · 2 lines
------------------
Dan Murphy
#4 lore raw

PATCH v6 2/7 net: zynq_gem: Add the passing of the phy-handle node

Quoted 15 lines · Dan Murphy

Bump?

Quoted 13 lines · Dan Murphy

Add the ability to pass the phy-handle node offset to the phy driver. This allows the phy driver to access the DT subnode's data and parse accordingly.

---

v6 - No changes - https://patchwork.ozlabs.org/patch/608769/

 drivers/net/zynq_gem.c | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

Joe, Tom: Do you want to take this series?
I am happy to do so because there is xilinx part.

Thanks,
Michal

#5 lore raw

PATCH v6 2/7 net: zynq_gem: Add the passing of the phy-handle node

Quoted 11 lines · Michal Simek
Quoted 10 lines · Dan Murphy

Bump?

Quoted 8 lines · Dan Murphy

Add the ability to pass the phy-handle node offset to the phy driver. This allows the phy driver to access the DT subnode's data and parse accordingly.

---

Quoted 8 lines
Quoted 4 lines
Quoted 4 lines

v6 - No changes - https://patchwork.ozlabs.org/patch/608769/

 drivers/net/zynq_gem.c | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

Joe, Tom: Do you want to take this series?
I am happy to do so because there is xilinx part.

If Joe doesn't want to take it, I will.

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160421/06369a91/attachment.sig>
#6 lore raw

PATCH v6 2/7 net: zynq_gem: Add the passing of the phy-handle node

Quoted 14 lines · Tom Rini
Quoted 13 lines · Michal Simek
Quoted 12 lines · Dan Murphy

Bump?

Quoted 10 lines · Dan Murphy

Add the ability to pass the phy-handle node offset to the phy driver. This allows the phy driver to access the DT subnode's data and parse accordingly.

---

v6 - No changes - https://patchwork.ozlabs.org/patch/608769/

Quoted 8 lines
Quoted 6 lines
Quoted 2 lines
Quoted 2 lines
 drivers/net/zynq_gem.c | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

Joe, Tom: Do you want to take this series?
I am happy to do so because there is xilinx part.

If Joe doesn't want to take it, I will.

Ok. Thanks,
Michal

author
#8 lore raw

PATCH v6 3/7 net: phy: dp83867: Add device tree bindings and documentation

In reply to Dan Murphy

Add the device tree bindings and the accompanying documentation for the TI DP83867 Giga bit ethernet phy driver.

The original document was from:

    [commit 2a10154abcb75ad0d7b6bfea6210ac743ec60897 from the Linux kernel]

---

v6 - No Changes - https://patchwork.ozlabs.org/patch/608768/

 doc/device-tree-bindings/net/ti,dp83867.txt | 25 +++++++++++++++++++++
 include/dt-bindings/net/ti-dp83867.h        | 35 +++++++++++++++++++++++++++++
 2 files changed, 60 insertions(+)
 create mode 100644 doc/device-tree-bindings/net/ti,dp83867.txt
 create mode 100644 include/dt-bindings/net/ti-dp83867.h
doc/device-tree-bindings/net/ti,dp83867.txt new file +25 -0
new file mode 100644
index 0000000..cb77fdf
@@ -0,0 +1,25 @@
+* Texas Instruments - dp83867 Giga bit ethernet phy
+
+Required properties:
+	- reg - The ID number for the phy, usually a small integer
+	- ti,rx-internal-delay - RGMII Recieve Clock Delay - see dt-bindings/net/ti-dp83867.h
+		for applicable values
+	- ti,tx-internal-delay - RGMII Transmit Clock Delay - see dt-bindings/net/ti-dp83867.h
+		for applicable values
+	- ti,fifo-depth - Transmitt FIFO depth- see dt-bindings/net/ti-dp83867.h
+		for applicable values
+
+Default child nodes are standard Ethernet PHY device
+nodes as described in doc/devicetree/bindings/net/ethernet.txt
+
+Example:
+
+	ethernet-phy at 0 {
+		reg = <0>;
+		ti,rx-internal-delay = <DP83867_RGMIIDCTL_2_25_NS>;
+		ti,tx-internal-delay = <DP83867_RGMIIDCTL_2_75_NS>;
+		ti,fifo-depth = <DP83867_PHYCR_FIFO_DEPTH_4_B_NIB>;
+	};
+
+Datasheet can be found:
+http://www.ti.com/product/DP83867IR/datasheet
include/dt-bindings/net/ti-dp83867.h new file +35 -0
new file mode 100644
index 0000000..1843757
@@ -0,0 +1,35 @@
+/*
+ * TI DP83867 PHY drivers
+ *
+ * SPDX-License-Identifier:	GPL-2.0
+ *
+ */
+
+#ifndef _DT_BINDINGS_TI_DP83867_H
+#define _DT_BINDINGS_TI_DP83867_H
+
+/* PHY CTRL bits */
+#define DP83867_PHYCR_FIFO_DEPTH_3_B_NIB	0x00
+#define DP83867_PHYCR_FIFO_DEPTH_4_B_NIB	0x01
+#define DP83867_PHYCR_FIFO_DEPTH_6_B_NIB	0x02
+#define DP83867_PHYCR_FIFO_DEPTH_8_B_NIB	0x03
+
+/* RGMIIDCTL internal delay for rx and tx */
+#define DP83867_RGMIIDCTL_250_PS	0x0
+#define DP83867_RGMIIDCTL_500_PS	0x1
+#define DP83867_RGMIIDCTL_750_PS	0x2
+#define DP83867_RGMIIDCTL_1_NS		0x3
+#define DP83867_RGMIIDCTL_1_25_NS	0x4
+#define DP83867_RGMIIDCTL_1_50_NS	0x5
+#define DP83867_RGMIIDCTL_1_75_NS	0x6
+#define DP83867_RGMIIDCTL_2_00_NS	0x7
+#define DP83867_RGMIIDCTL_2_25_NS	0x8
+#define DP83867_RGMIIDCTL_2_50_NS	0x9
+#define DP83867_RGMIIDCTL_2_75_NS	0xa
+#define DP83867_RGMIIDCTL_3_00_NS	0xb
+#define DP83867_RGMIIDCTL_3_25_NS	0xc
+#define DP83867_RGMIIDCTL_3_50_NS	0xd
+#define DP83867_RGMIIDCTL_3_75_NS	0xe
+#define DP83867_RGMIIDCTL_4_00_NS	0xf
+
+#endif
Signature · 1 line
2.8.1.116.g7b0d47b
#9 lore raw

PATCH v6 3/7 net: phy: dp83867: Add device tree bindings and documentation

Quoted 8 lines · Dan Murphy

Add the device tree bindings and the accompanying documentation for the TI DP83867 Giga bit ethernet phy driver.

The original document was from:

    [commit 2a10154abcb75ad0d7b6bfea6210ac743ec60897 from the Linux kernel]

Tested this on dra72 rev C evm

Regards
Mugutnhan V N

#10 lore raw

PATCH v6 3/7 net: phy: dp83867: Add device tree bindings and documentation

In reply to Dan Murphy
Quoted 8 lines · Dan Murphy

Add the device tree bindings and the accompanying documentation for the TI DP83867 Giga bit ethernet phy driver.

The original document was from:

    [commit 2a10154abcb75ad0d7b6bfea6210ac743ec60897 from the Linux kernel]
author
#11 lore raw

PATCH v6 4/7 net: phy: ti: Allow the driver to be more configurable

In reply to Dan Murphy

Not all devices use the same internal delay or fifo depth. Add the ability to set the internal delay for rx or tx and the fifo depth via the devicetree. If the value is not set in the devicetree then set the delay to the default.

If devicetree is not used then use the default defines within the driver.

---

v6 - Fix build error when DM_ETH is not configured - https://patchwork.ozlabs.org/patch/608764/

 drivers/net/phy/ti.c | 87 ++++++++++++++++++++++++++++++++++++++++++++++------
 1 file changed, 77 insertions(+), 10 deletions(-)
drivers/net/phy/ti.c +77 -10
index 937426b..4c4f0c1 100644
@@ -6,6 +6,14 @@
  */
 #include <common.h>
 #include <phy.h>
+#include <linux/compat.h>
+#include <malloc.h>
+
+#include <fdtdec.h>
+#include <dm.h>
+#include <dt-bindings/net/ti-dp83867.h>
+
+DECLARE_GLOBAL_DATA_PTR;
 
 /* TI DP83867 */
 #define DP83867_DEVADDR		0x1f
@@ -71,6 +79,17 @@
 #define MII_MMD_CTRL_INCR_RDWT	0x8000 /* post increment on reads & writes */
 #define MII_MMD_CTRL_INCR_ON_WT	0xC000 /* post increment on writes only */
 
+/* User setting - can be taken from DTS */
+#define DEFAULT_RX_ID_DELAY	DP83867_RGMIIDCTL_2_25_NS
+#define DEFAULT_TX_ID_DELAY	DP83867_RGMIIDCTL_2_75_NS
+#define DEFAULT_FIFO_DEPTH	DP83867_PHYCR_FIFO_DEPTH_4_B_NIB
+
+struct dp83867_private {
+	int rx_id_delay;
+	int tx_id_delay;
+	int fifo_depth;
+};
+
 /**
  * phy_read_mmd_indirect - reads data from the MMD registers
  * @phydev: The PHY device bus
@@ -148,16 +167,60 @@ static inline bool phy_interface_is_rgmii(struct phy_device *phydev)
 		phydev->interface <= PHY_INTERFACE_MODE_RGMII_TXID;
 }
 
-/* User setting - can be taken from DTS */
-#define RX_ID_DELAY	8
-#define TX_ID_DELAY	0xa
-#define FIFO_DEPTH	1
+#if defined(CONFIG_DM_ETH)
+/**
+ * dp83867_data_init - Convenience function for setting PHY specific data
+ *
+ * @phydev: the phy_device struct
+ */
+static int dp83867_of_init(struct phy_device *phydev)
+{
+	struct dp83867_private *dp83867 = phydev->priv;
+	struct udevice *dev = phydev->dev;
+
+	dp83867->rx_id_delay = fdtdec_get_uint(gd->fdt_blob, dev->of_offset,
+				 "ti,rx-internal-delay", -1);
+
+	dp83867->tx_id_delay = fdtdec_get_uint(gd->fdt_blob, dev->of_offset,
+				 "ti,tx-internal-delay", -1);
+
+	dp83867->fifo_depth = fdtdec_get_uint(gd->fdt_blob, dev->of_offset,
+				 "ti,fifo-depth", -1);
+
+	return 0;
+}
+#else
+static int dp83867_of_init(struct phy_device *phydev)
+{
+	struct dp83867_private *dp83867 = phydev->priv;
+
+	dp83867->rx_id_delay = DEFAULT_RX_ID_DELAY;
+	dp83867->tx_id_delay = DEFAULT_TX_ID_DELAY;
+	dp83867->fifo_depth = DEFAULT_FIFO_DEPTH;
+
+	return 0;
+}
+#endif
 
 static int dp83867_config(struct phy_device *phydev)
 {
+	struct dp83867_private *dp83867;
 	unsigned int val, delay, cfg2;
 	int ret;
 
+	if (!phydev->priv) {
+		dp83867 = kzalloc(sizeof(*dp83867), GFP_KERNEL);
+		if (!dp83867)
+			return -ENOMEM;
+
+		phydev->priv = dp83867;
+		ret = dp83867_of_init(phydev);
+		if (ret)
+			goto err_out;
+	} else {
+		dp83867 = (struct dp83867_private *)phydev->priv;
+	}
+
 	/* Restart the PHY.  */
 	val = phy_read(phydev, MDIO_DEVAD_NONE, DP83867_CTRL);
 	phy_write(phydev, MDIO_DEVAD_NONE, DP83867_CTRL,
@@ -166,9 +229,9 @@ static int dp83867_config(struct phy_device *phydev)
 	if (phy_interface_is_rgmii(phydev)) {
 		ret = phy_write(phydev, MDIO_DEVAD_NONE, MII_DP83867_PHYCTRL,
 			(DP83867_MDI_CROSSOVER_AUTO << DP83867_MDI_CROSSOVER) |
-			(FIFO_DEPTH << DP83867_PHYCR_FIFO_DEPTH_SHIFT));
+			(dp83867->fifo_depth << DP83867_PHYCR_FIFO_DEPTH_SHIFT));
 		if (ret)
-			return ret;
+			goto err_out;
 	} else {
 		phy_write(phydev, MDIO_DEVAD_NONE, MII_BMCR,
 			  (BMCR_ANENABLE | BMCR_FULLDPLX | BMCR_SPEED1000));
@@ -189,8 +252,8 @@ static int dp83867_config(struct phy_device *phydev)
 			  DP83867_PHYCTRL_SGMIIEN |
 			  (DP83867_MDI_CROSSOVER_MDIX <<
 			  DP83867_MDI_CROSSOVER) |
-			  (FIFO_DEPTH << DP83867_PHYCTRL_RXFIFO_SHIFT) |
-			  (FIFO_DEPTH  << DP83867_PHYCTRL_TXFIFO_SHIFT));
+			  (dp83867->fifo_depth << DP83867_PHYCTRL_RXFIFO_SHIFT) |
+			  (dp83867->fifo_depth << DP83867_PHYCTRL_TXFIFO_SHIFT));
 		phy_write(phydev, MDIO_DEVAD_NONE, MII_DP83867_BISCR, 0x0);
 	}
 
@@ -212,8 +275,8 @@ static int dp83867_config(struct phy_device *phydev)
 		phy_write_mmd_indirect(phydev, DP83867_RGMIICTL,
 				       DP83867_DEVADDR, phydev->addr, val);
 
-		delay = (RX_ID_DELAY |
-			 (TX_ID_DELAY << DP83867_RGMII_TX_CLK_DELAY_SHIFT));
+		delay = (dp83867->rx_id_delay |
+			 (dp83867->tx_id_delay << DP83867_RGMII_TX_CLK_DELAY_SHIFT));
 
 		phy_write_mmd_indirect(phydev, DP83867_RGMIIDCTL,
 				       DP83867_DEVADDR, phydev->addr, delay);
@@ -221,6 +284,10 @@ static int dp83867_config(struct phy_device *phydev)
 
 	genphy_config_aneg(phydev);
 	return 0;
+
+err_out:
+	kfree(dp83867);
+	return ret;
 }
 
 static struct phy_driver DP83867_driver = {
Signature · 1 line
2.8.1.116.g7b0d47b
#12 lore raw

PATCH v6 4/7 net: phy: ti: Allow the driver to be more configurable

Quoted 9 lines · Dan Murphy

Not all devices use the same internal delay or fifo depth. Add the ability to set the internal delay for rx or tx and the fifo depth via the devicetree. If the value is not set in the devicetree then set the delay to the default.

If devicetree is not used then use the default defines within the driver.

Tested this on dra72 rev C evm

Regards
Mugutnhan V N

#13 lore raw

PATCH v6 4/7 net: phy: ti: Allow the driver to be more configurable

In reply to Dan Murphy
Quoted 9 lines · Dan Murphy

Not all devices use the same internal delay or fifo depth. Add the ability to set the internal delay for rx or tx and the fifo depth via the devicetree. If the value is not set in the devicetree then set the delay to the default.

If devicetree is not used then use the default defines within the driver.

#14 lore raw

PATCH v6 4/7 net: phy: ti: Allow the driver to be more configurable

Quoted 6 lines · Joe Hershberger
Quoted 5 lines · Dan Murphy

Not all devices use the same internal delay or fifo depth. Add the ability to set the internal delay for rx or tx and the fifo depth via the devicetree. If the value is not set in the devicetree then set the delay to the default.

Quoted 6 lines
Quoted 4 lines

If devicetree is not used then use the default defines within the driver.

This patch is not checkpatch.pl clean. Please resubmit.

610950.mbox:140: WARNING: line over 80 characters 610950.mbox:153: WARNING: line over 80 characters 610950.mbox:154: WARNING: line over 80 characters 610950.mbox:165: WARNING: line over 80 characters
total: 0 errors, 4 warnings, 0 checks, 136 lines checked

author
#15 lore raw

PATCH v6 4/7 net: phy: ti: Allow the driver to be more configurable

Joe

Quoted 13 lines · Joe Hershberger
Quoted 11 lines · Joe Hershberger
Quoted 9 lines · Dan Murphy

Not all devices use the same internal delay or fifo depth. Add the ability to set the internal delay for rx or tx and the fifo depth via the devicetree. If the value is not set in the devicetree then set the delay to the default.

If devicetree is not used then use the default defines within the driver.

Quoted 8 lines

This patch is not checkpatch.pl clean. Please resubmit.

610950.mbox:140: WARNING: line over 80 characters 610950.mbox:153: WARNING: line over 80 characters 610950.mbox:154: WARNING: line over 80 characters 610950.mbox:165: WARNING: line over 80 characters
total: 0 errors, 4 warnings, 0 checks, 136 lines checked

How do you want me to rebase these patches on the SGMII work from Michal on the ti.c or off of master? The patch I submitted was based off of the SGMII patchset.

Need to know how you want to handle this as I see the SGMII code is not in the base line yet.

Dan

Signature · 2 lines
------------------
Dan Murphy
#16 lore raw

PATCH v6 4/7 net: phy: ti: Allow the driver to be more configurable

Quoted 19 lines · Dan Murphy

Joe

Quoted 16 lines · Joe Hershberger
Quoted 11 lines · Joe Hershberger
Quoted 9 lines · Dan Murphy

Not all devices use the same internal delay or fifo depth. Add the ability to set the internal delay for rx or tx and the fifo depth via the devicetree. If the value is not set in the devicetree then set the delay to the default.

If devicetree is not used then use the default defines within the driver.

This patch is not checkpatch.pl clean. Please resubmit.

Quoted 8 lines
Quoted 5 lines

610950.mbox:140: WARNING: line over 80 characters 610950.mbox:153: WARNING: line over 80 characters 610950.mbox:154: WARNING: line over 80 characters 610950.mbox:165: WARNING: line over 80 characters
total: 0 errors, 4 warnings, 0 checks, 136 lines checked

How do you want me to rebase these patches on the SGMII work from Michal on the ti.c or off of master? The patch I submitted was based off of the SGMII patchset.

I'm pulling in some of Michal's patches this release. Please reference which patches this depends on (patchwork links).

Quoted 2 lines

Need to know how you want to handle this as I see the SGMII code is not in the base line yet.

If the patches you depend on are acceptable (no changes requested) then definitely base your changes on them, but point them out to me.

Thanks,
-Joe

#17 lore raw

PATCH v6 4/7 net: phy: ti: Allow the driver to be more configurable

Hi Joe,

Quoted 26 lines · Joe Hershberger
Quoted 25 lines · Dan Murphy

Joe

Quoted 21 lines · Joe Hershberger
Quoted 11 lines · Joe Hershberger
Quoted 9 lines · Dan Murphy

Not all devices use the same internal delay or fifo depth. Add the ability to set the internal delay for rx or tx and the fifo depth via the devicetree. If the value is not set in the devicetree then set the delay to the default.

If devicetree is not used then use the default defines within the driver.

This patch is not checkpatch.pl clean. Please resubmit.

610950.mbox:140: WARNING: line over 80 characters 610950.mbox:153: WARNING: line over 80 characters 610950.mbox:154: WARNING: line over 80 characters 610950.mbox:165: WARNING: line over 80 characters
total: 0 errors, 4 warnings, 0 checks, 136 lines checked

Quoted 5 lines
Quoted 2 lines

How do you want me to rebase these patches on the SGMII work from Michal on the ti.c or off of master? The patch I submitted was based off of the SGMII patchset.

I'm pulling in some of Michal's patches this release. Please reference which patches this depends on (patchwork links).

NOTE: A lot of my patches (maybe all of them) were already merged to mainline via Xilinx tree.

Cheers,
Michal

author
#18 lore raw

PATCH v6 4/7 net: phy: ti: Allow the driver to be more configurable

Michal

Quoted 28 lines · Michal Simek

Hi Joe,

Quoted 25 lines · Joe Hershberger
Quoted 24 lines · Dan Murphy

Joe

Quoted 21 lines · Joe Hershberger
Quoted 11 lines · Joe Hershberger
Quoted 9 lines · Dan Murphy

Not all devices use the same internal delay or fifo depth. Add the ability to set the internal delay for rx or tx and the fifo depth via the devicetree. If the value is not set in the devicetree then set the delay to the default.

If devicetree is not used then use the default defines within the driver.

This patch is not checkpatch.pl clean. Please resubmit.

610950.mbox:140: WARNING: line over 80 characters 610950.mbox:153: WARNING: line over 80 characters 610950.mbox:154: WARNING: line over 80 characters 610950.mbox:165: WARNING: line over 80 characters
total: 0 errors, 4 warnings, 0 checks, 136 lines checked

Joe fixing these will break readability of the code. I will document this in the next patch submission

Quoted 6 lines
Quoted 4 lines
Quoted 2 lines

How do you want me to rebase these patches on the SGMII work from Michal on the ti.c or off of master? The patch I submitted was based off of the SGMII patchset.

I'm pulling in some of Michal's patches this release. Please reference which patches this depends on (patchwork links).

NOTE: A lot of my patches (maybe all of them) were already merged to mainline via Xilinx tree.

OK latest pull has the SGMII patches on the ti.c.

Quoted 2 lines

Cheers,
Michal

Signature · 2 lines
------------------
Dan Murphy
author
#19 lore raw

PATCH v6 5/7 net: phy: Move is_rgmii helper to phy.h

In reply to Dan Murphy

Move the phy_interface_is_rgmii to the phy.h file for all phy's to be able to use the API.

This now aligns with the Linux kernel based on commit e463d88c36d42211aa72ed76d32fb8bf37820ef1

---

v6 - No changes - https://patchwork.ozlabs.org/patch/608765/

 drivers/net/phy/ti.c | 11 -----------
 include/phy.h        | 11 +++++++++++
 2 files changed, 11 insertions(+), 11 deletions(-)
drivers/net/phy/ti.c +0 -11
index 4c4f0c1..4c19353 100644
@@ -156,17 +156,6 @@ void phy_write_mmd_indirect(struct phy_device *phydev, int prtad,
 	phy_write(phydev, addr, MII_MMD_DATA, data);
 }
 
-/**
- * phy_interface_is_rgmii - Convenience function for testing if a PHY interface
- * is RGMII (all variants)
- * @phydev: the phy_device struct
- */
-static inline bool phy_interface_is_rgmii(struct phy_device *phydev)
-{
-	return phydev->interface >= PHY_INTERFACE_MODE_RGMII &&
-		phydev->interface <= PHY_INTERFACE_MODE_RGMII_TXID;
-}
-
 #if defined(CONFIG_DM_ETH)
 /**
  * dp83867_data_init - Convenience function for setting PHY specific data
include/phy.h +11 -0
index 21459a8..7b2d1ff 100644
@@ -277,6 +277,17 @@ int get_phy_id(struct mii_dev *bus, int addr, int devad, u32 *phy_id);
  */
 int phy_get_interface_by_name(const char *str);
 
+/**
+ * phy_interface_is_rgmii - Convenience function for testing if a PHY interface
+ * is RGMII (all variants)
+ * @phydev: the phy_device struct
+ */
+static inline bool phy_interface_is_rgmii(struct phy_device *phydev)
+{
+	return phydev->interface >= PHY_INTERFACE_MODE_RGMII &&
+		phydev->interface <= PHY_INTERFACE_MODE_RGMII_TXID;
+}
+
 /* PHY UIDs for various PHYs that are referenced in external code */
 #define PHY_UID_CS4340  0x13e51002
 #define PHY_UID_TN2020	0x00a19410
Signature · 1 line
2.8.1.116.g7b0d47b
#20 lore raw

PATCH v6 5/7 net: phy: Move is_rgmii helper to phy.h

Quoted 9 lines · Dan Murphy

Move the phy_interface_is_rgmii to the phy.h file for all phy's to be able to use the API.

This now aligns with the Linux kernel based on commit e463d88c36d42211aa72ed76d32fb8bf37820ef1

Tested this on dra72 rev C evm

Regards
Mugutnhan V N

#21 lore raw

PATCH v6 5/7 net: phy: Move is_rgmii helper to phy.h

In reply to Dan Murphy
Quoted 9 lines · Dan Murphy

Move the phy_interface_is_rgmii to the phy.h file for all phy's to be able to use the API.

This now aligns with the Linux kernel based on commit e463d88c36d42211aa72ed76d32fb8bf37820ef1

author
#22 lore raw

PATCH v6 6/7 net: phy: Add phy_interface_is_sgmii to phy.h

In reply to Dan Murphy

Add a helper to phy.h to identify whether the phy is configured for SGMII all variables.

---

v6 - No changes - https://patchwork.ozlabs.org/patch/608766/

 include/phy.h | 11 +++++++++++
 1 file changed, 11 insertions(+)
include/phy.h +11 -0
index 7b2d1ff..ef3eb51 100644
@@ -288,6 +288,17 @@ static inline bool phy_interface_is_rgmii(struct phy_device *phydev)
 		phydev->interface <= PHY_INTERFACE_MODE_RGMII_TXID;
 }
 
+/**
+ * phy_interface_is_sgmii - Convenience function for testing if a PHY interface
+ * is SGMII (all variants)
+ * @phydev: the phy_device struct
+ */
+static inline bool phy_interface_is_sgmii(struct phy_device *phydev)
+{
+	return phydev->interface >= PHY_INTERFACE_MODE_SGMII &&
+		phydev->interface <= PHY_INTERFACE_MODE_QSGMII;
+}
+
 /* PHY UIDs for various PHYs that are referenced in external code */
 #define PHY_UID_CS4340  0x13e51002
 #define PHY_UID_TN2020	0x00a19410
Signature · 1 line
2.8.1.116.g7b0d47b
author
#25 lore raw

PATCH v6 7/7 net: phy: dp83867: Add SGMII helper for configuration

In reply to Dan Murphy

The code assumed that if the interface is not RGMII configured then it must be SGMII configured. This device has the ability to support most of the MII interfaces. Therefore add the helper for SGMII and only configure the device if the interface is configured for SGMII.

---

v6 - No changes - https://patchwork.ozlabs.org/patch/608767/

 drivers/net/phy/ti.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/phy/ti.c +1 -1
index 4c19353..c55dd97 100644
@@ -221,7 +221,7 @@ static int dp83867_config(struct phy_device *phydev)
 			(dp83867->fifo_depth << DP83867_PHYCR_FIFO_DEPTH_SHIFT));
 		if (ret)
 			goto err_out;
-	} else {
+	} else if (phy_interface_is_sgmii(phydev)) {
 		phy_write(phydev, MDIO_DEVAD_NONE, MII_BMCR,
 			  (BMCR_ANENABLE | BMCR_FULLDPLX | BMCR_SPEED1000));
 
Signature · 1 line
2.8.1.116.g7b0d47b
#26 lore raw

PATCH v6 7/7 net: phy: dp83867: Add SGMII helper for configuration

Quoted 9 lines · Dan Murphy

The code assumed that if the interface is not RGMII configured then it must be SGMII configured. This device has the ability to support most of the MII interfaces. Therefore add the helper for SGMII and only configure the device if the interface is configured for SGMII.

Tested this on dra72 rev C evm

Regards
Mugutnhan V N

#27 lore raw

PATCH v6 7/7 net: phy: dp83867: Add SGMII helper for configuration

In reply to Dan Murphy
Quoted 9 lines · Dan Murphy

The code assumed that if the interface is not RGMII configured then it must be SGMII configured. This device has the ability to support most of the MII interfaces. Therefore add the helper for SGMII and only configure the device if the interface is configured for SGMII.

#28 lore raw

PATCH v6 1/7 drivers: net: cpsw: Add reading of DT phy-handle node

In reply to Dan Murphy
Quoted 8 lines · Dan Murphy

Add the ability to read the phy-handle node of the cpsw slave. Upon reading this handle the phy-id can be stored based on the reg node in the DT.

The phy-handle also needs to be stored and passed to the phy to access any phy data that is available.

Tested this on dra72 rev C evm

Regards
Mugutnhan V N

#29 lore raw

PATCH v6 1/7 drivers: net: cpsw: Add reading of DT phy-handle node

In reply to Dan Murphy
Quoted 3 lines · Dan Murphy

Add the ability to read the phy-handle node of the cpsw slave. Upon reading this handle the phy-id can be stored based on the reg node in the DT.

It would be great if the phy could be handled generically. Unfortunately there is no uniform description so far, so having each driver parse it is the best we can do for now.

Quoted 4 lines

The phy-handle also needs to be stored and passed to the phy to access any phy data that is available.

#30 lore raw

PATCH v6 1/7 drivers: net: cpsw: Add reading of DT phy-handle node

Quoted 9 lines · Joe Hershberger
Quoted 3 lines · Dan Murphy

Add the ability to read the phy-handle node of the cpsw slave. Upon reading this handle the phy-id can be stored based on the reg node in the DT.

It would be great if the phy could be handled generically. Unfortunately there is no uniform description so far, so having each driver parse it is the best we can do for now.

Quoted 6 lines
Quoted 4 lines

The phy-handle also needs to be stored and passed to the phy to access any phy data that is available.

This patch is not checkpatch.pl clean. Please resubmit.

610946.mbox:57: WARNING: line over 80 characters 610946.mbox:59: WARNING: line over 80 characters 610946.mbox:62: WARNING: line over 80 characters 610946.mbox:62: CHECK: Alignment should match open parenthesis 610946.mbox:65: WARNING: line over 80 characters 610946.mbox:66: WARNING: line over 80 characters
total: 0 errors, 5 warnings, 1 checks, 39 lines checked

author
#31 lore raw

PATCH v6 1/7 drivers: net: cpsw: Add reading of DT phy-handle node

Joe

Quoted 18 lines · Joe Hershberger
Quoted 8 lines · Joe Hershberger
Quoted 3 lines · Dan Murphy

Add the ability to read the phy-handle node of the cpsw slave. Upon reading this handle the phy-id can be stored based on the reg node in the DT.

It would be great if the phy could be handled generically. Unfortunately there is no uniform description so far, so having each driver parse it is the best we can do for now.

Quoted 5 lines
Quoted 4 lines

The phy-handle also needs to be stored and passed to the phy to access any phy data that is available.

This patch is not checkpatch.pl clean. Please resubmit.

Quoted 7 lines

610946.mbox:57: WARNING: line over 80 characters 610946.mbox:59: WARNING: line over 80 characters 610946.mbox:62: WARNING: line over 80 characters 610946.mbox:62: CHECK: Alignment should match open parenthesis 610946.mbox:65: WARNING: line over 80 characters 610946.mbox:66: WARNING: line over 80 characters
total: 0 errors, 5 warnings, 1 checks, 39 lines checked

I can only fix a few there will still be at least 2 LTL warnings on this file and fixing it will break readability

I don't see how to fix this.

WARNING: line over 80 characters
#46: FILE: drivers/net/cpsw.c:1230:
+ if (priv->data.slave_data[slave_index].phy_of_handle >= 0) {

WARNING: line over 80 characters
#49: FILE: drivers/net/cpsw.c:1233:
+ priv->data.slave_data[slave_index].phy_of_handle,

Dan

Signature · 2 lines
------------------
Dan Murphy
#32 lore raw

PATCH v6 1/7 drivers: net: cpsw: Add reading of DT phy-handle node

Quoted 33 lines · Dan Murphy

Joe

Quoted 18 lines · Joe Hershberger
Quoted 8 lines · Joe Hershberger
Quoted 3 lines · Dan Murphy

Add the ability to read the phy-handle node of the cpsw slave. Upon reading this handle the phy-id can be stored based on the reg node in the DT.

It would be great if the phy could be handled generically. Unfortunately there is no uniform description so far, so having each driver parse it is the best we can do for now.

Quoted 5 lines
Quoted 4 lines

The phy-handle also needs to be stored and passed to the phy to access any phy data that is available.

This patch is not checkpatch.pl clean. Please resubmit.

Quoted 7 lines

610946.mbox:57: WARNING: line over 80 characters 610946.mbox:59: WARNING: line over 80 characters 610946.mbox:62: WARNING: line over 80 characters 610946.mbox:62: CHECK: Alignment should match open parenthesis 610946.mbox:65: WARNING: line over 80 characters 610946.mbox:66: WARNING: line over 80 characters
total: 0 errors, 5 warnings, 1 checks, 39 lines checked

I can only fix a few there will still be at least 2 LTL warnings on this file and fixing it will break readability

I don't see how to fix this.

Quoted 7 lines

WARNING: line over 80 characters
#46: FILE: drivers/net/cpsw.c:1230:
+ if (priv->data.slave_data[slave_index].phy_of_handle >= 0) {

WARNING: line over 80 characters
#49: FILE: drivers/net/cpsw.c:1233:
+ priv->data.slave_data[slave_index].phy_of_handle,

If you plan to have a patch that you feel can't be clean, please comment after the patch log with the reasoning. I had enough failures in the patches this release that I have not investigated each one on my own.

Thanks,
-Joe