From: Heiner Kallweit <hkallweit1@gmail.com>
To: javen <javen_xu@realsil.com.cn>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
horms@kernel.org, kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, nic_swsd@realtek.com, pabeni@redhat.com
Subject: Re: [PATCH net-next v1 0/3] r816e: Add r816e driver in Realtek
Date: Wed, 28 Jan 2026 20:08:12 +0100 [thread overview]
Message-ID: <4a13d635-7a22-4de6-a4bb-1ae4351b114c@gmail.com> (raw)
In-Reply-To: <20260128065309.556-1-javen_xu@realsil.com.cn>
On 1/28/2026 7:53 AM, javen wrote:
>> On 1/27/2026 12:34 PM, javen wrote:
>
>>> From: Javen Xu <javen_xu@realsil.com.cn>
>
>>>
>
>>> This series patch add a fake driver r816e to ensure the kernel could
>
>>> set the correct power state for #fun through r816e driver when suspending.
>
>>>
>
>>
>
>> I think a better approach would be to contribute to adding phylink/sfp support
>
>> to r8169, so that the SFP NIC versions (incl. RTL8116AF) can be properly
>
>> supported. This would have to include making the SFP I2C bus accessible by
>
>> the kernel (instead of firmware only).
>
>>
>
>
>
> RTL8116af is a multi-function device. fun0 is a BMC virtual driver and fun1 is
>
> the nic driver. The BMC virtual driver(fun0) is used for power management,
>
> while fun1 provides the actual network functionality.
>
>
If only purpose of this dummy driver is to bring the device to D3hot during system
suspend, then this may be a question to the PCI subsystem maintainer(s).
PCI devices are instantiated by the PCI core, just that in case of the device here
no driver gets attached. Still PCI core applies a default suspend handling to each
device.
prev parent reply other threads:[~2026-01-28 19:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 11:34 [PATCH net-next v1 0/3] r816e: Add r816e driver in Realtek javen
2026-01-27 11:34 ` [PATCH net-next v1 1/3] r816e: add a fake driver r816e for RTL8116af javen
2026-01-27 17:10 ` kernel test robot
2026-01-27 11:34 ` [PATCH net-next v1 2/3] r816e: Add a Makefile in the r816e folder javen
2026-01-27 11:34 ` [PATCH net-next v1 3/3] realtek: Update Makefile and Kconfig javen
2026-01-27 22:33 ` kernel test robot
2026-01-27 22:33 ` kernel test robot
2026-01-27 20:58 ` [PATCH net-next v1 0/3] r816e: Add r816e driver in Realtek Heiner Kallweit
2026-01-28 6:53 ` javen
2026-01-28 13:04 ` Andrew Lunn
2026-01-28 19:08 ` Heiner Kallweit [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=4a13d635-7a22-4de6-a4bb-1ae4351b114c@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.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