From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpufreq: flush any pending policy update work scheduled before freeing
Date: Fri, 18 Oct 2019 13:33:38 +0530 [thread overview]
Message-ID: <20191018080338.vbgnrt3i6epkrx3u@vireshk-i7> (raw)
In-Reply-To: <CAJZ5v0h0vY9OBYg-_pR-hu_TJkE0odf5Nnd8qnJc17+8NQo=7w@mail.gmail.com>
On 18-10-19, 09:32, Rafael J. Wysocki wrote:
> Well, the policy is going away, so the governor has been stopped for
> it already. Even if the limit is updated, it will not be used anyway,
> so why bother with updating it?
The hardware will be programmed to run on that frequency before the
policy exits, so I will say it will be used and the constraint will be
satisfied. And so I had that view.
--
viresh
next prev parent reply other threads:[~2019-10-18 8:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 16:35 Sudeep Holla
2019-10-17 19:36 ` Rafael J. Wysocki
2019-10-17 21:26 ` Rafael J. Wysocki
2019-10-18 5:55 ` Sudeep Holla
2019-10-18 6:02 ` Viresh Kumar
2019-10-18 7:32 ` Rafael J. Wysocki
2019-10-18 8:03 ` Viresh Kumar [this message]
2019-10-18 8:19 ` Rafael J. Wysocki
2019-10-18 8:25 ` Viresh Kumar
2019-10-18 10:19 ` Sudeep Holla
2019-10-18 10:37 ` Rafael J. Wysocki
2019-10-18 11:06 ` Sudeep Holla
2019-10-21 0:14 ` Rafael J. Wysocki
2019-10-21 10:33 ` Sudeep Holla
2019-10-21 2:15 ` Viresh Kumar
2019-10-21 8:20 ` Rafael J. Wysocki
2019-10-21 10:27 ` Sudeep Holla
2019-10-21 10:55 ` Viresh Kumar
2019-10-18 5:47 ` Sudeep Holla
2019-10-18 5:38 ` Viresh Kumar
2019-10-18 7:53 ` 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=20191018080338.vbgnrt3i6epkrx3u@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.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
all inboxes | Powered by JetHome®