linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philippe Schenker <philippe.schenker@toradex.com>
To: "tony@atomide.com" <tony@atomide.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"grygorii.strashko@ti.com" <grygorii.strashko@ti.com>
Cc: "o.rempel@pengutronix.de" <o.rempel@pengutronix.de>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"andrew@lunn.ch" <andrew@lunn.ch>
Subject: Re: [PATCH next] ARM: dts: am57xx: fix networking on boards with ksz9031 phy
Date: Thu, 7 May 2020 08:42:50 +0000	[thread overview]
Message-ID: <eab549aed345683a3ee79835369169c99e003488.camel@toradex.com> (raw)
In-Reply-To: <20200506191124.31569-1-grygorii.strashko@ti.com>

On Wed, 2020-05-06 at 22:11 +0300, Grygorii Strashko wrote:
> Since commit bcf3440c6dd7 ("net: phy: micrel: add phy-mode support for
> the
> KSZ9031 PHY") the networking is broken on boards:
>  am571x-idk
>  am572x-idk
>  am574x-idk
>  am57xx-beagle-x15
> 
> All above boards have phy-mode = "rgmii" and this is worked before
> because
> KSZ9031 PHY started with default RGMII internal delays configuration
> (TX
> off, RX on 1.2 ns) and MAC provided TX delay. After above commit, the
> KSZ9031 PHY starts handling phy mode properly and disables RX delay,
> as
> result networking is become broken.
> 
> Fix it by switching to phy-mode = "rgmii-rxid" to reflect previous
> behavior.
> 
> Cc: Oleksij Rempel <o.rempel@pengutronix.de>
> Cc: Andrew Lunn <andrew@lunn.ch>
> Cc: Philippe Schenker <philippe.schenker@toradex.com>
> Fixes: commit bcf3440c6dd7 ("net: phy: micrel: add phy-mode support
> for the KSZ9031 PHY")
> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>

Thanks Grygorii!

Reviewed-by: Philippe Schenker <
philippe.schenker@toradex.com>

> ---
>  arch/arm/boot/dts/am571x-idk.dts                | 4 ++--
>  arch/arm/boot/dts/am57xx-beagle-x15-common.dtsi | 4 ++--
>  arch/arm/boot/dts/am57xx-idk-common.dtsi        | 4 ++--
>  3 files changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/am571x-idk.dts
> b/arch/arm/boot/dts/am571x-idk.dts
> index 669559c9c95b..c13756fa0f55 100644
> --- a/arch/arm/boot/dts/am571x-idk.dts
> +++ b/arch/arm/boot/dts/am571x-idk.dts
> @@ -190,13 +190,13 @@
>  
>  &cpsw_port1 {
>  	phy-handle = <&ethphy0_sw>;
> -	phy-mode = "rgmii";
> +	phy-mode = "rgmii-rxid";
>  	ti,dual-emac-pvid = <1>;
>  };
>  
>  &cpsw_port2 {
>  	phy-handle = <&ethphy1_sw>;
> -	phy-mode = "rgmii";
> +	phy-mode = "rgmii-rxid";
>  	ti,dual-emac-pvid = <2>;
>  };
>  
> diff --git a/arch/arm/boot/dts/am57xx-beagle-x15-common.dtsi
> b/arch/arm/boot/dts/am57xx-beagle-x15-common.dtsi
> index a813a0cf3ff3..565675354de4 100644
> --- a/arch/arm/boot/dts/am57xx-beagle-x15-common.dtsi
> +++ b/arch/arm/boot/dts/am57xx-beagle-x15-common.dtsi
> @@ -433,13 +433,13 @@
>  
>  &cpsw_emac0 {
>  	phy-handle = <&phy0>;
> -	phy-mode = "rgmii";
> +	phy-mode = "rgmii-rxid";
>  	dual_emac_res_vlan = <1>;
>  };
>  
>  &cpsw_emac1 {
>  	phy-handle = <&phy1>;
> -	phy-mode = "rgmii";
> +	phy-mode = "rgmii-rxid";
>  	dual_emac_res_vlan = <2>;
>  };
>  
> diff --git a/arch/arm/boot/dts/am57xx-idk-common.dtsi
> b/arch/arm/boot/dts/am57xx-idk-common.dtsi
> index aa5e55f98179..a3ff1237d1fa 100644
> --- a/arch/arm/boot/dts/am57xx-idk-common.dtsi
> +++ b/arch/arm/boot/dts/am57xx-idk-common.dtsi
> @@ -408,13 +408,13 @@
>  
>  &cpsw_emac0 {
>  	phy-handle = <&ethphy0>;
> -	phy-mode = "rgmii";
> +	phy-mode = "rgmii-rxid";
>  	dual_emac_res_vlan = <1>;
>  };
>  
>  &cpsw_emac1 {
>  	phy-handle = <&ethphy1>;
> -	phy-mode = "rgmii";
> +	phy-mode = "rgmii-rxid";
>  	dual_emac_res_vlan = <2>;
>  };
>  

  reply	other threads:[~2020-05-07  8:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 19:11 [PATCH next] ARM: dts: am57xx: fix networking on boards with ksz9031 phy Grygorii Strashko
2020-05-07  8:42 ` Philippe Schenker [this message]
2020-05-07 17:51   ` Tony Lindgren

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=eab549aed345683a3ee79835369169c99e003488.camel@toradex.com \
    --to=philippe.schenker@toradex.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=grygorii.strashko@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=tony@atomide.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).