netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Linton <jeremy.linton@arm.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	netdev@vger.kernel.org
Cc: steve.glendinning@shawell.net
Subject: Re: [PATCH] net: smsc911x: If PHY doesn't have an interrupt then POLL
Date: Tue, 14 Jun 2016 15:59:11 -0500	[thread overview]
Message-ID: <5760701F.6000204@arm.com> (raw)
In-Reply-To: <46b56679-e92a-a8f9-f290-f67495169bdc@cogentembedded.com>

On 06/14/2016 03:44 PM, Sergei Shtylyov wrote:
> On 06/14/2016 07:16 PM, Jeremy Linton wrote:
>
>> If the interrupt configuration isn't set and we are using the
>
>     It's never set, judging by the driver code.
>
>> internal phy, then we need to poll the phy to reliably detect
>> phy state changes.
>
>     What address your internal PHY is at? Mine is at 1, and things seem
> to work reliably after probing:
>
> SMSC LAN8700 18000000.etherne:01: attached PHY driver [SMSC LAN8700]
> (mii_bus:phy_addr=18000000.etherne:01, irq=-1)

	Looks like your phy ends up polling (-1==IRQ_POLL)...

>
>     I'm using the device tree on my board.

	This was DT as well with a recent fedora/NetworkManager. It actually 
seems to be timing related to how fast the device gets configured after 
the initial phy probe. There is something like a 1 second window or so 
where it will work, but if network manager takes longer than that, the 
link state drops and cannot be brought back up unless the cable is 
pulled, replugged while the netdevice is being restarted.

  reply	other threads:[~2016-06-14 20:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14 16:16 [PATCH] net: smsc911x: If PHY doesn't have an interrupt then POLL Jeremy Linton
2016-06-14 18:30 ` Sergei Shtylyov
2016-06-14 19:27   ` Sergei Shtylyov
2016-06-14 19:49     ` Sergei Shtylyov
2016-06-14 20:12       ` Andrew Lunn
2016-06-14 20:21         ` Sergei Shtylyov
2016-06-14 20:13       ` Jeremy Linton
2016-06-14 18:42 ` Andrew Lunn
2016-06-14 20:48   ` Jeremy Linton
2016-06-14 20:44 ` Sergei Shtylyov
2016-06-14 20:59   ` Jeremy Linton [this message]
2016-06-14 21:24     ` Sergei Shtylyov
2016-06-14 22:26     ` Andrew Lunn
2016-06-15 15:50       ` Jeremy Linton
2016-06-14 21:02   ` Jeremy Linton
2016-06-14 21:12   ` Jeremy Linton
2016-06-14 21:26     ` Sergei Shtylyov
2016-06-14 21:29   ` Jeremy Linton
2016-06-14 21:34     ` Sergei Shtylyov
2016-06-14 21:40       ` Jeremy Linton
2016-06-14 21:42         ` Sergei Shtylyov
2016-06-14 21:53           ` Jeremy Linton
2016-06-14 21:56             ` Sergei Shtylyov
2016-06-15 15:56               ` Jeremy Linton

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=5760701F.6000204@arm.com \
    --to=jeremy.linton@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=steve.glendinning@shawell.net \
    /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).