From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Stratos Karafotis <stratosk@semaphore.gr>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Randy Dunlap <rdunlap@infradead.org>,
"David S. Miller" <davem@davemloft.net>,
Hans-Christian Egtvedt <egtvedt@samfundet.no>,
Dirk Brandewie <dirk.j.brandewie@intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-doc@vger.kernel.org,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/8] cpufreq: Introduce macros for cpufreq_frequency_table iteration
Date: Tue, 22 Apr 2014 00:06:39 +0200 [thread overview]
Message-ID: <26900651.DzFuLa6PAS@vostro.rjw.lan> (raw)
In-Reply-To: <534E2B44.7090008@semaphore.gr>
On Wednesday, April 16, 2014 10:03:32 AM Stratos Karafotis wrote:
> Many cpufreq drivers need to iterate over the cpufreq_frequency_table
> for various tasks.
>
> This patch introduces two macros which can be used for iteration over
> cpufreq_frequency_table keeping a common coding style across drivers:
>
> - cpufreq_for_each_entry: iterate over each entry of the table
> - cpufreq_for_each_valid_entry: iterate over each entry that contains
> a valid frequency.
>
> It should have no functional changes.
>
> Signed-off-by: Stratos Karafotis <stratosk@semaphore.gr>
Can you please resend the entire series as v4 so that it is clear which version
of each patch is the current one?
> ---
>
> Changes v2 -> v3
> - Better formatting in Documentation
> - Fix spell error in comments
>
> Documentation/cpu-freq/cpu-drivers.txt | 19 +++++++++++++++++++
> drivers/cpufreq/cpufreq.c | 11 +++++++++++
> include/linux/cpufreq.h | 21 +++++++++++++++++++++
> 3 files changed, 51 insertions(+)
>
> diff --git a/Documentation/cpu-freq/cpu-drivers.txt b/Documentation/cpu-freq/cpu-drivers.txt
> index 48da5fd..b045fe5 100644
> --- a/Documentation/cpu-freq/cpu-drivers.txt
> +++ b/Documentation/cpu-freq/cpu-drivers.txt
> @@ -228,3 +228,22 @@ is the corresponding frequency table helper for the ->target
> stage. Just pass the values to this function, and the unsigned int
> index returns the number of the frequency table entry which contains
> the frequency the CPU shall be set to.
> +
> +The following macros can be used as iterators over cpufreq_frequency_table:
> +
> +cpufreq_for_each_entry(pos, table) - iterates over all entries of frequency
> +table.
> +
> +cpufreq-for_each_valid_entry(pos, table) - iterates over all entries,
> +excluding CPUFREQ_ENTRY_INVALID frequencies.
> +Use arguments "pos" - a cpufreq_frequency_table * as a loop cursor and
> +"table" - the cpufreq_frequency_table * you want to iterate over.
> +
> +For example:
> +
> + struct cpufreq_frequency_table *pos, *driver_freq_table;
> +
> + cpufreq_for_each_entry(pos, driver_freq_table) {
> + /* Do something with pos */
> + pos->frequency = ...
> + }
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> index abda660..a517da9 100644
> --- a/drivers/cpufreq/cpufreq.c
> +++ b/drivers/cpufreq/cpufreq.c
> @@ -237,6 +237,17 @@ void cpufreq_cpu_put(struct cpufreq_policy *policy)
> }
> EXPORT_SYMBOL_GPL(cpufreq_cpu_put);
>
> +bool cpufreq_next_valid(struct cpufreq_frequency_table **pos)
> +{
> + while ((*pos)->frequency != CPUFREQ_TABLE_END)
> + if ((*pos)->frequency != CPUFREQ_ENTRY_INVALID)
> + return true;
> + else
> + (*pos)++;
> + return false;
> +}
> +EXPORT_SYMBOL_GPL(cpufreq_next_valid);
> +
> /*********************************************************************
> * EXTERNALLY AFFECTING FREQUENCY CHANGES *
> *********************************************************************/
> diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
> index 5ae5100..77a5fa1 100644
> --- a/include/linux/cpufreq.h
> +++ b/include/linux/cpufreq.h
> @@ -468,6 +468,27 @@ struct cpufreq_frequency_table {
> * order */
> };
>
> +bool cpufreq_next_valid(struct cpufreq_frequency_table **pos);
> +
> +/*
> + * cpufreq_for_each_entry - iterate over a cpufreq_frequency_table
> + * @pos: the cpufreq_frequency_table * to use as a loop cursor.
> + * @table: the cpufreq_frequency_table * to iterate over.
> + */
> +
> +#define cpufreq_for_each_entry(pos, table) \
> + for (pos = table; pos->frequency != CPUFREQ_TABLE_END; pos++)
> +
> +/*
> + * cpufreq_for_each_valid_entry - iterate over a cpufreq_frequency_table
> + * excluding CPUFREQ_ENTRY_INVALID frequencies.
> + * @pos: the cpufreq_frequency_table * to use as a loop cursor.
> + * @table: the cpufreq_frequency_table * to iterate over.
> + */
> +
> +#define cpufreq_for_each_valid_entry(pos, table) \
> + for (pos = table; cpufreq_next_valid(&pos); pos++)
> +
> int cpufreq_frequency_table_cpuinfo(struct cpufreq_policy *policy,
> struct cpufreq_frequency_table *table);
>
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2014-04-21 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 7:03 Stratos Karafotis
2014-04-21 22:06 ` Rafael J. Wysocki [this message]
2014-04-21 23:00 ` [PATCH v4 " Stratos Karafotis
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=26900651.DzFuLa6PAS@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=cpufreq@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dirk.j.brandewie@intel.com \
--cc=egtvedt@samfundet.no \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=stratosk@semaphore.gr \
--cc=viresh.kumar@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®