From: Divya Koppera <Divya.Koppera@microchip.com>
To: <arun.ramadoss@microchip.com>, <UNGLinuxDriver@microchip.com>,
<andrew@lunn.ch>, <hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH net-next v3 0/2] Adds support for lan887x phy
Date: Wed, 21 Aug 2024 11:29:04 +0530 [thread overview]
Message-ID: <20240821055906.27717-1-Divya.Koppera@microchip.com> (raw)
From: Divya Koppera <divya.koppera@microchip.com>
Adds support for lan887x phy and accept autoneg configuration in
phy driver only when feature is enabled in supported list.
v2 -> v3
https://lore.kernel.org/lkml/20240813181515.863208-1-divya.koppera@microchip.com
Removed extra braces for linkmode_test_bit in phy library.
v1 -> v2
https://lore.kernel.org/lkml/20240808145916.26006-1-Divya.Koppera@microchip.com
Addresed below review comments
- Added phy library support to check supported list when autoneg is
enabled.
- Removed autoneg enabled check in lan887x phy.
- Removed of_mdio macro for LED initialization.
- Removed clearing pause frames support from supported list.
Divya Koppera (2):
net: phy: Add phy library support to check supported list when autoneg
is enabled
net: phy: microchip_t1: Adds support for lan887x phy
drivers/net/phy/microchip_t1.c | 577 ++++++++++++++++++++++++++++++++-
drivers/net/phy/phy.c | 5 +-
2 files changed, 580 insertions(+), 2 deletions(-)
--
2.17.1
next reply other threads:[~2024-08-21 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 5:59 Divya Koppera [this message]
2024-08-21 5:59 ` [PATCH net-next v3 1/2] net: phy: Add phy library support to check supported list when autoneg is enabled Divya Koppera
2024-08-26 1:39 ` Andrew Lunn
2024-08-21 5:59 ` [PATCH net-next v3 2/2] net: phy: microchip_t1: Adds support for lan887x phy Divya Koppera
2024-08-26 16:30 ` [PATCH net-next v3 0/2] " 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=20240821055906.27717-1-Divya.Koppera@microchip.com \
--to=divya.koppera@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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.