The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco.dolcini@toradex.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Francesco Dolcini <francesco.dolcini@toradex.com>,
	f.fainelli@gmail.com, Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Stefan Agner <stefan@agner.ch>,
	Marcel Ziswiler <marcel.ziswiler@toradex.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] phy: micrel: ksz8041nl: do not use power down mode
Date: Mon, 18 Oct 2021 12:18:02 +0200	[thread overview]
Message-ID: <20211018101802.GA7669@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <180289ac-4480-1e4c-d679-df4f0478ec65@csgroup.eu>

Hello Christophe,

On Mon, Oct 18, 2021 at 11:53:03AM +0200, Christophe Leroy wrote:
> 
> 
> Le 18/10/2021 à 11:42, Francesco Dolcini a écrit :
> > From: Stefan Agner <stefan@agner.ch>
> > 
> > Some Micrel KSZ8041NL PHY chips exhibit continous RX errors after using
> > the power down mode bit (0.11). If the PHY is taken out of power down
> > mode in a certain temperature range, the PHY enters a weird state which
> > leads to continously reporting RX errors. In that state, the MAC is not
> > able to receive or send any Ethernet frames and the activity LED is
> > constantly blinking. Since Linux is using the suspend callback when the
> > interface is taken down, ending up in that state can easily happen
> > during a normal startup.
> > 
> > Micrel confirmed the issue in errata DS80000700A [*], caused by abnormal
> > clock recovery when using power down mode. Even the latest revision (A4,
> > Revision ID 0x1513) seems to suffer that problem, and according to the
> > errata is not going to be fixed.
> > 
> > Remove the suspend/resume callback to avoid using the power down mode
> > completely.
> 
> As far as I can see in the ERRATA, KSZ8041 RNLI also has the bug.
> Shoudn't you also remove the suspend/resume on that one (which follows in
> ksphy_driver[])

Yes, I could, however this patch is coming out of a real issue we had with
KSZ8041NL with this specific phy id (and we have such a patch in our linux
branch since years).

On the other hand the entry for KSZ8041RNLI in the driver is somehow weird,
since the phy id according to the original commit does not even exists on
the datasheet. Would you be confident applying such errata for that phyid
without having a way of testing it?

Francesco


  reply	other threads:[~2021-10-18 10:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18  9:42 [PATCH net-next] phy: micrel: ksz8041nl: do not use power down mode Francesco Dolcini
2021-10-18  9:53 ` Christophe Leroy
2021-10-18 10:18   ` Francesco Dolcini [this message]
2021-10-18 10:46     ` Christophe Leroy
2021-10-18 11:27       ` Francesco Dolcini
2021-10-18 11:57         ` Christophe Leroy
2021-10-18 16:52 ` Jakub Kicinski
2021-10-18 17:16   ` Francesco Dolcini
2021-10-18 17:27     ` Jakub Kicinski

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=20211018101802.GA7669@francesco-nb.int.toradex.com \
    --to=francesco.dolcini@toradex.com \
    --cc=andrew@lunn.ch \
    --cc=christophe.leroy@csgroup.eu \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=marcel.ziswiler@toradex.com \
    --cc=netdev@vger.kernel.org \
    --cc=stefan@agner.ch \
    /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