From: Raju Lakkaraju <Raju.Lakkaraju@microchip.com>
To: <netdev@vger.kernel.org>
Cc: <davem@davemloft.net>, <kuba@kernel.org>,
<linux-kernel@vger.kernel.org>, <bryan.whitehead@microchip.com>,
<andrew@lunn.ch>, <linux@armlinux.org.uk>,
<UNGLinuxDriver@microchip.com>
Subject: [PATCH net-next 0/7] Add support to PHYLINK and SFP for PCI11x1x chips
Date: Fri, 21 Jul 2023 11:30:12 +0530 [thread overview]
Message-ID: <20230721060019.2737-1-Raju.Lakkaraju@microchip.com> (raw)
This patch series adds support to PHYLINK and SFP pluggable module.
Add software-nodes to hold the network interface phylink, sfp, i2c and GPIO
configuration and integrates the PCI1x1x chip I2C driver and GPIO driver to
access the SFP module EEPROM data.
Tested on chip PCI11010 Rev-B with Bridgeport Evaluation board Rev-1 with
following SFP modules:
1. FS's 2.5G SFP (SFP-2.5G-T) with 2.5 Gbps speed (interface 2500Base-X)
2. FS's DAC10G SFP (SFPP-PC01) with 2.5 Gbps speed (interface 2500Base-X)
3. FS's 1G SFP (SFP-GB-GE-TL) with 1G/100M/10M bps speed (interface SGMII)
4. Axcen's 1G SFP (AXGT-R1T4-05I1) with 1G/100M/10M bps speed (interface SGMII)
5. Excom's 1G SFP (SFP-T) with 1G/100M/10M bps speed (interface SGMII)
Raju Lakkaraju (7):
net: lan743x: Create separate PCS power reset function
net: lan743x: Create separate Link Speed Duplex state function
net: lan743x: Add SFP support check flag
net: lan743x: Add support to software-nodes for SFP and PHYLINK
net: lan743x: Add support to the Phylink framework
net: lan743x: Add support to ethtool phylink get and set settings
net: lan743x: Register the platform device for sfp pluggable module
drivers/net/ethernet/microchip/Kconfig | 4 +-
.../net/ethernet/microchip/lan743x_ethtool.c | 34 +-
drivers/net/ethernet/microchip/lan743x_main.c | 707 ++++++++++++++++--
drivers/net/ethernet/microchip/lan743x_main.h | 42 ++
4 files changed, 718 insertions(+), 69 deletions(-)
--
2.25.1
next reply other threads:[~2023-07-21 6:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 6:00 Raju Lakkaraju [this message]
2023-07-21 6:00 ` [PATCH net-next 1/7] net: lan743x: Create separate PCS power reset function Raju Lakkaraju
2023-07-22 20:24 ` Simon Horman
2023-07-21 6:00 ` [PATCH net-next 2/7] net: lan743x: Create separate Link Speed Duplex state function Raju Lakkaraju
2023-07-21 6:00 ` [PATCH net-next 3/7] net: lan743x: Add SFP support check flag Raju Lakkaraju
2023-07-21 6:00 ` [PATCH net-next 4/7] net: lan743x: Add support to software-nodes for SFP and PHYLINK Raju Lakkaraju
2023-07-21 6:00 ` [PATCH net-next 5/7] net: lan743x: Add support to the Phylink framework Raju Lakkaraju
2023-07-21 8:49 ` Russell King (Oracle)
2023-07-21 11:57 ` Russell King (Oracle)
2023-07-24 8:24 ` Raju Lakkaraju
2023-08-01 14:36 ` Russell King (Oracle)
2023-07-22 20:27 ` Simon Horman
2023-07-21 6:00 ` [PATCH net-next 6/7] net: lan743x: Add support to ethtool phylink get and set settings Raju Lakkaraju
2023-07-21 8:53 ` Russell King (Oracle)
2023-07-21 6:00 ` [PATCH net-next 7/7] net: lan743x: Register the platform device for sfp pluggable module Raju Lakkaraju
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=20230721060019.2737-1-Raju.Lakkaraju@microchip.com \
--to=raju.lakkaraju@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=bryan.whitehead@microchip.com \
--cc=davem@davemloft.net \
--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
Powered by JetHome