From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>,
robh+dt@kernel.org, sboyd@codeaurora.org, lee.jones@linaro.org
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
mark.rutland@arm.com, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org, nm@ti.com,
devicetree@vger.kernel.org, b.zolnierkie@samsung.com,
m.szyprowski@samsung.com, Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH V3 0/5] PM / OPP: opp-supported-hw and <prop>-name bindings
Date: Wed, 11 Nov 2015 08:10:53 +0530 [thread overview]
Message-ID: <cover.1447209519.git.viresh.kumar@linaro.org> (raw)
Hi Rafael,
Rob only needs to Ack the modified 2/5 patch and then you can safely
apply this series.
The first patch enables us to select only a subset of OPPs from the
bigger table, based on what version of the hardware we are running on.
The second one enables us to select slightly different values for
multiple properties, based on what kind of hardware they are running on.
The third one removes an (unused) binding, which is replaced by the
second patch with a better solution.
The fourth patch is based on what Stephen suggested (and then reviewed)
in the earlier series, and the 5th one updates the existing users of
these bindings for it.
V2->V3:
- dropped turbo/suspend named properties
- Applied all the Acks
Viresh Kumar (5):
PM / OPP: Add "opp-supported-hw" binding
PM / OPP: Add {opp-microvolt|opp-microamp}-<name> binding
PM / OPP: Remove 'operating-points-names' binding
PM / OPP: Rename OPP nodes as opp@<opp-hz>
ARM: dts: exynos4412: Rename OPP nodes as opp@<opp-hz>
Documentation/devicetree/bindings/opp/opp.txt | 132 ++++++++++++++++++--------
arch/arm/boot/dts/exynos4412.dtsi | 28 +++---
2 files changed, 107 insertions(+), 53 deletions(-)
--
2.6.2.198.g614a2ac
next reply other threads:[~2015-11-11 2:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 2:40 Viresh Kumar [this message]
2015-11-11 2:40 ` [PATCH V3 1/5] PM / OPP: Add "opp-supported-hw" binding Viresh Kumar
2015-11-11 2:40 ` [PATCH V3 2/5] PM / OPP: Add {opp-microvolt|opp-microamp}-<name> binding Viresh Kumar
2015-11-11 20:31 ` Rob Herring
2015-11-12 5:08 ` Viresh Kumar
2015-11-20 5:11 ` Viresh Kumar
2015-11-11 2:40 ` [PATCH V3 3/5] PM / OPP: Remove 'operating-points-names' binding Viresh Kumar
2015-11-11 2:40 ` [PATCH V3 4/5] PM / OPP: Rename OPP nodes as opp@<opp-hz> Viresh Kumar
2015-11-11 2:40 ` [PATCH V3 5/5] ARM: dts: exynos4412: " Viresh Kumar
2015-11-23 23:04 ` Rafael J. Wysocki
2015-11-23 23:10 ` Rafael J. Wysocki
[not found] ` <cover.1447209519.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-11-23 23:02 ` [PATCH V3 0/5] PM / OPP: opp-supported-hw and <prop>-name bindings Rafael J. Wysocki
2015-11-24 1:59 ` Viresh Kumar
2015-12-10 8:58 ` Lee Jones
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.1447209519.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=b.zolnierkie@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=pawel.moll@arm.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 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).