From: Stefan Roese <sr@denx.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net: ibm_newemac: Don't start autonegotiation when disabled in BMCR (genmii)
Date: Tue, 19 Jul 2011 13:59:57 +0200 [thread overview]
Message-ID: <201107191359.57421.sr@denx.de> (raw)
In-Reply-To: <1311075322.25044.418.camel@pasglop>
Hi Ben,
On Tuesday 19 July 2011 13:35:22 Benjamin Herrenschmidt wrote:
> On Tue, 2011-07-19 at 12:50 +0200, Stefan Roese wrote:
> > As noticed on a custom 440GX board using the Micrel KSZ8041 PHY in
> > fiber mode, a strapped fixed PHY configuration will currently restart
> > the autonegotiation. This patch checks the BMCR_ANENABLE bit and
> > skips this autonegotiation if its disabled.
>
> Won't that just break aneg on everything else ?
>
> IE, most other PHYs rely on ANENABLE being set further down this same
> function (especially if the FW doesn't do it but even then, we may reset
> PHYs along the way etc...)
If aneg is enabled for a PHY (e.g. not strapped to fixed configuration), I
don't see how this patch will change the current aneg behaviour. Perhaps I'm
missing something, but I tested this on some boards with aneg enabled (Sequoia
etc). And I didn't notice any problems.
> This is something that really a case where the device-tree should
> indicate that aneg shall not be performed and from there don't call
> setup_aneg at all.
I feel that this BMCR_ANENABLE bit should be evaluated, but I have no strong
preference here. If you prefer that this should be handled via a new dt
property (phy-aneg = "disabled" ?), I can implement it this way. Just let me
know.
Thanks,
Stefan
next prev parent reply other threads:[~2011-07-19 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 10:50 [PATCH] net: ibm_newemac: Don't start autonegotiation when disabled in BMCR (genmii) Stefan Roese
2011-07-19 11:35 ` Benjamin Herrenschmidt
2011-07-19 11:59 ` Stefan Roese [this message]
2011-07-19 12:29 ` Benjamin Herrenschmidt
2011-07-20 7:18 ` Stefan Roese
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=201107191359.57421.sr@denx.de \
--to=sr@denx.de \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--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 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).