From: francescolavra.fl@gmail.com (Francesco Lavra)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
Date: Sun, 10 Mar 2013 16:58:19 +0100 [thread overview]
Message-ID: <513CAD9B.908@gmail.com> (raw)
In-Reply-To: <6cba8f153cfd4b0d3075a34a6dfe287bdec2eb06.1362676407.git.viresh.kumar@linaro.org>
Hi,
On 03/07/2013 06:14 PM, Viresh Kumar wrote:
> big LITTLE is ARM's new Architecture focussing power/performance needs of modern
> world. More information about big LITTLE can be found here:
>
> http://www.arm.com/products/processors/technologies/biglittleprocessing.php
> http://lwn.net/Articles/481055/
>
> In order to keep cpufreq support for all big LITTLE platforms simple/generic,
> this patch tries to add a generic cpufreq driver layer for all big LITTLE
> platforms.
>
> The driver is divided into two parts:
> - Core driver: Generic and shared across all big LITTLE SoC's
> - Glue drivers: Per platform drivers providing ops to the core driver
>
> This patch adds in a generic glue driver which would extract information from
> Device Tree.
>
> Future SoC's can either reuse the DT glue or write their own depending on the
> need.
>
> Signed-off-by: Sudeep KarkadaNagesha <sudeep.karkadanagesha@arm.com>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
[...]
> +void bL_cpufreq_unregister(struct cpufreq_arm_bL_ops *ops)
> +{
> + if (arm_bL_ops != ops) {
> + pr_info("%s: Registered with: %s, can't unregister, exiting\n",
> + __func__, arm_bL_ops->name);
> + }
The code is not doing what the info message says.
> +
> + cpufreq_unregister_driver(&bL_cpufreq_driver);
> + pr_info("%s: Un-registered platform driver: %s\n", __func__,
> + arm_bL_ops->name);
> + arm_bL_ops = NULL;
> +}
> +EXPORT_SYMBOL_GPL(bL_cpufreq_unregister);
--
Francesco
next prev parent reply other threads:[~2013-03-10 15:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 17:14 [PATCH V2] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue Viresh Kumar
2013-03-07 21:56 ` Guennadi Liakhovetski
2013-03-08 4:20 ` Viresh Kumar
2013-03-08 6:11 ` Guennadi Liakhovetski
2013-03-09 3:06 ` Viresh Kumar
2013-03-10 15:58 ` Francesco Lavra [this message]
2013-03-11 0:57 ` Viresh Kumar
2013-03-21 23:50 ` Rafael J. Wysocki
2013-03-22 2:21 ` Viresh Kumar
-- strict thread matches above, loose matches on Subject: below --
2013-03-26 9:51 Viresh Kumar
2013-03-26 13:17 ` Rob Herring
2013-03-26 14:30 ` Viresh Kumar
2013-04-13 20:13 ` Francesco Lavra
2013-04-15 7:02 ` 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=513CAD9B.908@gmail.com \
--to=francescolavra.fl@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).