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, pavel@ucw.cz, nm@ti.com,
chander.kashyap@linaro.org,
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>,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH Resend] driver/core: cpu: initialize opp table
Date: Mon, 19 May 2014 23:16:20 +0200 [thread overview]
Message-ID: <1458497.gJ29RmexAd@vostro.rjw.lan> (raw)
In-Reply-To: <4765191.0FhyvSGyvF@vostro.rjw.lan>
On Monday, May 19, 2014 11:13:24 PM Rafael J. Wysocki wrote:
> On Monday, May 19, 2014 11:59:11 AM Viresh Kumar wrote:
> > All drivers expecting CPU's OPPs from device tree initialize OPP table using
> > of_init_opp_table() and there is nothing driver specific in that. They all do it
> > in the same way adding to code redundancy.
> >
> > It would be better if we can get rid of code redundancy by initializing CPU OPPs
> > from core code for all CPUs that have a "operating-points" property defined in
> > their node.
> >
> > This patch initializes OPPs as soon as CPU device is registered in
> > register_cpu().
> >
> > 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>
> > Cc: Sudeep Holla <sudeep.holla@arm.com>
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Do patches [2-5/5] depend on this one BTW?
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2014-05-19 20:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 6:17 [PATCH 0/5] CPUFreq: Initialize CPU's OPP tables from core Viresh Kumar
2014-05-19 6:17 ` [PATCH 1/5] driver/core: cpu: initialize opp table Viresh Kumar
2014-05-19 6:29 ` [PATCH Resend] " Viresh Kumar
2014-05-19 21:13 ` Rafael J. Wysocki
2014-05-19 21:16 ` Rafael J. Wysocki [this message]
2014-05-20 2:38 ` Viresh Kumar
2014-05-20 2:38 ` Viresh Kumar
2014-05-21 23:57 ` Rafael J. Wysocki
2014-05-22 4:12 ` Viresh Kumar
2014-05-21 9:35 ` Sudeep Holla
2014-05-21 9:41 ` Viresh Kumar
2014-05-21 9:48 ` Sudeep Holla
2014-05-21 9:54 ` Viresh Kumar
2014-05-19 6:17 ` [PATCH 2/5] cpufreq: arm_big_little: don't " Viresh Kumar
2014-05-19 6:17 ` [PATCH 3/5] cpufreq: imx6q: " Viresh Kumar
2014-05-19 6:17 ` [PATCH 4/5] cpufreq: cpufreq-cpu0: " Viresh Kumar
2014-05-19 6:17 ` [PATCH 5/5] cpufreq: exynos5440: " Viresh Kumar
2014-05-21 8:59 ` [PATCH 0/5] CPUFreq: Initialize CPU's OPP tables from core Shawn Guo
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=1458497.gJ29RmexAd@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=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
all inboxes | Powered by JetHome®