From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arvind Chauhan <arvind.chauhan@arm.com>,
Ips Gandhi <inderpal.s@samsung.com>, Nishanth Menon <nm@ti.com>,
Chander Kashyap <chander.kashyap@linaro.org>,
Pavel Machek <pavel@ucw.cz>, "Brown, Len" <len.brown@intel.com>,
Sudeep Holla <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 13:30:09 +0200 [thread overview]
Message-ID: <11801597.a0CDeJOEp5@vostro.rjw.lan> (raw)
In-Reply-To: <CAKohpokZSw430PWjJfYOPA6KXOJiKFhxRi4BuEf6ouMgUHQ+gw@mail.gmail.com>
On Tuesday, May 27, 2014 05:48:27 AM Viresh Kumar wrote:
> On 27 May 2014 05:34, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> > We are also using it for cpu->dev_id, but that's not so important. This
> > routine wouldn't have existed if you wouldn't have asked for it. It is
> > just a wrapper over of_init_opp_table, which also has a dummy
> > implementation when its not supported.
> >
> > So, it might not be worth enough for any other code to use it. :)
> > And so I added it here.
> >
> > Let me know how/where do you want it and I will resend it quickly.
>
> There is another option here, add these print messages in
> of_init_opp_table() ? That's the only difference new wrapper has.
Yeah, put them into of_init_opp_table() rather I'd say.
Rafael
next prev parent reply other threads:[~2014-05-27 11:13 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
2014-05-27 0:04 ` Viresh Kumar
2014-05-27 0:18 ` Viresh Kumar
2014-05-27 11:30 ` Rafael J. Wysocki [this message]
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=11801597.a0CDeJOEp5@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
all inboxes | Powered by JetHome®