From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: netdev@vger.kernel.org, sean.wang@mediatek.com, john@phrozen.org,
kernel@pengutronix.de, privat@egil-hjelmeland.no,
Woojung.Huh@microchip.com, vivien.didelot@savoirfairelinux.com,
andrew@lunn.ch
Subject: Re: [RFT/RFC net-next 0/2] net: dsa: Plug in PHYLINK support
Date: Fri, 15 Dec 2017 12:08:31 +0000 [thread overview]
Message-ID: <20171215120831.GS10595@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20171215002850.27862-1-f.fainelli@gmail.com>
On Thu, Dec 14, 2017 at 04:28:48PM -0800, Florian Fainelli wrote:
> Hi all,
>
> This patch series replaces the existing PHYLIB integration with PHYLINK which
> is a superior solution since we need to support a collection of fixed links,
> integrated PHYs, SFP, non-pluggable SFPs etc.
>
> I am expecting quite a lot of breakage, for a number of reasons:
>
> - PHYLINK does not create a PHY device for fixed links (MLO_AN_FIXED), which
> means that user-facing port (not DSA, not CPU) need to be explicitly handled
> with phylink_mac_ops now
>
> - only been able to test this on a limited number of platforms, and not the
> ZII devel B/C boards yet
>
> Please test and report!
The good news is that it almost works on the ZII Rev C with the SFF
modules, but there's a few issues that need solving:
1. s/WARN_ON(!lockdep_rtnl_is_held())/ASSERT_RTNL()/ in phylink.c -
probably wouldn't have been noticed if it wasn't for the lockdep
splat with DSA's interrupt handling during boot that's been there
since -rc1. (Andrew mentioned that it's known, so I haven't
reported that.)
2. ports without a phy but with sfp cause the "no phy at" and
"failed to connect to port" message - I think we need a way for
DSA to know whether it should be attempting to attach a PHY.
3. We need mv88e6xxx to implement at least phylink_mac_link_state()
so that SFPs report sane ethtool information. It also needs to
implement phylink_mac_config() so that the link can be appropriately
configured to the module's capabilities, and phylink_validate() to
do the jiggery for choosing between 1000base-X vs 2500base-X mode
if the DSA switches can't automatically select the appropriate one.
With a few hacks for the above, I can get TX_DISABLE on the SFF2 module
to follow the interface up/down status, but as I say more work is needed
so that mv88e6xxx works with the phylink callbacks for the SFF modules
to be properly supported.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up
According to speedtest.net: 8.21Mbps down 510kbps up
next prev parent reply other threads:[~2017-12-15 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 0:28 [RFT/RFC net-next 0/2] net: dsa: Plug in PHYLINK support Florian Fainelli
2017-12-15 0:28 ` [RFT/RFC net-next 1/2] " Florian Fainelli
2017-12-15 0:28 ` [RFT/RFC net-next 2/2] net: dsa: bcm_sf2: Kick PHYLINK upon link interrupts Florian Fainelli
2017-12-15 12:08 ` Russell King - ARM Linux [this message]
2017-12-15 12:48 ` [RFT/RFC net-next 0/2] net: dsa: Plug in PHYLINK support Andrew Lunn
2017-12-15 15:51 ` Egil Hjelmeland
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=20171215120831.GS10595@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Woojung.Huh@microchip.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=john@phrozen.org \
--cc=kernel@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=privat@egil-hjelmeland.no \
--cc=sean.wang@mediatek.com \
--cc=vivien.didelot@savoirfairelinux.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).