linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Waldemar Rymarkiewicz <waldemar.rymarkiewicz@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Waldemar Rymarkiewicz <waldemarx.rymarkiewicz@intel.com>,
	linux-pm@vger.kernel.org, Viresh Kumar <vireshk@kernel.org>,
	Nishanth Menon <nm@ti.com>, Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: [PATCH v4 1/1] PM / OPP: Fix get sharing cpus when hotplug is used
Date: Thu, 27 Jul 2017 13:01:50 +0530	[thread overview]
Message-ID: <20170727073150.GN352@vireshk-i7> (raw)
In-Reply-To: <CAHKzcENdNdfsMmcQe_ET25JSY97dOrq5RkSK_Gpa-pKdFNx_Pw@mail.gmail.com>

On 27-07-17, 09:25, Waldemar Rymarkiewicz wrote:
> On 27 July 2017 at 02:03, Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
> > On Wednesday, July 26, 2017 02:11:38 PM Waldemar Rymarkiewicz wrote:
> >> We fail dev_pm_opp_of_get_sharing_cpus() when possible cpu device does not
> >> exist. This can happen on platforms where not all possible CPUs are
> >> available at start up ie. hotplugged out. Cpu device is not registered in
> >> the system so we are not able to check struct device to set the sharing
> >> CPUs bitmask properly.
> >>
> >> Example (real use case):
> >> 2 physical MIPS cores, 4 VPE, cpu0/2 run Linux and cpu1/3 are not available
> >> for Linux at boot up. cpufreq-dt driver + opp v2 fail to register opp_table
> >> due to the fact there is no struct device for cpu1 (remains offline at
> >> bootup).
> >>
> >> To solve the bug, stop using device struct to check device_node. Instead
> >> get cpu device_node directly from device tree with of_get_cpu_node().
> >>
> >> Signed-off-by: Waldemar Rymarkiewicz <waldemarx.rymarkiewicz@intel.com>
> >> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> >> Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
> >
> > Please fix the build issue reported by 0-day introduced by this patch.
> 
> Where can I find the report? I did not receive anything.

It was sent to your email id:
Waldemar Rymarkiewicz <waldemarx.rymarkiewicz@intel.com>

Here is the link:

http://marc.info/?l=linux-pm&m=150110740706429&w=2

-- 
viresh

  reply	other threads:[~2017-07-27  7:31 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 ` [PATCH v4 0/1] " Waldemar Rymarkiewicz
2017-07-26 13:10 ` [PATCH v4 1/1] PM / OPP: " 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 [this message]
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=20170727073150.GN352@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --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 \
    --cc=waldemarx.rymarkiewicz@intel.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).