From: Andrew Lunn <andrew@lunn.ch>
To: Divya Koppera <divya.koppera@microchip.com>
Cc: 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,
arun.ramadoss@microchip.com, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next v2 2/2] net: phy: microchip_t1: Adds support for lan887x phy
Date: Fri, 16 Aug 2024 22:56:16 +0200 [thread overview]
Message-ID: <4956ed49-89b4-46fc-a2e8-8debada5a35c@lunn.ch> (raw)
In-Reply-To: <20240813181515.863208-3-divya.koppera@microchip.com>
On Tue, Aug 13, 2024 at 11:45:15PM +0530, Divya Koppera wrote:
> The LAN887x is a Single-Port Ethernet Physical Layer Transceiver compliant
> with the IEEE 802.3bw (100BASE-T1) and IEEE 802.3bp (1000BASE-T1)
> specifications. The device provides 100/1000 Mbit/s transmit and receive
> capability over a single Unshielded Twisted Pair (UTP) cable. It supports
> communication with an Ethernet MAC via standard RGMII/SGMII interfaces.
>
> LAN887x supports following features,
> - Events/Interrupts
> - LED/GPIO Operation
> - IEEE 1588 (PTP)
> - SQI
> - Sleep and Wakeup (TC10)
> - Cable Diagnostics
>
> First patch only supports 100Mbps and 1000Mbps force-mode.
>
> Signed-off-by: Divya.Koppera <divya.koppera@microchip.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
prev parent reply other threads:[~2024-08-16 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 18:15 [PATCH net-next v2 0/2] " Divya Koppera
2024-08-13 18:15 ` [PATCH net-next v2 1/2] net: phy: Add phy library support to check supported list when autoneg is enabled Divya Koppera
2024-08-16 18:18 ` Jakub Kicinski
2024-08-13 18:15 ` [PATCH net-next v2 2/2] net: phy: microchip_t1: Adds support for lan887x phy Divya Koppera
2024-08-16 20:56 ` Andrew Lunn [this message]
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=4956ed49-89b4-46fc-a2e8-8debada5a35c@lunn.ch \
--to=andrew@lunn.ch \
--cc=UNGLinuxDriver@microchip.com \
--cc=arun.ramadoss@microchip.com \
--cc=davem@davemloft.net \
--cc=divya.koppera@microchip.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®