From: Viresh Kumar <viresh.kumar@linaro.org>
To: santosh shilimkar <santosh.shilimkar@oracle.com>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Nishanth Menon <nm@ti.com>, Sudeep Holla <Sudeep.Holla@arm.com>,
Stephen Boyd <sboyd@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
Mike Turquette <mike.turquette@linaro.org>,
Rob Herring <rob.herring@linaro.org>,
Grant Likely <grant.likely@linaro.org>,
Abhilash Kesavan <kesavan.abhilash@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Chander Kashyap <k.chander@samsung.com>,
"olof@lixom.net" <olof@lixom.net>,
Thomas Abraham <ta.omasab@gmail.com>
Subject: Re: [RFC] cpufreq: Add "dvfs-method" binding to probe cpufreq drivers
Date: Thu, 27 Nov 2014 10:44:45 +0530 [thread overview]
Message-ID: <CAKohpokLeX+NoD9KX1MWWjyZtu6otw_oryt1f4gwLz7TffcExQ@mail.gmail.com> (raw)
In-Reply-To: <54760107.3010205@oracle.com>
On 26 November 2014 at 22:04, santosh shilimkar
<santosh.shilimkar@oracle.com> wrote:
> Its really not 'dvfs-method' but really the actual driver which you
> want to probe. Also we should just have one global way to parse
> DT vs non-DT cpufreq drivers. In other words, instead of matching
> multiple driver strings for different drivers, we should come up with
> slightly generic binding. Probably 'cpufreq-dt' for all DT based probed
> CPUFREQ drivers.
>
> What you say ?
I got a bit confused. :(
The whole purpose of this binding is to select which cpufreq driver to
choose from the available ones.
Are you saying that we should have only one cpufreq driver that works
with DT ? I don't think that would be the right decision, but we should
try to reuse cpufreq-dt wherever possible.
Or are you saying that some common code should parse this DT information?
This is what I said in the patch, we can write another file which will
just create
a platform_device for us, depending on the string that came in.
next prev parent reply other threads:[~2014-11-27 5:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 8:46 [RFC] cpufreq: Add "dvfs-method" binding to probe cpufreq drivers Viresh Kumar
2014-11-26 8:49 ` Viresh Kumar
2014-11-26 16:34 ` santosh shilimkar
2014-11-27 5:14 ` Viresh Kumar [this message]
2014-11-30 20:04 ` santosh.shilimkar
2014-11-26 17:00 ` Sudeep Holla
2014-11-26 17:04 ` Sudeep Holla
2014-11-27 5:29 ` Viresh Kumar
2014-11-27 9:54 ` Sudeep Holla
2014-11-27 10:22 ` Viresh Kumar
2014-11-27 11:15 ` Sudeep Holla
2014-11-28 6:31 ` Viresh Kumar
2014-11-28 11:51 ` Sudeep Holla
2014-12-01 8:06 ` 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=CAKohpokLeX+NoD9KX1MWWjyZtu6otw_oryt1f4gwLz7TffcExQ@mail.gmail.com \
--to=viresh.kumar@linaro.org \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=Sudeep.Holla@arm.com \
--cc=arnd.bergmann@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=k.chander@samsung.com \
--cc=kesavan.abhilash@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=mike.turquette@linaro.org \
--cc=nm@ti.com \
--cc=olof@lixom.net \
--cc=rjw@rjwysocki.net \
--cc=rob.herring@linaro.org \
--cc=santosh.shilimkar@oracle.com \
--cc=sboyd@codeaurora.org \
--cc=ta.omasab@gmail.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).