From: Viresh Kumar <viresh.kumar@linaro.org>
To: rjw@sisk.pl
Cc: cpufreq@vger.kernel.org, linux-pm@vger.kernel.org
Subject: [PATCH V2 Resend 15/44] cpufreq: ia64-acpi: use cpufreq_table_validate_and_show()
Date: Mon, 16 Sep 2013 18:56:17 +0530 [thread overview]
Message-ID: <def54433f7c57099a2746c1a4e65f5d152eb85f1.1379309339.git.viresh.kumar@linaro.org> (raw)
In-Reply-To: <cover.1379309339.git.viresh.kumar@linaro.org>
In-Reply-To: <cover.1379309339.git.viresh.kumar@linaro.org>
Lets use cpufreq_table_validate_and_show() instead of calling
cpufreq_frequency_table_cpuinfo() and cpufreq_frequency_table_get_attr().
Cc: Tony Luck <tony.luck@intel.com>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
---
drivers/cpufreq/ia64-acpi-cpufreq.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/cpufreq/ia64-acpi-cpufreq.c b/drivers/cpufreq/ia64-acpi-cpufreq.c
index 3e14f03..6cfad51 100644
--- a/drivers/cpufreq/ia64-acpi-cpufreq.c
+++ b/drivers/cpufreq/ia64-acpi-cpufreq.c
@@ -335,7 +335,7 @@ acpi_cpufreq_cpu_init (
}
}
- result = cpufreq_frequency_table_cpuinfo(policy, data->freq_table);
+ result = cpufreq_table_validate_and_show(policy, data->freq_table);
if (result) {
goto err_freqfree;
}
@@ -356,8 +356,6 @@ acpi_cpufreq_cpu_init (
(u32) data->acpi_data.states[i].status,
(u32) data->acpi_data.states[i].control);
- cpufreq_frequency_table_get_attr(data->freq_table, policy->cpu);
-
/* the first call to ->target() should result in us actually
* writing something to the appropriate registers. */
data->resume = 1;
--
1.7.12.rc2.18.g61b472e
next prev parent reply other threads:[~2013-09-16 13:28 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 13:26 [PATCH V2 Resend 00/44] CPUFreq Cleanup Series: Part I Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 01/44] cpufreq: Add new helper cpufreq_table_validate_and_show() Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 02/44] cpufreq: pxa: call cpufreq_frequency_table_get_attr() Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 03/44] cpufreq: s3cx4xx: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 04/44] cpufreq: sparc: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 05/44] cpufreq: acpi-cpufreq: use cpufreq_table_validate_and_show() Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 06/44] cpufreq: arm_big_little: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 07/44] cpufreq: blackfin: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 08/44] cpufreq: cpufreq-cpu0: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 09/44] cpufreq: cris: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 10/44] cpufreq: davinci: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 11/44] cpufreq: dbx500: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 12/44] cpufreq: e_powersaver: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 13/44] cpufreq: elanfreq: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 14/44] cpufreq: exynos: " Viresh Kumar
2013-09-16 13:26 ` Viresh Kumar [this message]
2013-09-16 13:26 ` [PATCH V2 Resend 16/44] cpufreq: imx6q: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 17/44] cpufreq: kirkwood: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 18/44] cpufreq: longhaul: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 19/44] cpufreq: loongson2: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 20/44] cpufreq: maple: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 21/44] cpufreq: omap: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 22/44] cpufreq: p4-clockmod: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 23/44] cpufreq: pasemi: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 24/44] cpufreq: pmac: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 25/44] cpufreq: powernow: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 26/44] cpufreq: ppc: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 27/44] cpufreq: pxa: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 28/44] cpufreq: s3cx4xx: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 29/44] cpufreq: s5pv210: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 30/44] cpufreq: sa11x0: Expose frequency table Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 31/44] cpufreq: sa11x0: let cpufreq core initialize struct policy fields Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 32/44] cpufreq: sc520: use cpufreq_table_validate_and_show() Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 33/44] cpufreq: sh: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 34/44] cpufreq: sparc: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 35/44] cpufreq: spear: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 36/44] cpufreq: speedstep: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 37/44] cpufreq: tegra: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 38/44] cpufreq: tegra: fix implementation of ->exit() Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 39/44] cpufreq: at32ap: add frequency table Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 40/44] cpufreq: arm_big_little: call cpufreq_frequency_table_put_attr() Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 41/44] cpufreq: blackfin: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 42/44] cpufreq: exynos: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 43/44] cpufreq: loongson2: " Viresh Kumar
2013-09-16 13:26 ` [PATCH V2 Resend 44/44] cpufreq: omap: " Viresh Kumar
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=def54433f7c57099a2746c1a4e65f5d152eb85f1.1379309339.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=cpufreq@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
/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).