From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: javen <javen_xu@realsil.com.cn>,
hkallweit1@gmail.com, nic_swsd@realtek.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
daniel@makrotopia.org, linux@armlinux.org.uk,
enelsonmoore@gmail.com, daniel@thingy.jp
Subject: Re: [PATCH net-next v5 3/8] r8169: add support for phylink
Date: Tue, 7 Jul 2026 13:37:23 +0200 [thread overview]
Message-ID: <96409687-5752-4ff9-b4ab-2c9ca54d6b15@bootlin.com> (raw)
In-Reply-To: <20260707091637.371-4-javen_xu@realsil.com.cn>
On 7/7/26 11:16, javen wrote:
> From: Javen Xu <javen_xu@realsil.com.cn>
>
> Transfer old framework to phylink. Phylink can support fiber mode card
> which can not get link status or link speed from standard phy registers.
>
> Signed-off-by: Javen Xu <javen_xu@realsil.com.cn>
> ---
> Changes in v2:
> - merge patch v1 3/6 and v1 4/6.
> - add helper rtl_mac_enable_tx_lpi(), rtl_mac_disable_tx_lpi()
> and rtl8169_get_lpi_caps()
>
> Changes in v3:
> - use phylink_ethtool_set_pauseparam to set pause status when change
> mtu
> - replace phy_do_ioctl_running with rtl8169_ioctl
> - recover phy_mode according to tp->supports_gmii for 1G nics
>
> Changes in v4:
> - set lpi_interface if support eee
> - Only if jumbo changes, set pause
>
> Changes in v5:
> - no changes
> ---
> drivers/net/ethernet/realtek/Kconfig | 1 +
> drivers/net/ethernet/realtek/r8169_main.c | 279 ++++++++++++++++------
> 2 files changed, 206 insertions(+), 74 deletions(-)
>
> diff --git a/drivers/net/ethernet/realtek/Kconfig b/drivers/net/ethernet/realtek/Kconfig
> index 9b0f4f9631db..49ac72734225 100644
> --- a/drivers/net/ethernet/realtek/Kconfig
> +++ b/drivers/net/ethernet/realtek/Kconfig
> @@ -88,6 +88,7 @@ config R8169
> select CRC32
> select PHYLIB
PHYLINK selects PHYLIB, you can therefore drop this.
Besides this and potential reworks for the pause, this patch looks
pretty good :)
Maxime
next prev parent reply other threads:[~2026-07-07 11:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 9:16 [PATCH net-next v5 0/8] r8169: add support for phylink javen
2026-07-07 9:16 ` [PATCH net-next v5 1/8] r8169: add speed in private struct javen
2026-07-07 9:16 ` [PATCH net-next v5 2/8] net: phy: phylink: add helper to modify pause javen
2026-07-07 11:10 ` Maxime Chevallier
2026-07-07 9:16 ` [PATCH net-next v5 3/8] r8169: add support for phylink javen
2026-07-07 11:37 ` Maxime Chevallier [this message]
2026-07-07 9:16 ` [PATCH net-next v5 4/8] r8169: add support for RTL8116af javen
2026-07-07 9:16 ` [PATCH net-next v5 5/8] r8169: add ltr support for RTL8117 series javen
2026-07-07 9:16 ` [PATCH net-next v5 6/8] r8169: fix RTL8116af can not enter s0idle and c10 javen
2026-07-07 9:16 ` [PATCH net-next v5 7/8] r8169: add phylink support for RTL8127atf javen
2026-07-07 9:16 ` [PATCH net-next v5 8/8] r8169: add 1g " javen
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=96409687-5752-4ff9-b4ab-2c9ca54d6b15@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=andrew+netdev@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=daniel@thingy.jp \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=enelsonmoore@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=javen_xu@realsil.com.cn \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--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