From: Viresh Kumar <viresh.kumar@linaro.org>
To: Vincent Donnefort <vincent.donnefort@arm.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Lukasz Luba <lukasz.luba@arm.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Quentin Perret <qperret@google.com>,
Linux PM <linux-pm@vger.kernel.org>,
Ionela Voinescu <ionela.voinescu@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>
Subject: Re: [PATCH v3 3/6] cpufreq: Add an interface to mark inefficient frequencies
Date: Tue, 6 Jul 2021 14:20:39 +0530 [thread overview]
Message-ID: <20210706085039.eb7wzc2dpnd2v6yo@vireshk-i7> (raw)
In-Reply-To: <20210706084312.GA219414@e120877-lin.cambridge.arm.com>
On 06-07-21, 09:43, Vincent Donnefort wrote:
> I was referring to how letting know a driver which registers ->target() that we
> want or not inefficient frequencies. My proposal was to rely on a
> cpufreq_policy's flag that the driver can read.
I am bit confused at this point, lets see how it looks eventually as patches :)
--
viresh
next prev parent reply other threads:[~2021-07-06 8:50 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 11:05 [PATCH v3 0/6] EM / PM: Inefficient OPPs Vincent Donnefort
2021-06-04 11:05 ` [PATCH v3 1/6] PM / EM: Fix inefficient states detection Vincent Donnefort
2021-06-04 18:09 ` Matthias Kaehlcke
2021-06-04 11:05 ` [PATCH v3 2/6] PM / EM: Mark inefficient states Vincent Donnefort
2021-06-04 18:12 ` Matthias Kaehlcke
2021-06-04 11:05 ` [PATCH v3 3/6] cpufreq: Add an interface to mark inefficient frequencies Vincent Donnefort
2021-06-04 18:19 ` Matthias Kaehlcke
2021-06-14 13:40 ` Vincent Donnefort
2021-06-07 5:02 ` Viresh Kumar
2021-06-07 10:14 ` Lukasz Luba
2021-06-14 7:28 ` Viresh Kumar
2021-06-14 13:35 ` Vincent Donnefort
2021-06-15 5:02 ` Viresh Kumar
2021-06-15 8:44 ` Vincent Donnefort
2021-06-15 10:17 ` Viresh Kumar
2021-06-15 17:15 ` Vincent Donnefort
2021-06-16 7:35 ` Viresh Kumar
2021-06-16 9:03 ` Lukasz Luba
2021-06-16 9:31 ` Viresh Kumar
2021-06-16 10:33 ` Lukasz Luba
2021-06-16 10:53 ` Viresh Kumar
2021-06-16 12:45 ` Lukasz Luba
2021-07-02 14:21 ` Lukasz Luba
2021-07-02 15:46 ` Rafael J. Wysocki
2021-07-02 16:04 ` Rafael J. Wysocki
2021-07-02 16:08 ` Lukasz Luba
2021-07-02 17:53 ` Rafael J. Wysocki
2021-07-02 19:04 ` Lukasz Luba
2021-07-02 19:17 ` Vincent Donnefort
2021-07-05 14:09 ` Rafael J. Wysocki
2021-07-06 8:12 ` Vincent Donnefort
2021-07-06 8:37 ` Viresh Kumar
2021-07-06 8:43 ` Vincent Donnefort
2021-07-06 8:50 ` Viresh Kumar [this message]
2021-07-06 12:11 ` Rafael J. Wysocki
2021-07-02 16:13 ` Vincent Donnefort
2021-07-02 17:38 ` Rafael J. Wysocki
2021-06-22 9:01 ` Quentin Perret
2021-06-22 9:25 ` Viresh Kumar
2021-06-04 11:05 ` [PATCH v3 4/6] cpufreq: Skip inefficient frequencies in cpufreq_driver_resolve_freq() Vincent Donnefort
2021-06-04 18:25 ` Matthias Kaehlcke
2021-06-04 11:06 ` [PATCH v3 5/6] cpufreq: Mark inefficient frequencies using the Energy Model Vincent Donnefort
2021-06-04 18:35 ` Matthias Kaehlcke
2021-06-04 11:06 ` [PATCH v3 6/6] PM / EM: Skip inefficient states Vincent Donnefort
2021-06-04 18:49 ` Matthias Kaehlcke
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=20210706085039.eb7wzc2dpnd2v6yo@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=dietmar.eggemann@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=peterz@infradead.org \
--cc=qperret@google.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=vincent.donnefort@arm.com \
--cc=vincent.guittot@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).