linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Waldemar Rymarkiewicz <waldemarx.rymarkiewicz@intel.com>
To: linux-pm@vger.kernel.org
Cc: waldemar.rymarkiewicz@gmail.com,
	Waldemar Rymarkiewicz <waldemarx.rymarkiewicz@intel.com>,
	Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: [PATCH v4 0/1] Fix get sharing cpus when hotplug is used
Date: Wed, 26 Jul 2017 14:11:39 +0200	[thread overview]
Message-ID: <20170726121151.7576-2-waldemarx.rymarkiewicz@intel.com> (raw)
In-Reply-To: <20170726121151.7576-1-waldemarx.rymarkiewicz@intel.com>

Hi,

This patch fixes problem with setting opp shared cpus bitmask on
hotplugable systems. See patch commit message for details.

CHANGLOG:

v4  Added Reviewed-by: Stephen Boyd <sboyd@codeaurora.org> + use pr_err
    instead dev_err for missing opp node phandle.

v3  Acked-by: Viresh Kumar added

v2  Abandon v1 as it was not good enough. Still check all possible CPUs as in
    original code, but don't check device struct. Instead check device_node
    directly in DT.

v1  [PATCH] PM / OPP: Don't check not plugged in CPUs to avoid error
    Avoid error by checking all present cpus instead possible cpus.

Thanks,
/Waldek


Waldemar Rymarkiewicz (1):
  PM / OPP: Fix get sharing cpus when hotplug is used

 drivers/base/power/opp/of.c | 29 +++++++++++++++++------------
 1 file changed, 17 insertions(+), 12 deletions(-)

-- 
2.10.1

  reply	other threads:[~2017-07-26 12:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-26 12:11 [PATCH v4 1/1] PM / OPP: Fix get sharing cpus when hotplug is used Waldemar Rymarkiewicz
2017-07-26 12:11 ` Waldemar Rymarkiewicz [this message]
2017-07-26 13:10 ` Sudeep Holla
2017-07-26 13:54   ` Waldemar Rymarkiewicz
2017-07-26 14:08     ` Sudeep Holla
2017-07-26 14:41       ` Waldemar Rymarkiewicz
2017-07-26 15:20         ` Sudeep Holla
2017-07-27  3:43       ` Viresh Kumar
2017-07-27  0:03 ` Rafael J. Wysocki
2017-07-27  7:25   ` Waldemar Rymarkiewicz
2017-07-27  7:31     ` Viresh Kumar
2017-07-27 10:01   ` Waldemar Rymarkiewicz
2017-07-30 14:54 ` kbuild test robot
2017-07-31 11:14   ` Rafael J. Wysocki
2017-07-31 15:12     ` Waldemar Rymarkiewicz
2017-07-31 18:50       ` Rafael J. Wysocki
2017-08-01  4:37         ` Viresh Kumar
2017-08-01 11:53           ` Rafael J. Wysocki
2017-08-03  1:50           ` [kbuild-all] " Fengguang Wu

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=20170726121151.7576-2-waldemarx.rymarkiewicz@intel.com \
    --to=waldemarx.rymarkiewicz@intel.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=rjw@rjwysocki.net \
    --cc=sboyd@codeaurora.org \
    --cc=vireshk@kernel.org \
    --cc=waldemar.rymarkiewicz@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).