From: Arun Ramadoss <arun.ramadoss@microchip.com>
To: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Jakub Kicinski <kuba@kernel.org>,
"David S . Miller" <davem@davemloft.net>
Subject: [RFC PATCH net-next 0/4] Add support for LAN937x T1 Phy
Date: Mon, 28 Feb 2022 19:35:06 +0530 [thread overview]
Message-ID: <20220228140510.20883-1-arun.ramadoss@microchip.com> (raw)
LAN937x is a Multi-port 100Base-T1 Switch and it internally uses LAN87xx
T1 Phy. This series of patch update the intialization routine for the
LAN87xx phy and also add LAN937x part support. Added the T1 Phy
master-slave configuration through ethtool.
Arun Ramadoss (4):
net: phy: used the genphy_soft_reset for phy reset in Lan87xx
net: phy: updated the initialization routine for LAN87xx
net: phy: added the LAN937x phy support
net: phy: added master-slave config and cable diagnostics for Lan937x
drivers/net/phy/microchip_t1.c | 373 +++++++++++++++++++++++++++------
1 file changed, 308 insertions(+), 65 deletions(-)
--
2.33.0
next reply other threads:[~2022-02-28 14:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 14:05 Arun Ramadoss [this message]
2022-02-28 14:05 ` [RFC PATCH net-next 1/4] net: phy: used the genphy_soft_reset for phy reset in Lan87xx Arun Ramadoss
2022-03-02 3:19 ` Andrew Lunn
2022-03-02 10:04 ` Arun.Ramadoss
2022-02-28 14:05 ` [RFC PATCH net-next 2/4] net: phy: updated the initialization routine for LAN87xx Arun Ramadoss
2022-02-28 14:05 ` [RFC PATCH net-next 3/4] net: phy: added the LAN937x phy support Arun Ramadoss
2022-03-02 3:22 ` Andrew Lunn
2022-03-02 9:57 ` Arun.Ramadoss
2022-02-28 14:05 ` [RFC PATCH net-next 4/4] net: phy: added master-slave config and cable diagnostics for Lan937x Arun Ramadoss
2022-02-28 14:12 ` Russell King (Oracle)
2022-03-01 16:59 ` Arun.Ramadoss
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=20220228140510.20883-1-arun.ramadoss@microchip.com \
--to=arun.ramadoss@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).