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 v1 0/2] Add 100 base-x mode
Date: Mon, 11 Jan 2021 14:06:55 +0100 [thread overview]
Message-ID: <20210111130657.10703-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
Cisco GLC-FE-100LX
HP SFP 100FX J9054C
Excom SFP-SX-M1002
Bjarni Jonasson (2):
net: phy: Add 100 base-x mode
sfp: add support for 100 base-x SFPs
drivers/net/phy/sfp-bus.c | 9 +++++++++
include/linux/phy.h | 4 ++++
2 files changed, 13 insertions(+)
--
2.17.1
next reply other threads:[~2021-01-11 13:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 13:06 Bjarni Jonasson [this message]
2021-01-11 13:06 ` [PATCH v1 1/2] net: phy: Add 100 base-x mode Bjarni Jonasson
2021-01-11 14:19 ` Russell King - ARM Linux admin
2021-01-11 14:26 ` Andrew Lunn
2021-01-11 16:47 ` Russell King - ARM Linux admin
2021-01-12 15:32 ` Bjarni Jonasson
2021-01-11 19:37 ` Michał Mirosław
2021-01-12 15:34 ` Bjarni Jonasson
2021-01-11 13:06 ` [PATCH v1 2/2] sfp: add support for 100 base-x SFPs Bjarni Jonasson
2021-01-11 14:22 ` Russell King - ARM Linux admin
2021-01-12 15:31 ` Bjarni Jonasson
2021-01-12 15:39 ` Andrew Lunn
2021-01-11 14:18 ` [PATCH v1 0/2] Add 100 base-x mode Russell King - ARM Linux admin
2021-01-12 14:33 ` Bjarni Jonasson
2021-01-12 16:05 ` Russell King - ARM Linux admin
2021-01-13 9:45 ` Bjarni Jonasson
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=20210111130657.10703-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 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).