netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Murali Karicheri <m-karicheri2@ti.com>
Cc: netdev@vger.kernel.org, "Kwok, WingMan" <w-kwok2@ti.com>
Subject: Re: Marvell Phy (1510) issue since v4.7 kernel
Date: Mon, 9 Jan 2017 23:56:41 +0100	[thread overview]
Message-ID: <20170109225641.GB22820@lunn.ch> (raw)
In-Reply-To: <587410EF.5090607@ti.com>

On Mon, Jan 09, 2017 at 05:38:39PM -0500, Murali Karicheri wrote:
> Hello Charles-Antoine, Andrew,
> 
> We have recently upgraded our kernel to v4.9 and started seeing an issue
> on our Keystone EVMs (K2E/L) that uses Marvel Phy 1510. The issue is that
> when we do a reboot command from the Linux console or do a SoC reset,
> the DHCP times out at U-Boot due to Phy auto negotiation failure. This works
> fine when the board is power cycled.

I've seen similar before. What version of kernel are you upgrading
from?

The problem i've had is that on shutdown/reboot, linux powers the PHYs
off. The uboot i have does not power them on again. Clearly a uboot
issue, it should not assume the PHYs are powered on.

I work around this with a uboot command:

mii write 1 0 0x3100

where the PHY is at address 1 on the bus. This writes to register 0,
and the import bit which needs setting to 0 is bit 11.

If mii read shows bit 11 is set, you know there uboot did not power up
the PHY.

    Andrew

  reply	other threads:[~2017-01-09 22:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-09 22:38 Marvell Phy (1510) issue since v4.7 kernel Murali Karicheri
2017-01-09 22:56 ` Andrew Lunn [this message]
2017-01-09 23:48   ` Kwok, WingMan
2017-01-09 23:55     ` Andrew Lunn
2017-01-10  1:37       ` Kwok, WingMan
2017-01-10  1:53         ` Andrew Lunn
2017-01-11 22:18           ` Kwok, WingMan
2017-01-11 22:27             ` Andrew Lunn
2017-01-11 22:32               ` Kwok, WingMan
2017-01-11 22:41               ` Kwok, WingMan
2017-01-11 22:59                 ` Andrew Lunn
2017-01-11 23:09                   ` Kwok, WingMan
2017-01-11 23:22                     ` Andrew Lunn
2017-01-12  0:31                       ` Kwok, WingMan
2017-01-12  1:06                         ` Andrew Lunn
2017-01-12 21:31                           ` Kwok, WingMan
2017-01-12 21:41                             ` Russell King - ARM Linux
2017-01-12 22:40                               ` Kwok, WingMan
2017-01-12 21:49                             ` Andrew Lunn
2017-01-12 22:31                               ` Russell King - ARM Linux
2017-01-12 22:49                               ` Kwok, WingMan

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=20170109225641.GB22820@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=m-karicheri2@ti.com \
    --cc=netdev@vger.kernel.org \
    --cc=w-kwok2@ti.com \
    /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).