From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>, Stephen Boyd <sboyd@codeaurora.org>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
robh+dt@kernel.org, nm@ti.com,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH 0/3] PM / OPP: Parse opp-supported-hw/opp-<prop>-<name> bindings
Date: Mon, 16 Nov 2015 16:07:25 +0530 [thread overview]
Message-ID: <cover.1447669859.git.viresh.kumar@linaro.org> (raw)
Hi Rafael,
The bindings are reviewed now and here is the code to parse them. The
first patch is a minor cleanup and other two contain the real stuff.
Rebased over: v4.4-rc1 + OPP debugfs support patch.
Tested-on: Exynos 5250, dual core A15.
Viresh Kumar (3):
PM / OPP: Add missing doc comments
PM / OPP: Parse 'opp-supported-hw' binding
PM / OPP: Parse 'opp-<prop>-<name>' bindings
drivers/base/power/opp/core.c | 301 ++++++++++++++++++++++++++++++++++++++++--
drivers/base/power/opp/opp.h | 11 +-
include/linux/pm_opp.h | 21 +++
3 files changed, 319 insertions(+), 14 deletions(-)
--
2.6.2.198.g614a2ac
next reply other threads:[~2015-11-16 10:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 10:37 Viresh Kumar [this message]
2015-11-16 10:37 ` [PATCH 1/3] PM / OPP: Add missing doc comments Viresh Kumar
2015-11-16 10:37 ` Viresh Kumar
2015-11-16 12:14 ` Pavel Machek
2015-11-18 22:29 ` Stephen Boyd
2015-11-16 10:37 ` [PATCH 2/3] PM / OPP: Parse 'opp-supported-hw' binding Viresh Kumar
2015-11-16 10:37 ` Viresh Kumar
2015-11-18 22:53 ` Stephen Boyd
2015-11-19 2:00 ` Viresh Kumar
2015-11-19 3:02 ` Viresh Kumar
2015-11-16 10:37 ` [PATCH 3/3] PM / OPP: Parse 'opp-<prop>-<name>' bindings Viresh Kumar
2015-11-16 10:37 ` Viresh Kumar
2015-11-19 1:12 ` Stephen Boyd
2015-11-19 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=cover.1447669859.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.