linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rjw@sisk.pl (Rafael J. Wysocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] PM / Domains: Add OF support
Date: Tue, 17 Jan 2012 21:45:35 +0100	[thread overview]
Message-ID: <201201172145.35407.rjw@sisk.pl> (raw)
In-Reply-To: <001e01ccd4e8$d04b03a0$70e10ae0$%kim@samsung.com>

On Tuesday, January 17, 2012, Kukjin Kim wrote:
> Rafael J. Wysocki wrote:
> > 
> > On Saturday, January 07, 2012, Thomas Abraham wrote:
> > > A device node pointer is added to generic pm domain structure to
> > associate
> > > the domain with a node in the device tree. The platform code parses the
> > > device tree to find available nodes representing the generic power
> > domain,
> > > instantiates the available domains and initializes them by calling
> > > pm_genpd_init().
> > >
> > > Nodes representing the devices include a phandle of the power domain to
> > > which it belongs. As these devices get instantiated, the driver code
> > > checkes for availability of a power domain phandle, converts the phandle
> > > to a device node and uses the new pm_genpd_of_add_device() api to
> > > associate the device with a power domain.
> > >
> > > pm_genpd_of_add_device() runs through its list of registered power
> > domains
> > > and matches the OF node of the domain with the one specified as the
> > > parameter. If a match is found, the device is associated with the
> > matched
> > > domain.
> > >
> > > Cc: Rafael J. Wysocki <rjw@sisk.pl>
> > > Cc: Rob Herring <rob.herring@calxeda.com>
> > > Cc: Grant Likely <grant.likely@secretlab.ca>
> > > Signed-off-by: Thomas Abraham <thomas.abraham@linaro.org>
> > 
> > I can take this patch for 3.4, but your [2/2] depends on it, so I'm not
> > sure how to handle that.  If you want me to take the other patch too,
> > it'll need ACKs from the Exynos maintaniers.
> > 
> Hi Rafael,
> 
> Basically, looks ok to me.
> 
> But it would be good if [v3 2/2] patch of this series (this patch) could be
> applied in samsung tree to avoid conflicts as it modifies many files. I
> don't want to make a trouble when sending my tree to upstream. Of course, as
> you said, this have a dependency with [v2 1/2]. So if you're ok, let me
> create topic branch will have both(1/2 and 2/2) to merge in your tree.
> 
> How do you think?

That would work for me too.

Thanks,
Rafael

  reply	other threads:[~2012-01-17 20:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-07 10:10 [PATCH v2 0/2] ARM: Exynos: Adapt to generic power domain Thomas Abraham
2012-01-07 10:10 ` [PATCH v2 1/2] PM / Domains: Add OF support Thomas Abraham
2012-01-08 21:23   ` Rafael J. Wysocki
2012-01-09 13:11     ` Thomas Abraham
2012-01-17  7:22     ` Kukjin Kim
2012-01-17 20:45       ` Rafael J. Wysocki [this message]
2012-01-31  5:53         ` Kukjin Kim
2012-02-01 21:32           ` Rafael J. Wysocki
2012-01-07 10:10 ` [PATCH v2 2/2] ARM: Exynos: Hook up power domains to generic power domain infrastructure Thomas Abraham
2012-01-07 14:44   ` Sylwester Nawrocki
2012-01-09 13:19     ` Thomas Abraham
2012-01-09  0:27   ` Kyungmin Park
2012-01-09 13:23     ` Thomas Abraham

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=201201172145.35407.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-arm-kernel@lists.infradead.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).