From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jeff Haran <jharan@Brocade.COM>
Cc: ebs@ebshome.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] IBM PPC EMAC driver:improved support for PHY configuration
Date: Fri, 27 Apr 2007 10:18:36 +1000 [thread overview]
Message-ID: <1177633116.14873.271.camel@localhost.localdomain> (raw)
In-Reply-To: <46F9780F64AE9945815725F4C0C72CB802A6DE66@hq-exch-1.corp.brocade.com>
On Thu, 2007-04-26 at 16:18 -0700, Jeff Haran wrote:
> From: Jeff Haran <jharan@brocade.com>
>
> This patch fixes some problems I found while debugging the IBM EMAC
> driver for PPC32 systems.
> The first problem was in the function that configures the PHY for
> autonegotiation, genmii_setup_aneg(). The original code does a
> read/modify/write of the autonegotiation advertizement register (reg 4),
> followed by a read/modify/write of the control register (reg 0). While
> the original code follows the proper procedure as per reading the IEEE
> specs, what I found is that on at least one PHY model (National DP83843)
> the read of the control register comes back with the soft reset bit set
> (bit 15).
Good catch ! I've seen that behaviour in the past too. Note that sungem
has this problem too.
.../...
> The second problem was in the function that configures the PHY for
> forced operation, genmii_setup_forced(). The original code initiates a
> software reset operation via a write of a 1 to bit 15 of the control
> register (reg 0), but then proceeds to do a second write to that same
> register without waiting until that reset bit is cleared by the PHY
> itself (which according to the IEEE specs indicates that the PHY reset
> is complete). This is a violation of how one is supposed to use this
> software reset feature of these PHYs and I believe was the cause of
> mysterious, difficult to reproduce link failures that we've observed on
> some of our systems that use this driver. The fix is to modify the
> function so that it spins waiting for the reset bit to clear after doing
> the soft reset and before doing the subsequent write. Since this
> modification, we haven't seen the mysterious link failures, though they
> were so rare its difficult to say at this point whether this was the
> cause.
This is also a bug inherited from sungem (thus my fault).
> I also added some error handling and reporting for the abnormal case
> where the reset bit never clears from the soft reset operation.
> Applied to kernel version 2.6.21.
Your patch appears to have been line wrapped by your mailer though...
Cheers,
Ben.
next prev parent reply other threads:[~2007-04-27 0:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 23:18 Jeff Haran
2007-04-27 0:18 ` Benjamin Herrenschmidt [this message]
2007-04-27 0:28 ` [PATCH 1/1] IBM PPC EMAC driver:improved support for PHYconfiguration Jeff Haran
2007-04-27 1:46 ` Benjamin Herrenschmidt
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=1177633116.14873.271.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=ebs@ebshome.net \
--cc=jharan@Brocade.COM \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®