From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
Alexander Holler <holler@ahsoftware.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
Michal Simek <michal.simek@xilinx.com>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH regression] net: phy: fix initialization (config_init) for Marvel 88E1116R PHYs
Date: Wed, 02 Apr 2014 22:25:02 +0200 [thread overview]
Message-ID: <533C721E.1080004@gmail.com> (raw)
In-Reply-To: <CAGVrzcZi5aNq8fR795fKhu2TAc1tQCa2YEorErZRLf2n9DPZuw@mail.gmail.com>
On 04/02/2014 09:01 PM, Florian Fainelli wrote:
> 2014-04-02 2:09 GMT-07:00 Alexander Holler <holler@ahsoftware.de>:
>> Am 02.04.2014 02:57, schrieb Florian Fainelli:
>>> 2014-04-01 16:55 GMT-07:00 Alexander Holler <holler@ahsoftware.de>:
>>>> Commit 7cd1463664c2a15721ff4ccfb61d4d970815cb3d (introduced with 3.14)
>>>> changed the initialization of the mv643xx_eth driver to use phy_init_hw()
>>>> to reset the PHY. Unfortunately the initialization for the 88E1116R PHY
>>>> was broken such, that it used mdelay() instead of really waiting for a
>>>> reset to finish.
>
> Can you resubmit with the following information:
>
> - you specify the commit that introduce the problem in parenthesis,
> e.g: deadbeef ("dead: beef: cafe babe")
> - put this dmesg snippet in your log message to clearly illustrate
> what is happening
> - clarify that the PHY needs to be polled in a comment in
> m88e1116r_config_init()
>
> Meanwhile, it would be good if someone with access to this particular
> PHY datasheet could look for known erratas, problems, non-standard
> compliant behavior ....
Alexander,
I tried todays linux/master on Seagate Dockstar with Marvell 88E1116R
(0x01410e40) and cannot reproduce any regression. I tried booting from
tftp and usb, I also rebooted twice to see if there are any side
effects - nothing - ethernet always comes up as expected.
I am curious, how you determined above commit to be the cause of the
regression you are seeing. Can you bisect, if you didn't already?
Sebastian
next prev parent reply other threads:[~2014-04-02 20:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 23:55 [PATCH regression] net: phy: fix initialization (config_init) for Marvel 88E1116R PHYs Alexander Holler
2014-04-02 0:00 ` Florian Fainelli
2014-04-02 0:57 ` Florian Fainelli
2014-04-02 9:09 ` Alexander Holler
2014-04-02 10:54 ` Alexander Holler
2014-04-02 19:01 ` Florian Fainelli
2014-04-02 20:25 ` Sebastian Hesselbarth [this message]
2014-04-02 22:12 ` Alexander Holler
2014-04-02 22:20 ` Florian Fainelli
2014-04-02 22:27 ` Sebastian Hesselbarth
2014-04-03 7:17 ` Alexander Holler
2014-04-03 8:49 ` Sebastian Hesselbarth
2014-04-03 15:06 ` Alexander Holler
2014-04-03 15:14 ` David Miller
2014-04-03 15:45 ` Alexander Holler
2014-04-03 15:45 ` Sebastian Hesselbarth
2014-04-03 15:58 ` Alexander Holler
2014-04-03 17:58 ` Bug(s) with netconsole (using mv643xx_eth on Kirkwood) Alexander Holler
2014-04-03 18:21 ` Sebastian Hesselbarth
2014-04-03 18:23 ` Alexander Holler
2014-04-03 18:39 ` Alexander Holler
2014-04-03 18:44 ` Florian Fainelli
2014-04-04 11:36 ` Alexander Holler
2014-04-03 17:44 ` [PATCH regression] net: phy: fix initialization (config_init) for Marvel 88E1116R PHYs Sebastian Hesselbarth
2014-04-03 18:20 ` Alexander Holler
2014-04-02 22:30 ` Sebastian Hesselbarth
2014-04-02 11:51 ` Sergei Shtylyov
2014-04-02 12:07 ` Sergei Shtylyov
2014-04-02 14:35 ` Alexander Holler
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=533C721E.1080004@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=holler@ahsoftware.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=stable@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).