From: Bart Van Assche <bvanassche@acm.org>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
Ricky WU <ricky_wu@realtek.com>,
Matthew Schwartz <matthew.schwartz@linux.dev>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
linux-block <linux-block@vger.kernel.org>
Subject: Re: [BUG] - Short freezes in gameplay due to MMC_CAP_AGGRESSIVE_PM on RTS525A card reader
Date: Wed, 28 Jan 2026 09:14:36 -0800 [thread overview]
Message-ID: <0b6fd99b-54a6-45f1-942e-94f707f2fbf5@acm.org> (raw)
In-Reply-To: <CAPDyKFoC-dwzcsABNy9pA=GGirBWwcxQhNMeTSSStXHtXmWbcg@mail.gmail.com>
On 1/28/26 5:23 AM, Ulf Hansson wrote:
> How does other block device drivers do this?
The role of the Linux kernel is to provide mechanisms while remaining as
policy-neutral as possible. In other words, it is up to user space to
decide whether to enable or to disable runtime PM.
For UFS devices some form of runtime PM is enabled by default for
battery-powered devices because otherwise the impact on battery life
would be unacceptable. If the latency impact of runtime resume is not
acceptable for some applications then it is up to user space software to
tune runtime power management as necessary.
Additionally, cpu_latency_qos_update_request() is called by the UFS
driver during runtime suspend and resume to prevent that CPU frequency
scaling negatively affects UFS processing latency. I'd like to move
these cpu_latency_qos_update_request() calls from the UFS driver into
the block layer core because I think that every block driver that
supports runtime power management needs this.
Bart.
next prev parent reply other threads:[~2026-01-28 17:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 21:01 Matthew Schwartz
2026-01-03 11:37 ` Ulf Hansson
2026-01-03 19:52 ` Matthew Schwartz
2026-01-04 0:45 ` Matthew Schwartz
2026-01-05 3:58 ` Ricky WU
2026-01-05 4:53 ` Matthew Schwartz
2026-01-05 7:02 ` Ricky WU
2026-01-05 7:50 ` Matthew Schwartz
2026-01-05 8:39 ` Ricky WU
2026-01-28 13:23 ` Ulf Hansson
2026-01-28 17:14 ` Bart Van Assche [this message]
2026-01-29 16:30 ` Ulf Hansson
2026-02-02 22:47 ` Bart Van Assche
2026-02-03 11:28 ` Ulf Hansson
2026-02-03 18:10 ` Bart Van Assche
2026-02-05 11:26 ` Ulf Hansson
2026-02-05 14:21 ` Bart Van Assche
2026-02-05 14:55 ` Ulf Hansson
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=0b6fd99b-54a6-45f1-942e-94f707f2fbf5@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=matthew.schwartz@linux.dev \
--cc=ricky_wu@realtek.com \
--cc=ulf.hansson@linaro.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
all inboxes | Powered by JetHome®