From: Viresh Kumar <viresh.kumar@linaro.org>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Shawn Guo <shawn.guo@linaro.org>, Nishanth Menon <nm@ti.com>,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Tomasz Figa <t.figa@samsung.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas P Abraham <thomas.ab@samsung.com>,
Arvind Chauhan <arvind.chauhan@arm.com>,
Sachin Kamat <spk.linux@gmail.com>
Subject: Re: [PATCH 07/14] cpufreq: cpu0: OPPs can be populated at runtime
Date: Thu, 10 Jul 2014 16:49:52 +0530 [thread overview]
Message-ID: <CAKohpo=KUktq8XJv7Ayis1Q3ik+Wh3wb8wN6VpRAtOsbbv9XCw@mail.gmail.com> (raw)
In-Reply-To: <53BD5564.2060704@ti.com>
On 9 July 2014 20:14, Santosh Shilimkar <santosh.shilimkar@ti.com> wrote:
> Assuming you are updating bidnings as suggested by Stephen,
> patch looks good to me.
> Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Why do you still have a separate cpufreq driver for omap?
Would this patch help getting that out?
I see this for omap:
static inline void omap_init_cpufreq(void)
{
struct platform_device_info devinfo = { };
if (!of_have_populated_dt())
devinfo.name = "omap-cpufreq";
else
devinfo.name = "cpufreq-generic";
platform_device_register_full(&devinfo);
}
and it makes me believe that you were just waiting for this patch?
next prev parent reply other threads:[~2014-07-10 11:19 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 16:32 [PATCH 00/14] cpufreq: cpu0: Extend support beyond CPU0, V2 Viresh Kumar
2014-07-01 16:32 ` [PATCH 01/14] of: Create of_property_match() Viresh Kumar
2014-07-01 16:32 ` [PATCH 02/14] clk: Create of_clk_shared_by_cpus() Viresh Kumar
2014-07-01 18:00 ` Stephen Boyd
2014-07-02 1:57 ` Viresh Kumar
2014-07-09 14:38 ` Santosh Shilimkar
2014-07-09 15:20 ` Viresh Kumar
[not found] ` <5f7164d789e87c62d722b575980c92dfd0504334.1404231535.git.viresh.kumar@linar o.org>
2014-07-28 14:01 ` Grant Likely
2014-07-01 16:32 ` [PATCH 03/14] cpufreq: Add support for per-policy driver data Viresh Kumar
2014-07-09 14:33 ` Santosh Shilimkar
2014-07-09 15:07 ` Viresh Kumar
2014-07-01 16:32 ` [PATCH 04/14] cpufreq: cpu0: Add Module Author Viresh Kumar
2014-07-09 14:42 ` Santosh Shilimkar
2014-07-09 15:08 ` Viresh Kumar
2014-07-09 15:24 ` Santosh Shilimkar
2014-07-01 16:32 ` [PATCH 05/14] cpufreq: cpu0: don't validate clock on clk_put() Viresh Kumar
2014-07-09 14:42 ` Santosh Shilimkar
2014-07-01 16:32 ` [PATCH 06/14] cpufreq: cpu0: defer probe if clock isn't registered yet Viresh Kumar
2014-07-02 5:53 ` Shawn Guo
2014-07-02 5:55 ` Viresh Kumar
2014-07-02 11:32 ` Viresh Kumar
2014-07-03 0:38 ` Stephen Boyd
2014-07-03 2:19 ` Viresh Kumar
2014-07-09 14:43 ` Santosh Shilimkar
2014-07-01 16:32 ` [PATCH 07/14] cpufreq: cpu0: OPPs can be populated at runtime Viresh Kumar
2014-07-01 18:02 ` Stephen Boyd
2014-07-02 2:03 ` Viresh Kumar
2014-07-02 4:03 ` [PATCH V2 Resend " Viresh Kumar
2014-07-09 14:44 ` [PATCH " Santosh Shilimkar
2014-07-09 15:09 ` Viresh Kumar
2014-07-10 11:19 ` Viresh Kumar [this message]
2014-07-10 12:39 ` Nishanth Menon
2014-07-10 13:31 ` Santosh Shilimkar
2014-07-10 13:36 ` Viresh Kumar
2014-07-01 16:32 ` [PATCH 08/14] cpufreq: cpu0: use dev_{err|warn|dbg} instead of pr_{err|warn|debug} Viresh Kumar
2014-07-09 14:45 ` Santosh Shilimkar
2014-07-01 16:32 ` [PATCH 09/14] cpufreq: cpu0: Move per-cluster initialization code to ->init() Viresh Kumar
2014-07-03 0:43 ` Stephen Boyd
2014-07-03 2:11 ` Viresh Kumar
2014-07-09 14:53 ` Santosh Shilimkar
2014-07-09 15:17 ` Viresh Kumar
2014-07-09 15:26 ` Santosh Shilimkar
2014-07-09 15:27 ` Viresh Kumar
2014-07-09 15:29 ` Santosh Shilimkar
2014-07-09 15:33 ` Viresh Kumar
2014-07-01 16:32 ` [PATCH 10/14] cpufreq: cpu0: try regulators with name "cpu-supply" Viresh Kumar
2014-07-01 16:32 ` [PATCH 11/14] cpufreq: cpu0: Make allocate_resources() work for any CPU Viresh Kumar
2014-07-01 16:32 ` [PATCH 12/14] cpufreq: cpu0: Extend support beyond CPU0 Viresh Kumar
2014-07-02 4:03 ` [PATCH V2 Resend " Viresh Kumar
2014-07-01 16:32 ` [PATCH 13/14] cpufreq: cpu0: rename driver and internals to 'cpufreq_generic' Viresh Kumar
2014-07-01 16:32 ` [PATCH 14/14] cpufreq: generic: set platform_{driver|device} '.name' to 'cpufreq-generic' Viresh Kumar
2014-07-02 4:12 ` [PATCH 00/14] cpufreq: cpu0: Extend support beyond CPU0, V2 Viresh Kumar
2014-07-03 1:24 ` Stephen Boyd
2014-07-03 2:44 ` Viresh Kumar
2014-07-03 22:16 ` Mike Turquette
2014-07-04 4:21 ` Viresh Kumar
2014-07-08 4:50 ` Viresh Kumar
2014-07-09 17:41 ` Stephen Boyd
2014-07-16 16:01 ` Viresh Kumar
2014-07-16 21:18 ` Rafael J. Wysocki
2014-07-17 0:28 ` Viresh Kumar
2014-07-17 7:35 ` Thomas Petazzoni
2014-07-17 7:41 ` Viresh Kumar
2014-07-18 1:02 ` Rafael J. Wysocki
2014-07-18 4:17 ` Viresh Kumar
2014-07-24 10:48 ` Viresh Kumar
2014-07-25 14:29 ` Rob Herring
2014-07-25 14:34 ` Viresh Kumar
2014-07-25 15:41 ` Thomas Petazzoni
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='CAKohpo=KUktq8XJv7Ayis1Q3ik+Wh3wb8wN6VpRAtOsbbv9XCw@mail.gmail.com' \
--to=viresh.kumar@linaro.org \
--cc=arvind.chauhan@arm.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=santosh.shilimkar@ti.com \
--cc=sboyd@codeaurora.org \
--cc=shawn.guo@linaro.org \
--cc=spk.linux@gmail.com \
--cc=t.figa@samsung.com \
--cc=thomas.ab@samsung.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 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).