From: Lukas Wunner <lukas@wunner.de>
To: javen <javen_xu@realsil.com.cn>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC Patch] pci: add power management for rtl8116af
Date: Fri, 22 May 2026 09:20:01 +0200 [thread overview]
Message-ID: <ahADoUizmRYB03D2@wunner.de> (raw)
In-Reply-To: <20260521033827.502-1-javen_xu@realsil.com.cn>
On Thu, May 21, 2026 at 11:38:27AM +0800, javen wrote:
> From: Javen Xu <javen_xu@realsil.com.cn>
>
> RTL8116af is a multi function card. But due to the hardware design, only
> function 0 and function 1(nic) are exposed to pci system. If the system
> want to enter s0idle or cpu need to enter c10 when suspend, function 2
> to 7 must be set to d3 and enable aspm. Function 5 and 6 are reserved,
> so we skip them.
[...]
> Just as the comments above, function 2 to 7 are hidden to pci system. So
> we have to set d3 and aspm through our private register, which is CSI. I
> have a discussion with netdev maintainer, and he thought this might be a
> question to pci system.
> I wonder whether this patch can be accepted here. Any feedback would be
> highly appreciated!
This is quite large for a quirk. Have you considered writing a small
driver instead to configure power state for the invisible/unused functions?
Or integrating the functionality into an existing driver?
Usually a quirk only makes sense if the system becomes unusable
or if a device falls off the bus without the quirk. It's not
suitable if the point is just to avoid unnecessarily high power
consumption.
Thanks,
Lukas
prev parent reply other threads:[~2026-05-22 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 3:38 [RFC Patch] pci: add power management for rtl8116af javen
2026-05-21 4:12 ` sashiko-bot
2026-05-21 16:09 ` Bjorn Helgaas
2026-05-22 6:34 ` Javen
2026-05-22 7:20 ` Lukas Wunner [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=ahADoUizmRYB03D2@wunner.de \
--to=lukas@wunner.de \
--cc=bhelgaas@google.com \
--cc=javen_xu@realsil.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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