From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: rafael@kernel.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
ulf.hansson@linaro.org
Subject: [PATCH RFC 3/3] cpuidle: Use the latency to call find_deepest_idle_state
Date: Wed, 13 Nov 2019 19:54:19 +0100 [thread overview]
Message-ID: <20191113185419.13305-3-daniel.lezcano@linaro.org> (raw)
In-Reply-To: <20191113185419.13305-1-daniel.lezcano@linaro.org>
As the dev->use_latency is filled with the latency value when this
function is called, use it as a parameter to the
find_deepest_idle_state() function.
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
---
drivers/cpuidle/cpuidle.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpuidle/cpuidle.c b/drivers/cpuidle/cpuidle.c
index f68a6c9e8482..659d8b1ece6d 100644
--- a/drivers/cpuidle/cpuidle.c
+++ b/drivers/cpuidle/cpuidle.c
@@ -124,7 +124,7 @@ void cpuidle_use_latency(unsigned int latency)
int cpuidle_find_deepest_state(struct cpuidle_driver *drv,
struct cpuidle_device *dev)
{
- return find_deepest_state(drv, dev, UINT_MAX, 0, false);
+ return find_deepest_state(drv, dev, dev->use_latency, 0, false);
}
#ifdef CONFIG_SUSPEND
--
2.17.1
next prev parent reply other threads:[~2019-11-13 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 18:54 [PATCH RFC 1/3] cpuidle: Replace use_deepest_state flag by use_latency Daniel Lezcano
2019-11-13 18:54 ` [PATCH RFC 2/3] sched: idle: Add a latency parameter to the play_idle function Daniel Lezcano
2019-11-13 22:08 ` Rafael J. Wysocki
2019-11-13 18:54 ` Daniel Lezcano [this message]
2019-11-13 22:19 ` [PATCH RFC 3/3] cpuidle: Use the latency to call find_deepest_idle_state Rafael J. Wysocki
2019-11-13 21:59 ` [PATCH RFC 1/3] cpuidle: Replace use_deepest_state flag by use_latency Rafael J. Wysocki
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=20191113185419.13305-3-daniel.lezcano@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).