LKML Archive on
help / color / mirror / Atom feed
From: Karol Wrona <>
To: Lorenzo Pieralisi <>,
	amit daniel kachhap <>
Cc: "" <>,
	"" <>,
	"" <>,
	"Rafael J. Wysocki" <>,
	Ulf Hansson <>,
	Bartlomiej Zolnierkiewicz <>,
	Kyungmin Park <>,
	Karol Wrona <>
Subject: Re: [RFC PATCH 1/1] PM / domains: Add support for virtual power domains
Date: Mon, 02 Feb 2015 13:14:36 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20150130115708.GE8787@red-moon>

On 01/30/2015 12:57 PM, Lorenzo Pieralisi wrote:
> On Fri, Jan 30, 2015 at 08:43:22AM +0000, amit daniel kachhap wrote:
>> Hi Karol,
>> I guess this patch series is not complete and use case implementation
>> will be more helpful for clarity. Also I can think of another way in
>> which this complete implementation can be done with pd name as
>> something "pd-virt". This pd can be handled differently inside the
>> platform specific exynos power off/on function.
> Yes, it would be nice to provide an example to understand what this
> patchset has to achieve. Is this supposed to be a power domain
> used as a container to check for devices runtime state ie dependencies ?
Yes, something like that.

In our case exynos do not enter LPD state with mmc host working and its is in
"top" pd which is not managed in conventional way. If we know runtime status of
the host we can decide what to do. Soon I will send full patchset.

I thought about it as exynos specific but I wonder if that would be needed not
only in exynos.



      reply	other threads:[~2015-02-02 12:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29 18:12 [RFC PATCH 0/1] PM / domains: Add support for virtual power domains Karol Wrona
2015-01-29 18:12 ` [RFC PATCH 1/1] " Karol Wrona
2015-01-30  8:43   ` amit daniel kachhap
2015-01-30 11:57     ` Lorenzo Pieralisi
2015-02-02 12:14       ` Karol Wrona [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).