From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Javen <javen_xu@realsil.com.cn>, Andrew Lunn <andrew@lunn.ch>
Cc: "hkallweit1@gmail.com" <hkallweit1@gmail.com>,
"nic_swsd@realtek.com" <nic_swsd@realtek.com>,
"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"horms@kernel.org" <horms@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v1 1/5] net: phy: realtek: add support for dummy phy
Date: Fri, 5 Jun 2026 12:50:10 +0200 [thread overview]
Message-ID: <f90bad35-72b8-4f03-aea3-54387dd376a0@bootlin.com> (raw)
In-Reply-To: <b98e02778a6742a1a831ef57c3da2070@realsil.com.cn>
Hi,
On 6/5/26 11:43, Javen wrote:
>
> Hi,
>
>>> You are exactly right. The PHY doesn't actually exist; what we have is
>>> an internal PCS.
>>
>> ...
>>
>>> I actually tried to migrate it to
>>> phylink before. However, the current driver codebase is deeply coupled
>>> with tp->phydev in many places. Decoupling it may introduce bugs for
>>> numerous existing devices. Therefore, I want to try to expose the
>>> internal PCS as a dummy PHY device.
>>
>> Architecturally, you are going down a dead end. You really should be using
>> phylink.
>>
>> I don't see anything too scary with tp->phydev in the driver. Are there parts
>> you think are going to be a problem with phylink?
>>
>> Andrew
>
> Thanks for your suggestion.
>
> Since I am not very familiar with phylink, so I may have been too conservative about the migration. I have prepared a version using phylink and will submit it for review.
>
> Any comments or suggestions would be very helpful.
We can help reviewing this, indeed :)
You should be able to follow the porting guide here :
https://docs.kernel.org/networking/sfp-phylink.html
It was updated not too long ago :)
Maxime
>
> Thanks,
> BRs,
> Javen
next prev parent reply other threads:[~2026-06-05 10:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 6:59 [PATCH net-next v1 0/5] r8169: fix RTL8116AF low power and link readiness issues javen
2026-06-03 6:59 ` [PATCH net-next v1 1/5] net: phy: realtek: add support for dummy phy javen
2026-06-03 7:38 ` Maxime Chevallier
2026-06-03 8:00 ` Javen
2026-06-03 8:52 ` Maxime Chevallier
2026-06-03 9:13 ` Javen
2026-06-03 9:48 ` Maxime Chevallier
2026-06-03 10:03 ` Javen
2026-06-03 13:15 ` Andrew Lunn
2026-06-05 9:43 ` Javen
2026-06-05 10:50 ` Maxime Chevallier [this message]
2026-06-03 6:59 ` [PATCH net-next v1 2/5] r8169: move funcitons forward javen
2026-06-03 6:59 ` [PATCH net-next v1 3/5] r8169: fix RTL8116af link readiness bug javen
2026-06-03 6:59 ` [PATCH net-next v1 4/5] r8169: add ltr support for RTL8116af javen
2026-06-03 6:59 ` [PATCH net-next v1 5/5] r8169: fix RTL8116af can not enter s0idle and c10 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=f90bad35-72b8-4f03-aea3-54387dd376a0@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.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=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