All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Brunner <systemprogrammierung.brunner@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: drivshin.allworx@gmail.com, netdev@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	devicetree@vger.kernel.org, hs@denx.de, mugunthanvnm@ti.com,
	kernel@iktek.de, dtrautmann@ibhsoftec-sps.de
Subject: Re: [PATCH 0/3] drivers: net: cpsw: phy-handle fixes
Date: Wed, 23 Dec 2015 19:35:37 +0100	[thread overview]
Message-ID: <2375419.xULY4PYlNl@localhost> (raw)
In-Reply-To: <20151223.120425.2005941258192616350.davem@davemloft.net>

On Wednesday 23 December 2015 12:04:25 David Miller wrote:
> From: "David Rivshin (Allworx)" <drivshin.allworx@gmail.com>
> Date: Tue, 22 Dec 2015 19:36:31 -0500
> 
> > Testing by anyone who has real hardware using phy-handle or dual_emac
> > with fixed-link would be appreciated.
> 
> I'm going to wait for such testing before applying this series.
> 
> Thanks.

Successfully tested the following 3 configurations.
1. emac0 with phy_id and emac1 with fixed phy
2. emac0 with phy-handle and emac1 with fixed phy
3. emac0 with fixed phy and emac1 with fixed phy


Below are the affected DT nodes, with one cpsw_emac0 node choosen for each 
test.

&cpsw_emac0 {
	phy_id = <&davinci_mdio>, <5>;
	phy-mode = "mii";
	dual_emac_res_vlan = <4093>;
};

&cpsw_emac0 {
	phy-mode = "mii";
	dual_emac_res_vlan = <4093>;
	phy-handle = <&phy0>;
};

&cpsw_emac0 {
	phy-mode = "mii";
	dual_emac_res_vlan = <4093>;
	fixed-link {
		speed = <100>;
		full-duplex;
	};
};

&cpsw_emac1 {
	dual_emac_res_vlan = <4094>;
	phy-mode = "mii";
	fixed-link {
		speed = <100>;
		full-duplex;
	};
};

&davinci_mdio {
	status = "okay";
	phy0: ethernet-phy@0 {
		reg = <5>;
	};
};

ps: I don't have access to the board for the next 2 weeks.

WARNING: multiple messages have this Message-ID (diff)
From: systemprogrammierung.brunner@gmail.com (Markus Brunner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] drivers: net: cpsw: phy-handle fixes
Date: Wed, 23 Dec 2015 19:35:37 +0100	[thread overview]
Message-ID: <2375419.xULY4PYlNl@localhost> (raw)
In-Reply-To: <20151223.120425.2005941258192616350.davem@davemloft.net>

On Wednesday 23 December 2015 12:04:25 David Miller wrote:
> From: "David Rivshin (Allworx)" <drivshin.allworx@gmail.com>
> Date: Tue, 22 Dec 2015 19:36:31 -0500
> 
> > Testing by anyone who has real hardware using phy-handle or dual_emac
> > with fixed-link would be appreciated.
> 
> I'm going to wait for such testing before applying this series.
> 
> Thanks.

Successfully tested the following 3 configurations.
1. emac0 with phy_id and emac1 with fixed phy
2. emac0 with phy-handle and emac1 with fixed phy
3. emac0 with fixed phy and emac1 with fixed phy


Below are the affected DT nodes, with one cpsw_emac0 node choosen for each 
test.

&cpsw_emac0 {
	phy_id = <&davinci_mdio>, <5>;
	phy-mode = "mii";
	dual_emac_res_vlan = <4093>;
};

&cpsw_emac0 {
	phy-mode = "mii";
	dual_emac_res_vlan = <4093>;
	phy-handle = <&phy0>;
};

&cpsw_emac0 {
	phy-mode = "mii";
	dual_emac_res_vlan = <4093>;
	fixed-link {
		speed = <100>;
		full-duplex;
	};
};

&cpsw_emac1 {
	dual_emac_res_vlan = <4094>;
	phy-mode = "mii";
	fixed-link {
		speed = <100>;
		full-duplex;
	};
};

&davinci_mdio {
	status = "okay";
	phy0: ethernet-phy at 0 {
		reg = <5>;
	};
};

ps: I don't have access to the board for the next 2 weeks.

  reply	other threads:[~2015-12-23 18:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-23  0:36 [PATCH 0/3] drivers: net: cpsw: phy-handle fixes David Rivshin (Allworx)
2015-12-23  0:36 ` David Rivshin (Allworx)
2015-12-23  0:36 ` [PATCH 1/3] drivers: net: cpsw: fix parsing of phy-handle DT property in dual_emac config David Rivshin (Allworx)
2015-12-23  0:36   ` David Rivshin (Allworx)
2015-12-23  0:36 ` [PATCH 2/3] drivers: net: cpsw: fix error messages when using phy-handle DT property David Rivshin (Allworx)
2015-12-23  0:36   ` David Rivshin (Allworx)
2015-12-29 20:30   ` Rob Herring
2015-12-29 20:30     ` Rob Herring
2015-12-23  0:36 ` [PATCH 3/3] drivers: net: cpsw: use of_phy_connect() in fixed-link case David Rivshin (Allworx)
2015-12-23  0:36   ` David Rivshin (Allworx)
2015-12-23 17:04 ` [PATCH 0/3] drivers: net: cpsw: phy-handle fixes David Miller
2015-12-23 17:04   ` David Miller
2015-12-23 18:35   ` Markus Brunner [this message]
2015-12-23 18:35     ` Markus Brunner
2015-12-23 21:51     ` David Rivshin (Allworx)
2015-12-23 21:51       ` David Rivshin (Allworx)
     [not found] ` <CABr+WT=oDpp56jouAD57UM8_38geD1MMizZcDnx14maf2ohpCw@mail.gmail.com>
2015-12-23 21:54   ` David Rivshin (Allworx)
2015-12-23 21:54     ` David Rivshin (Allworx)
     [not found]     ` <CABr+WTm=Oo16=qB6dyO6ZhUUz0307ROi=o270Rac2R4W5-usjg@mail.gmail.com>
2015-12-24  1:18       ` David Rivshin (Allworx)
2015-12-24  1:18         ` David Rivshin (Allworx)
2015-12-24  9:10         ` Markus Brunner
2015-12-24  9:10           ` Markus Brunner
2016-02-13  1:28         ` David Rivshin (Allworx)
2016-02-13  1:28           ` David Rivshin (Allworx)

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=2375419.xULY4PYlNl@localhost \
    --to=systemprogrammierung.brunner@gmail.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=drivshin.allworx@gmail.com \
    --cc=dtrautmann@ibhsoftec-sps.de \
    --cc=hs@denx.de \
    --cc=kernel@iktek.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mugunthanvnm@ti.com \
    --cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.