From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
open list <linux-kernel@vger.kernel.org>
Subject: [PATCH V3 0/2] PM / OPP: Parse opp-supported-hw/opp-<prop>-<name> bindings
Date: Wed, 9 Dec 2015 08:01:45 +0530 [thread overview]
Message-ID: <cover.1449627691.git.viresh.kumar@linaro.org> (raw)
Hi Rafael,
These patches parse the newly added opp-supported-hw/opp-<prop>-<name>
bindings.
Rebased over: Latest pm/linux-next
Tested-on: Exynos 5250, dual core A15.
V2->V3:
- Stephen had an interesting point to make for V2, as the patches
created the dev_opp first and then updated it within the OPP-list
lock. But a simultaneous reader of the dev_opp list need a rcu way of
handling this.
- The big difference, why its not a problem here, is that the platform
needs to call this routine before the OPPs are parsed from DT and the
opp-list will be empty. And so no-readers.
- It wasn't guaranteed earlier, but now we have installed few WARN_ON()
to make sure about that there are no OPPs while these routines are
called.
- It should be pretty safe to get these merged now.
- Lee's work depends on this to be merged,
http://marc.info/?l=linux-kernel&m=144958553611215&w=2
V1->V2:
- Fixed locking
- NUL terminate strings instead of sprintf
- Remove NULL checkers for the routines
- constify 'versions'
- s/EINVAL/EBUSY
- updated comments over routines
- Use of_property_read_u32_index() instead of allocating arrays
- remove dev_opp for failures
Viresh Kumar (2):
PM / OPP: Parse 'opp-supported-hw' binding
PM / OPP: Parse 'opp-<prop>-<name>' bindings
drivers/base/power/opp/core.c | 313 ++++++++++++++++++++++++++++++++++++++++--
drivers/base/power/opp/opp.h | 7 +
include/linux/pm_opp.h | 22 +++
3 files changed, 327 insertions(+), 15 deletions(-)
--
2.6.2.198.g614a2ac
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH V3 0/2] PM / OPP: Parse opp-supported-hw/opp-<prop>-<name> bindings
Date: Wed, 9 Dec 2015 08:01:45 +0530 [thread overview]
Message-ID: <cover.1449627691.git.viresh.kumar@linaro.org> (raw)
Hi Rafael,
These patches parse the newly added opp-supported-hw/opp-<prop>-<name>
bindings.
Rebased over: Latest pm/linux-next
Tested-on: Exynos 5250, dual core A15.
V2->V3:
- Stephen had an interesting point to make for V2, as the patches
created the dev_opp first and then updated it within the OPP-list
lock. But a simultaneous reader of the dev_opp list need a rcu way of
handling this.
- The big difference, why its not a problem here, is that the platform
needs to call this routine before the OPPs are parsed from DT and the
opp-list will be empty. And so no-readers.
- It wasn't guaranteed earlier, but now we have installed few WARN_ON()
to make sure about that there are no OPPs while these routines are
called.
- It should be pretty safe to get these merged now.
- Lee's work depends on this to be merged,
http://marc.info/?l=linux-kernel&m=144958553611215&w=2
V1->V2:
- Fixed locking
- NUL terminate strings instead of sprintf
- Remove NULL checkers for the routines
- constify 'versions'
- s/EINVAL/EBUSY
- updated comments over routines
- Use of_property_read_u32_index() instead of allocating arrays
- remove dev_opp for failures
Viresh Kumar (2):
PM / OPP: Parse 'opp-supported-hw' binding
PM / OPP: Parse 'opp-<prop>-<name>' bindings
drivers/base/power/opp/core.c | 313 ++++++++++++++++++++++++++++++++++++++++--
drivers/base/power/opp/opp.h | 7 +
include/linux/pm_opp.h | 22 +++
3 files changed, 327 insertions(+), 15 deletions(-)
--
2.6.2.198.g614a2ac
next reply other threads:[~2015-12-09 2:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 2:31 Viresh Kumar [this message]
2015-12-09 2:31 ` [PATCH V3 0/2] PM / OPP: Parse opp-supported-hw/opp-<prop>-<name> bindings Viresh Kumar
2015-12-09 2:31 ` [PATCH V3 1/2] PM / OPP: Parse 'opp-supported-hw' binding Viresh Kumar
2015-12-09 2:31 ` Viresh Kumar
2015-12-10 9:55 ` Lee Jones
2015-12-09 2:31 ` [PATCH V3 2/2] PM / OPP: Parse 'opp-<prop>-<name>' bindings Viresh Kumar
2015-12-09 2:31 ` Viresh Kumar
2015-12-10 9:54 ` Lee Jones
2015-12-10 21:45 ` Rafael J. Wysocki
2015-12-11 1:41 ` Viresh Kumar
2016-01-05 10:31 ` Geert Uytterhoeven
2016-01-05 10:46 ` 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.1449627691.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=gregkh@linuxfoundation.org \
--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=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.org \
--cc=vireshk@kernel.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.