From: Bjarni Jonasson <bjarni.jonasson@microchip.com>
To: Russell King <linux@armlinux.org.uk>,
Andrew Lunn <andrew@lunn.ch>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: Bjarni Jonasson <bjarni.jonasson@microchip.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
UNGLinuxDriver <UNGLinuxDriver@microchip.com>
Subject: [PATCH net-next v2 0/2] Add 100 base-x mode
Date: Wed, 13 Jan 2021 12:56:24 +0100 [thread overview]
Message-ID: <20210113115626.17381-1-bjarni.jonasson@microchip.com> (raw)
Adding support for 100 base-x in phylink.
The Sparx5 switch supports 100 base-x pcs (IEEE 802.3 Clause 24) 4b5b encoded.
These patches adds phylink support for that mode.
Tested in Sparx5, using sfp modules:
Axcen 100fx AXFE-1314-0521 (base-fx)
Axcen 100lx AXFE-1314-0551 (base-lx)
HP SFP 100FX J9054C (bx-10)
Excom SFP-SX-M1002 (base-lx)
v1 -> v2:
Added description to Documentation/networking/phy.rst
Moved PHY_INTERFACE_MODE_100BASEX to above 1000BASEX
Patching against net-next
Bjarni Jonasson (2):
net: phy: Add 100 base-x mode
sfp: add support for 100 base-x SFPs
Documentation/networking/phy.rst | 5 +++++
drivers/net/phy/sfp-bus.c | 9 +++++++++
include/linux/phy.h | 4 ++++
3 files changed, 18 insertions(+)
--
2.17.1
next reply other threads:[~2021-01-13 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 11:56 Bjarni Jonasson [this message]
2021-01-13 11:56 ` [PATCH net-next v2 1/2] net: phy: Add 100 base-x mode Bjarni Jonasson
2021-01-14 15:13 ` Russell King - ARM Linux admin
2021-01-13 11:56 ` [PATCH net-next v2 2/2] sfp: add support for 100 base-x SFPs Bjarni Jonasson
2021-01-14 15:14 ` Russell King - ARM Linux admin
2021-01-15 0:10 ` [PATCH net-next v2 0/2] Add 100 base-x mode patchwork-bot+netdevbpf
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=20210113115626.17381-1-bjarni.jonasson@microchip.com \
--to=bjarni.jonasson@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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.