From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] OPP: Introduce OPP bindings V2 and supporting code
Date: Fri, 27 Feb 2015 10:55:43 +0530 [thread overview]
Message-ID: <CAKohpokF0_or8aXwzWZ=bUX1Robk8THyqRpKjbaarg9NHufLmw@mail.gmail.com> (raw)
In-Reply-To: <cover.1423642246.git.viresh.kumar@linaro.org>
On 11 February 2015 at 13:46, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> Now that I have received an verbal Ack from Rob Herring (in a personal
> conversation) about the bindings, I am showing how the code looks like with
> these new bindings.
>
> Some part is still now done:
s/now/not
> - Interface for adding new detailed OPPs from platform code instead of DT
> - Providing cpufreq helpers for the next OPPs
> - Providing regulator helpers for the target/min/max ranges
>
> Please provide feedback on how this looks like..
Can we have some reviews of the code changes please ?
--
viresh
next prev parent reply other threads:[~2015-02-27 5:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 8:16 [PATCH 0/7] OPP: Introduce OPP bindings V2 and supporting code Viresh Kumar
2015-02-11 8:16 ` [PATCH 1/7] OPP: Redefine bindings to overcome shortcomings Viresh Kumar
2015-02-23 22:36 ` Kevin Hilman
2015-02-24 4:24 ` Viresh Kumar
2015-02-24 17:12 ` Kevin Hilman
2015-02-25 3:45 ` viresh kumar
2015-02-11 8:16 ` [PATCH 2/7] opp: Relocate few routines Viresh Kumar
2015-02-11 8:16 ` [PATCH 3/7] OPP: Break _opp_add_dynamic() into smaller functions Viresh Kumar
2015-02-11 8:16 ` [PATCH 4/7] opp: Parse new (v2) bindings Viresh Kumar
2015-02-11 8:16 ` [PATCH 5/7] opp: convert device_opp->dev to a list of devices Viresh Kumar
2015-02-11 8:16 ` [PATCH 6/7] opp: Add helpers for initializing CPU opps Viresh Kumar
2015-02-11 8:16 ` [PATCH 7/7] cpufreq-dt: Use DT to set policy->cpus/related_cpus Viresh Kumar
2015-02-12 0:52 ` [PATCH 0/7] OPP: Introduce OPP bindings V2 and supporting code Stephen Boyd
2015-02-12 7:22 ` Viresh Kumar
2015-02-12 8:20 ` Stephen Boyd
2015-02-17 7:46 ` Viresh Kumar
2015-03-22 18:56 ` Mark Brown
2015-02-27 5:25 ` Viresh Kumar [this message]
2015-03-16 9:54 ` Viresh Kumar
2015-04-01 6:22 ` Viresh Kumar
2015-04-01 16:43 ` Rob Herring
2015-04-02 3:00 ` 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='CAKohpokF0_or8aXwzWZ=bUX1Robk8THyqRpKjbaarg9NHufLmw@mail.gmail.com' \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).