From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, arvind.chauhan@arm.com,
inderpal.s@samsung.com, nm@ti.com, chander.kashyap@linaro.org,
pavel@ucw.cz, len.brown@intel.com, sudeep.holla@arm.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Amit Daniel Kachhap <amit.daniel@samsung.com>,
Kukjin Kim <kgene.kim@samsung.com>,
Shawn Guo <shawn.guo@linaro.org>
Subject: Re: [PATCH V3 4/8] driver/core: cpu: initialize opp table
Date: Tue, 27 May 2014 01:32:58 +0200 [thread overview]
Message-ID: <3104462.ta2PpIfF9J@vostro.rjw.lan> (raw)
In-Reply-To: <6379a5109bf6b4875cc1656b025f9b8186bbb91a.1400736536.git.viresh.kumar@linaro.org>
On Thursday, May 22, 2014 11:07:28 AM Viresh Kumar wrote:
> Drivers expecting CPU's OPPs from device tree initialize OPP table themselves by
> calling of_init_opp_table() and there is nothing driver specific in that. They
> all do it in the same redundant way.
>
> It would be better if we can get rid of redundancy by initializing CPU OPPs from
> CPU core code for all CPUs (that have a "operating-points" property defined in
> their node).
>
> This patch adds another routine in cpu.c: of_init_cpu_opp_table() and calls it
> right after CPU device is registered in register_cpu(). A dummy implementation
> is also provided to make it lightweight for platforms that don't need it.
>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Amit Daniel Kachhap <amit.daniel@samsung.com>
> Cc: Kukjin Kim <kgene.kim@samsung.com>
> Cc: Shawn Guo <shawn.guo@linaro.org>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
> drivers/base/cpu.c | 30 ++++++++++++++++++++++++++----
> 1 file changed, 26 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/base/cpu.c b/drivers/base/cpu.c
> index 006b1bc..818cfe8 100644
> --- a/drivers/base/cpu.c
> +++ b/drivers/base/cpu.c
> @@ -16,6 +16,7 @@
> #include <linux/acpi.h>
> #include <linux/of.h>
> #include <linux/cpufeature.h>
> +#include <linux/pm_opp.h>
>
> #include "base.h"
>
> @@ -322,6 +323,25 @@ static int cpu_uevent(struct device *dev, struct kobj_uevent_env *env)
> }
> #endif
>
> +#if defined(CONFIG_PM_OPP) && defined(CONFIG_OF)
> +static inline void of_init_cpu_opp_table(struct cpu *cpu)
Do you actually use cpu anywere in this function for anything other than
just accessing cpu->dev? If not, why not to pass cpu->dev to it and
move it somewhere in the OPP core?
> +{
> + int error;
> +
> + /* Initialize CPU's OPP table */
> + error = of_init_opp_table(&cpu->dev);
> + if (!error)
> + dev_dbg(&cpu->dev, "%s: created OPP table for cpu: %d\n",
> + __func__, cpu->dev.id);
> + /* Print error only if there is an issue with OPP table */
> + else if (error != -ENOSYS && error != -ENODEV)
> + dev_err(&cpu->dev, "%s: failed to init OPP table for cpu%d, err: %d\n",
> + __func__, cpu->dev.id, error);
> +}
> +#else
> +static inline void of_init_cpu_opp_table(struct cpu *cpu) {}
> +#endif
> +
> /*
> * register_cpu - Setup a sysfs device for a CPU.
> * @cpu - cpu->hotpluggable field set to 1 will generate a control file in
> @@ -349,10 +369,12 @@ int register_cpu(struct cpu *cpu, int num)
> if (cpu->hotpluggable)
> cpu->dev.groups = hotplugable_cpu_attr_groups;
> error = device_register(&cpu->dev);
> - if (!error)
> - per_cpu(cpu_sys_devices, num) = &cpu->dev;
> - if (!error)
> - register_cpu_under_node(num, cpu_to_node(num));
> + if (error)
> + return error;
> +
> + per_cpu(cpu_sys_devices, num) = &cpu->dev;
> + register_cpu_under_node(num, cpu_to_node(num));
> + of_init_cpu_opp_table(cpu);
>
> return error;
> }
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2014-05-26 23:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 5:37 [PATCH V3 0/8] CPUFreq: Initialize CPU's OPP tables from CPU core Viresh Kumar
2014-05-22 5:37 ` [PATCH V3 1/8] cpufreq: cpufreq-cpu0: remove dependency on thermal Viresh Kumar
2014-05-22 14:52 ` Eduardo Valentin
2014-05-23 4:33 ` Viresh Kumar
2014-05-23 13:21 ` Eduardo Valentin
2014-05-23 13:28 ` Viresh Kumar
2014-05-24 12:59 ` Pavel Machek
2014-05-26 4:04 ` Viresh Kumar
2014-05-22 5:37 ` [PATCH V3 2/8] opp: of_init_opp_table(): return -ENOSYS when feature isn't implemented Viresh Kumar
2014-05-22 5:37 ` [PATCH V3 3/8] opp: call of_node_{get|put}() from of_init_opp_table() Viresh Kumar
2014-05-22 5:37 ` [PATCH V3 4/8] driver/core: cpu: initialize opp table Viresh Kumar
2014-05-26 23:32 ` Rafael J. Wysocki [this message]
2014-05-27 0:04 ` Viresh Kumar
2014-05-27 0:18 ` Viresh Kumar
2014-05-27 11:30 ` Rafael J. Wysocki
2014-05-22 5:37 ` [PATCH V3 5/8] cpufreq: arm_big_little: don't " Viresh Kumar
2014-05-22 5:37 ` [PATCH V3 6/8] cpufreq: imx6q: " Viresh Kumar
2014-05-22 5:37 ` [PATCH V3 7/8] cpufreq: cpufreq-cpu0: " Viresh Kumar
2014-05-22 5:37 ` [PATCH V3 8/8] cpufreq: exynos5440: " 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=3104462.ta2PpIfF9J@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=amit.daniel@samsung.com \
--cc=arvind.chauhan@arm.com \
--cc=chander.kashyap@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=inderpal.s@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=len.brown@intel.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=pavel@ucw.cz \
--cc=shawn.guo@linaro.org \
--cc=sudeep.holla@arm.com \
--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
Powered by JetHome