linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Joonyoung Shim <jy0922.shim@samsung.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	vireshk@kernel.org, nm@ti.com, sboyd@codeaurora.org,
	rjw@rjwysocki.net, len.brown@intel.com, pavel@ucw.cz,
	gregkh@linuxfoundation.org
Subject: Re: [PATCH] PM / OPP: fix CPU device to be removed from OPP table in wrong order
Date: Thu, 24 Nov 2016 14:04:03 +0530	[thread overview]
Message-ID: <20161124083403.GA29969@vireshk-i7> (raw)
In-Reply-To: <1479973761-21225-1-git-send-email-jy0922.shim@samsung.com>

Ho Joonyoung,

On 24-11-16, 16:49, Joonyoung Shim wrote:
> The device that creates OPP table first should be removed from dev_list
> of OPP table in last because it can be used by other resources
> (supported_hw, prop_name, regulator), but not now.

I am not sure what you are trying to do here? Why can't the CPU which
added the OPP should be removed last.

Can you give a real example where you see a problem ?

> If OPP table is
> shared by several CPUs, the CPU device that creates OPP table can be
> removed earlier than other CPU devices.

I don't think that's a problem, though I can be wrong for sure.

-- 
viresh

  reply	other threads:[~2016-11-24  8:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24  7:49 [PATCH] PM / OPP: fix CPU device to be removed from OPP table in wrong order Joonyoung Shim
2016-11-24  8:34 ` Viresh Kumar [this message]
2016-11-25  1:54   ` Joonyoung Shim
2016-11-25  6:57     ` Viresh Kumar
2016-11-25  7:30       ` Joonyoung Shim

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=20161124083403.GA29969@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jy0922.shim@samsung.com \
    --cc=len.brown@intel.com \
    --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 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).