From: Florian Fainelli <f.fainelli@gmail.com>
To: Stefan Agner <stefan@agner.ch>, david.choi@micrel.com
Cc: netdev@vger.kernel.org
Subject: Re: Micrel PHY and power down mode
Date: Wed, 10 Feb 2016 14:10:32 -0800 [thread overview]
Message-ID: <56BBB558.3010205@gmail.com> (raw)
In-Reply-To: <ea1cb242a247bc6665947ab9a77cb454@agner.ch>
Hi Stefan,
On 10/02/16 11:25, Stefan Agner wrote:
> Hi David, Hi Florian,
>
> We use a Micrel KSZ8041NL and we observe sometimes continuous RX errors
> (PHY's RXER counter is continuously incrementing, activity LED blinks
> and no communication is possible). It seems that only some PHY's are
> affected (3-4%) and only in certain temperature ranges (the PHY I can
> reproduce the issue here shows the problem ~30°C). We could narrow the
> issue down, and realized that the problem only appears after the PHY has
> been in power down mode. Since Linux calls suspend/resume when
> attaching/detaching the PHY, a simple ifup/ifdown bascially can trigger
> the issue.
>
> Currently, the wakeup sequence writes the following registers
> 0x8000 to 0x00 (phy_attach_direct -> phy_init_hw -> genphy_soft_reset)
> 0x3000 to 0x00 (phy_attach_direct -> genphy_resume)
>
> I am not sure if this sequence is really ok. It seems to me that
> genphy_soft_reset clears the power down bit already, which makes
> genphy_resume somewhat useless. However, altering the behavior of
> genphy_soft_reset to not clear the power down bit (yet) did not resolve
> the issue.
AFAIR, issuing a BMCR reset, with a PHY which was in power down should
clear the power down bit, but I would not be surprised if some PHYs were
not quite behaving like that though.
>
> Is clearing the power down bit and generating the reset in one go
> intended? I checked the datasheet, and did not found particular
> information about the "resume" sequence...
Does it help if your PHY resume callback does the same thing as what the
config_init() does? You have the ability to skip the generic software
reset of the PHY via BMCR bit 15, and instead do nothing by implementing
your own soft_reset() callback, that might tell you whether the software
reset is what is screwing things up?
Getting some insight from somebody at Micrel would definitively help
with understanding what a workaround or fix would look like.
HTH
--
Florian
next prev parent reply other threads:[~2016-02-10 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 19:25 Micrel PHY and power down mode Stefan Agner
2016-02-10 22:10 ` Florian Fainelli [this message]
2016-02-10 22:20 ` Stefan Agner
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=56BBB558.3010205@gmail.com \
--to=f.fainelli@gmail.com \
--cc=david.choi@micrel.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 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.