From: Kevin Hilman <khilman@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PM-WIP_CPUFREQ][PATCH 4/6 v2] OMAP2: cpufreq: use clk_init_cpufreq_table if OPPs not available
Date: Thu, 19 May 2011 15:12:28 +0200 [thread overview]
Message-ID: <87d3jeal6r.fsf@ti.com> (raw)
In-Reply-To: <1305704266-17623-5-git-send-email-nm@ti.com> (Nishanth Menon's message of "Wed, 18 May 2011 02:37:44 -0500")
Nishanth Menon <nm@ti.com> writes:
> OMAP2 does not use OPP tables at the moment for DVFS. Currently,
> we depend on opp table initialization to give us the freq_table,
> which makes sense for OMAP3+. for OMAP2, we should be using
> clk_init_cpufreq_table - so if the opp based frequency table
> initilization fails, fall back to clk_init_cpufreq_table to give
> us the table.
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
This is a good approach, but for readability, the OPP version and the
clk version should probably be separated into separate functions, along
with their error handling.
Minor: please capitalize acronyms: OPP, CPU, OMAP, etc...
Kevin
> ---
> arch/arm/mach-omap2/omap2plus-cpufreq.c | 9 ++++++++-
> 1 files changed, 8 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/omap2plus-cpufreq.c b/arch/arm/mach-omap2/omap2plus-cpufreq.c
> index 45f1e9e..854f4b3 100644
> --- a/arch/arm/mach-omap2/omap2plus-cpufreq.c
> +++ b/arch/arm/mach-omap2/omap2plus-cpufreq.c
> @@ -180,7 +180,13 @@ static int __cpuinit omap_cpu_init(struct cpufreq_policy *policy)
> pr_warning("%s: unable to get the mpu device\n", __func__);
> return -EINVAL;
> }
> - opp_init_cpufreq_table(mpu_dev, &freq_table);
> +
> + /*
> + * if we dont get cpufreq table using opp, use traditional omap2 lookup
> + * as a fallback
> + */
> + if (opp_init_cpufreq_table(mpu_dev, &freq_table))
> + clk_init_cpufreq_table(&freq_table);
>
> if (freq_table) {
> result = cpufreq_frequency_table_cpuinfo(policy, freq_table);
> @@ -188,6 +194,7 @@ static int __cpuinit omap_cpu_init(struct cpufreq_policy *policy)
> cpufreq_frequency_table_get_attr(freq_table,
> policy->cpu);
> } else {
> + clk_exit_cpufreq_table(&freq_table);
> WARN(true, "%s: fallback to clk_round(freq_table=%d)\n",
> __func__, result);
> kfree(freq_table);
next prev parent reply other threads:[~2011-05-19 13:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PM-WIP_CPUFREQ][PATCH 0/5] Cleanups for cpufreq>
2011-05-18 7:37 ` [PM-WIP_CPUFREQ][PATCH 0/6 v2] Cleanups for cpufreq Nishanth Menon
2011-05-18 7:37 ` [PM-WIP_CPUFREQ][PATCH 1/6 v2] OMAP2+: cpufreq: free up table on exit Nishanth Menon
2011-05-19 10:26 ` Kevin Hilman
2011-05-19 13:48 ` Menon, Nishanth
2011-05-18 7:37 ` [PM-WIP_CPUFREQ][PATCH 2/6 v2] OMAP2+: cpufreq: handle invalid cpufreq table Nishanth Menon
2011-05-18 7:37 ` [PM-WIP_CPUFREQ][PATCH 3/6 v2] OMAP2+: cpufreq: minor comment cleanup Nishanth Menon
2011-05-18 20:08 ` Todd Poynor
2011-05-18 20:34 ` Menon, Nishanth
2011-05-18 7:37 ` [PM-WIP_CPUFREQ][PATCH 4/6 v2] OMAP2: cpufreq: use clk_init_cpufreq_table if OPPs not available Nishanth Menon
2011-05-19 13:12 ` Kevin Hilman [this message]
2011-05-19 13:51 ` Menon, Nishanth
2011-05-25 0:01 ` Kevin Hilman
2011-05-25 7:44 ` Menon, Nishanth
2011-05-18 7:37 ` [PM-WIP_CPUFREQ][PATCH 5/6 v2] OMAP2+: cpufreq: use cpufreq_frequency_table_target Nishanth Menon
2011-05-18 7:37 ` [PM-WIP_CPUFREQ][PATCH 6/6 v2] OMAP2+: cpufreq: fix freq_table leak Nishanth Menon
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=87d3jeal6r.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.