All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ioana Ciornei <ciorneiioana@gmail.com>
To: "Michal Vokáč" <michal.vokac@ysoft.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Jonathan McDowell <noodles@earth.li>,
	Florian Fainelli <f.fainelli@gmail.com>,
	David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org
Subject: Re: Broken imx6 to QCA8334 connection since PHYLIB to PHYLINK conversion
Date: Tue, 13 Apr 2021 20:49:15 +0300	[thread overview]
Message-ID: <20210413174915.uu2senujpqubmcnw@skbuf> (raw)
In-Reply-To: <9fa83984-f385-4705-a50f-688928cc366f@ysoft.com>

On Tue, Apr 13, 2021 at 09:09:37AM +0200, Michal Vokáč wrote:
> On 12. 04. 21 16:14, Andrew Lunn wrote:
> > > [1] https://elixir.bootlin.com/linux/v5.12-rc7/source/arch/arm/boot/dts/imx6dl-yapp4-common.dtsi#L101
> > 
> > &fec {
> > 	pinctrl-names = "default";
> > 	pinctrl-0 = <&pinctrl_enet>;
> > 	phy-mode = "rgmii-id";
> > 	phy-reset-gpios = <&gpio1 25 GPIO_ACTIVE_LOW>;
> > 	phy-reset-duration = <20>;
> > 	phy-supply = <&sw2_reg>;
> > 	phy-handle = <&ethphy0>;
> > 	status = "okay";
> > 
> > 	mdio {
> > 		#address-cells = <1>;
> > 		#size-cells = <0>;
> > 
> > 		phy_port2: phy@1 {
> > 			reg = <1>;
> > 		};
> > 
> > 		phy_port3: phy@2 {
> > 			reg = <2>;
> > 		};
> > 
> > 		switch@10 {
> > 			compatible = "qca,qca8334";
> > 			reg = <10>;
> > 
> > 			switch_ports: ports {
> > 				#address-cells = <1>;
> > 				#size-cells = <0>;
> > 
> > 				ethphy0: port@0 {
> > 					reg = <0>;
> > 					label = "cpu";
> > 					phy-mode = "rgmii-id";
> > 					ethernet = <&fec>;
> > 
> > 					fixed-link {
> > 						speed = <1000>;
> > 						full-duplex;
> > 					};
> > 				};
> > 
> > The fec phy-handle = <&ethphy0>; is pointing to the PHY of switch port
> > 0. This seems wrong.
> 

Actually, the phy-handle is pointing directly to the switch port 0 node.

> I do not understand. Why this seems wrong?

The phy-handle property should point to a node representing a PHY
device. If a fixed-link subnode is present, no phy-handle is needed.

> The switch has four ports. Ports 2 and 3 have a PHY and are connected
> to the transformers/RJ45 connectors. Port 0 is MII/RMII/RGMII of
> the switch. Port 6 (not used) is a SerDes.
> 
> > Does the FEC have a PHY? Do you connect the FEC
> > and the SWITCH at the RGMII level? Or with two back to back PHYs?
> > 
> > If you are doing it RGMII level, the FEC also needs a fixed-link.
> 
> The FEC does not have PHY and is connected to the switch at RGMII level.
> Adding the fixed-link { speed = <1000>; full-duplex; }; subnode to FEC
> does not help.
> 

Did you also remove the extra phy-handle when you tested?

Ioana

      parent reply	other threads:[~2021-04-13 17:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 13:28 Broken imx6 to QCA8334 connection since PHYLIB to PHYLINK conversion Michal Vokáč
2021-04-12 14:14 ` Andrew Lunn
2021-04-13  7:09   ` Michal Vokáč
2021-04-13 12:44     ` Andrew Lunn
2021-04-13 13:26       ` Michal Vokáč
2021-04-13 17:49     ` Ioana Ciornei [this message]

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=20210413174915.uu2senujpqubmcnw@skbuf \
    --to=ciorneiioana@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=michal.vokac@ysoft.com \
    --cc=netdev@vger.kernel.org \
    --cc=noodles@earth.li \
    /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.