All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mason <slash.tmp@free.fr>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev <netdev@vger.kernel.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	David Miller <davem@davemloft.net>
Subject: Re: Waiting for the PHY to complete auto-negotiation
Date: Wed, 6 Dec 2017 20:25:53 +0100	[thread overview]
Message-ID: <b94d080e-1bc4-9e6f-3907-25c782809cbd@free.fr> (raw)
In-Reply-To: <20171206190728.GC28774@lunn.ch>

On 06/12/2017 20:07, Andrew Lunn wrote:

> By chip, you mean the Ethernet controller? Not the whole SoC?

Doh! Yes. Let me rephrase.

When we detect link down, we put the ethernet HW block in reset,
and repeat initialization when the link comes back up.

Hmmm, however, at the moment, I only reset on an administrative
(user-requested) link down, i.e. through ndo_stop. I would probably
have to handle cable unplug/replug events as well.

Or just consider the quirk to make flow control too complicated
to implement correctly...

Regards.

  reply	other threads:[~2017-12-06 19:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06 16:39 Waiting for the PHY to complete auto-negotiation Mason
2017-12-06 16:59 ` Andrew Lunn
2017-12-06 18:03   ` Mason
2017-12-06 18:26     ` Andrew Lunn
2017-12-06 19:00       ` Mason
2017-12-06 19:07         ` Andrew Lunn
2017-12-06 19:25           ` Mason [this message]
2017-12-06 23:00             ` Florian Fainelli
2017-12-07 16:17               ` Mason
2017-12-09 18:49                 ` Florian Fainelli
2017-12-11 14:29                   ` Mason
2017-12-11 14:36                     ` Måns Rullgård
2017-12-11 14:47                       ` Mason
2017-12-11 16:32                         ` Måns Rullgård

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=b94d080e-1bc4-9e6f-3907-25c782809cbd@free.fr \
    --to=slash.tmp@free.fr \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=netdev@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.