From: patchwork-bot+netdevbpf@kernel.org
To: Parthiban Veerasooran <Parthiban.Veerasooran@microchip.com>
Cc: piergiorgio.beruto@gmail.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,
parthiban.veerasooran@microchip.com
Subject: Re: [PATCH net-next v4 0/2] Add SQI and SQI+ support for OATC14 10Base-T1S PHYs and Microchip T1S driver
Date: Mon, 01 Dec 2025 23:10:29 +0000 [thread overview]
Message-ID: <176463062952.2589368.13509263665154937851.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251201032346.6699-1-parthiban.veerasooran@microchip.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 1 Dec 2025 08:53:44 +0530 you wrote:
> This patch series adds Signal Quality Indicator (SQI) and enhanced SQI+
> support for OATC14 10Base-T1S PHYs, along with integration into the
> Microchip T1S PHY driver. This enables ethtool to report the SQI value for
> OATC14 10Base-T1S PHYs.
>
> Patch Summary:
> 1. add SQI and SQI+ support for OATC14 10Base-T1S PHYs
> - Introduces MDIO register definitions for DCQ_SQI and DCQ_SQIPLUS.
> - Adds genphy_c45_oatc14_get_sqi_max() to report the maximum SQI/SQI+
> level.
> - Adds genphy_c45_oatc14_get_sqi() to return the current SQI or SQI+
> value.
> - Updates include/linux/phy.h to expose the new APIs.
> - SQI+ capability is read from the Advanced Diagnostic Features
> Capability register (ADFCAP). If unsupported, the driver falls back
> to basic SQI (0–7 levels).
> - If SQI+ capability is supported, the function returns the extended
> SQI+ value; otherwise, it returns the basic SQI value.
> - Open Alliance TC14 10BASE-T1S Advanced Diagnostic PHY Features.
> https://opensig.org/wp-content/uploads/2025/06/OPEN_Alliance_10BASE-T1S_Advanced_PHY_features_for-automotive_Ethernet_V2.1b.pdf
>
> [...]
Here is the summary with links:
- [net-next,v4,1/2] net: phy: phy-c45: add SQI and SQI+ support for OATC14 10Base-T1S PHYs
https://git.kernel.org/netdev/net-next/c/5e1bf5ae5e3b
- [net-next,v4,2/2] net: phy: microchip_t1s: add SQI support for LAN867x Rev.D0 PHYs
https://git.kernel.org/netdev/net-next/c/16416c835287
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-12-01 23:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 3:23 [PATCH net-next v4 0/2] Add SQI and SQI+ support for OATC14 10Base-T1S PHYs and Microchip T1S driver Parthiban Veerasooran
2025-12-01 3:23 ` [PATCH net-next v4 1/2] net: phy: phy-c45: add SQI and SQI+ support for OATC14 10Base-T1S PHYs Parthiban Veerasooran
2025-12-01 13:24 ` Andrew Lunn
2025-12-02 16:21 ` Simon Horman
2025-12-03 8:22 ` Parthiban.Veerasooran
2025-12-01 3:23 ` [PATCH net-next v4 2/2] net: phy: microchip_t1s: add SQI support for LAN867x Rev.D0 PHYs Parthiban Veerasooran
2025-12-01 13:25 ` Andrew Lunn
2025-12-01 23:10 ` patchwork-bot+netdevbpf [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=176463062952.2589368.13509263665154937851.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Parthiban.Veerasooran@microchip.com \
--cc=andrew@lunn.ch \
--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 \
--cc=piergiorgio.beruto@gmail.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