public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Russell King - ARM Linux admin <linux@armlinux•org.uk>
To: Andrew Lunn <andrew@lunn•ch>,
	Florian Fainelli <f.fainelli@gmail•com>,
	Heiner Kallweit <hkallweit1@gmail•com>
Cc: "David S. Miller" <davem@davemloft•net>, netdev@vger•kernel.org
Subject: Re: [PATCH net-next 0/3] net: add phylink support for PCS
Date: Sat, 14 Mar 2020 10:31:38 +0000	[thread overview]
Message-ID: <20200314103137.GK25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200314102721.GG25745@shell.armlinux.org.uk>

Please ignore this series entirely.

On Sat, Mar 14, 2020 at 10:27:21AM +0000, Russell King - ARM Linux admin wrote:
> Depends on "net: mii clause 37 helpers".
> 
> This series adds support for IEEE 802.3 register set compliant PCS
> for phylink.  In order to do this, we:
> 
> 1. add accessors for modifying a MDIO device register, and use them in
>    phylib, rather than duplicating the code from phylib.
> 2. add support for decoding the advertisement from clause 22 compatible
>    register sets for clause 37 advertisements and SGMII advertisements.
> 3. add support for clause 45 register sets for 10GBASE-R PCS.
> 
> These have been tested on the LX2160A Clearfog-CX platform.
> 
> This is a re-post of the series previously sent, but with the first two
> patches separated out; the conclusion of the discussion with Vladimir
> seemed to be that there was no issue with the patches themselves.
> 
>  drivers/net/phy/mdio_bus.c |  55 +++++++++++
>  drivers/net/phy/phy-core.c |  31 ------
>  drivers/net/phy/phylink.c  | 236 +++++++++++++++++++++++++++++++++++++++++++++
>  include/linux/mdio.h       |   4 +
>  include/linux/phy.h        |  19 ++++
>  include/linux/phylink.h    |   8 ++
>  include/uapi/linux/mii.h   |   5 +
>  7 files changed, 327 insertions(+), 31 deletions(-)
> 
> -- 
> RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
> FTTC broadband for 0.8mile line in suburbia: sync at 10.2Mbps down 587kbps up

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 10.2Mbps down 587kbps up

      parent reply	other threads:[~2020-03-15  1:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-14 10:27 [PATCH net-next 0/3] net: add phylink support for PCS Russell King - ARM Linux admin
2020-03-14 10:28 ` [PATCH net-next 1/5] net: mdiobus: add APIs for modifying a MDIO device register Russell King
2020-03-14 10:28 ` [PATCH net-next 2/5] net: phylink: pcs: add 802.3 clause 22 helpers Russell King
2020-03-14 10:28 ` [PATCH net-next 3/5] net: phylink: pcs: add 802.3 clause 45 helpers Russell King
2020-03-14 10:28 ` [PATCH net-next 4/5] net: phylink: rename 'ops' to 'mac_ops' Russell King
2020-03-14 10:29   ` Russell King - ARM Linux admin
2020-03-14 10:28 ` [PATCH net-next 5/5] net: phylink: add separate pcs operations structure Russell King
2020-03-14 10:29 ` [PATCH REPOST2 net-next 0/3] net: add phylink support for PCS Russell King - ARM Linux admin
2020-03-14 10:31 ` Russell King - ARM Linux admin [this message]

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=20200314103137.GK25745@shell.armlinux.org.uk \
    --to=linux@armlinux$(echo .)org.uk \
    --cc=andrew@lunn$(echo .)ch \
    --cc=davem@davemloft$(echo .)net \
    --cc=f.fainelli@gmail$(echo .)com \
    --cc=hkallweit1@gmail$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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