From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Alexander Holler <holler@ahsoftware.de>,
Florian Fainelli <f.fainelli@gmail.com>
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: Thu, 03 Apr 2014 00:30:17 +0200 [thread overview]
Message-ID: <533C8F79.2030707@gmail.com> (raw)
In-Reply-To: <533BD3CD.1010905@ahsoftware.de>
On 04/02/2014 11:09 AM, Alexander Holler wrote:
> Am 02.04.2014 02:57, schrieb Florian Fainelli:
>> Could you verify the following two things before your patch gets merged:
>>
>> - how long does it take for your PHY to clear the BMCR_RESET bit, is
>> it more than the allowed time out in
>> drivers/net/phy/phy_device.c::phy_poll_reset
>> - is your PHY powered down (check BMCR_PWRDOWN), if that is the case,
>> we might be hitting some corner case where toggling BMCR_RESET will
>> power it on, but at the expense of waiting longer
>
> I've done two tests with pr_info before and after the two resets in
> m88e1116r_config_init:
>
[...]
> with mdelay (the value after reset is what contains MII_BMCR):
>
> -----------------------
> dmesg | grep -A1 -B1 AHO
> [ 1.090072] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version
> 1.4
> [ 1.175888] AHO: before first reset
> [ 1.678806] AHO: after first reset 0x0
> [ 1.683281] AHO: before second reset
> [ 2.186288] AHO: after second reset 0x0
> [ 2.191010] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC
> address xx
> --
> [ 2.426349] netpoll: netconsole: device eth0 not up yet, forcing it
> [ 2.505917] AHO: before first reset
> [ 2.605824] usb 1-1: new high-speed USB device number 2 using orion-ehci
> --
> [ 2.829987] hub 1-1:1.0: 4 ports detected
> [ 3.044502] AHO: after first reset 0x0
If the above hex at the end is BMCR..
> [ 3.049133] AHO: before second reset
> [ 3.126110] usb 1-1.1: new high-speed USB device number 3 using
> orion-ehci
> --
> [ 3.526107] usb 1-1.3: device descriptor read/64, error -32
> [ 3.614264] AHO: after second reset 0x0
> [ 3.618708] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> --
> [ 21.335730] Adding 2996116k swap on /dev/sda3. Priority:-1 extents:1
> across:2996116k
> [ 28.195942] AHO: before first reset
> [ 28.696270] AHO: after first reset 0x800
.. have you noticed that your PHY enters POWERDOWN here?
Sebastian
> [ 28.696958] AHO: before second reset
> [ 29.197354] AHO: after second reset 0x800
> [ 111.612263] RPC: Registered named UNIX socket transport module.
> -----------------------
next prev parent reply other threads:[~2014-04-02 22:30 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
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 [this message]
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=533C8F79.2030707@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 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.