From: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
To: Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: phy: turn carrier off on phy attach
Date: Thu, 14 Jan 2016 21:22:57 +0100 [thread overview]
Message-ID: <1452802977.30596.46.camel@collabora.co.uk> (raw)
In-Reply-To: <10DF45FB-A812-4D6F-8B45-817B86FD48CE@gmail.com>
On Tue, 2016-01-12 at 17:31 -0800, Florian Fainelli wrote:
> On January 9, 2016 10:44:05 AM PST, Sjoerd Simons <sjoerd.simons@coll
> abora.co.uk> wrote:
> > The operstate of a networking device initially IF_OPER_UNKNOWN aka
> > "unknown", updated on carrier state changes (with carrier state
> > being
> > on
> > by default). This means it will stay unknown unless the carrier
> > state
> > goes to off at some point, which is not the case if the phy is
> > already
> > up/connected at startup.
>
> Correct, drivers typically call netif_carrier_off prior to
> registering the network device to give a predictable link state,
> regardless of whether or not they use PHYLIB.
>
> >
> > Explicitly turn off the carrier on phy attach, leaving the phy
> > state
> > machine to turn the carrier on when it has done the initial
> > negotiation.
>
> Same comment as Andrew on the comment below.
>
> Out of curiosity, was there a particular driver you ran into issues
> with?
Prepping a v2. This came up on Rada Rock2 board, so the (Rockchip)
DWMAC driver combined with a realtek phy (RTL8211E). Thanks for the
review
--
Sjoerd Simons
Collabora Ltd.
next prev parent reply other threads:[~2016-01-14 20:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 18:44 [PATCH] net: phy: turn carrier off on phy attach Sjoerd Simons
2016-01-11 22:17 ` David Miller
2016-01-12 0:57 ` Andrew Lunn
2016-01-13 1:31 ` Florian Fainelli
2016-01-14 20:22 ` Sjoerd Simons [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-01-14 20:57 Sjoerd Simons
2016-01-15 19:50 ` David Miller
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=1452802977.30596.46.camel@collabora.co.uk \
--to=sjoerd.simons@collabora.co.uk \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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.