From: Paolo Abeni <pabeni@redhat.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
Hayes Wang <hayeswang@realtek.com>,
Heiner Kallweit <hkallweit1@gmail.com>
Cc: Chih Kai Hsu <hsu.chih.kai@realtek.com>,
Birger Koblitz <mail@birger-koblitz.de>,
netdev@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: r8152: RTL8153 never runtime suspends with link up on a network with broadcast traffic
Date: Tue, 17 Nov 2026 13:16:33 +0100 [thread overview]
Message-ID: <9fec496b-a01e-4701-8c4b-0f78fef2ab48@redhat.com> (raw)
In-Reply-To: <fba64030-4f1e-4158-ae39-bc072bc5751d@molgen.mpg.de>
Adding Heiner,
On 11/11/26 01:52, Paul Menzel wrote:
> 2. If the hardware cannot do it, would you accept a per-device switch for the behaviour of the experiment, off by default? A module parameter is surely the wrong interface. A private flag (ethtool --set-priv-flags) would need no new uAPI, and userspace that knows the network configuration (systemd-udevd .link files, NetworkManager) could set it. Or do you see a generic interface for a "runtime wake filter", as other drivers that runtime suspend with the link up would have the same problem?
This is borderline, but I think a a private flag could be the better option
> 3. Is losing the first frame that wakes the device expected, or should it be delivered after the resume?
AFAICT loosing such frames is acceptable.
Other questions are for realtek guys,
prev parent reply other threads:[~2026-11-17 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 0:52 r8152: RTL8153 never runtime suspends with link up on a network with broadcast traffic Paul Menzel
2026-11-17 12:02 ` Paolo Abeni
2026-11-17 12:16 ` Paolo Abeni [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=9fec496b-a01e-4701-8c4b-0f78fef2ab48@redhat.com \
--to=pabeni@redhat.com \
--cc=hayeswang@realtek.com \
--cc=hkallweit1@gmail.com \
--cc=hsu.chih.kai@realtek.com \
--cc=linux-usb@vger.kernel.org \
--cc=mail@birger-koblitz.de \
--cc=netdev@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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