All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Thomas Abraham <thomas.abraham@linaro.org>,
	linux-samsung-soc@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	devicetree-discuss@lists.ozlabs.org, rob.herring@calxeda.com,
	kgene.kim@samsung.com, broonie@opensource.wolfsonmicro.com,
	patches@linaro.org
Subject: Re: [PATCH 1/2] PM / Domains: Add OF support
Date: Tue, 3 Jan 2012 23:28:44 +0100	[thread overview]
Message-ID: <201201032328.45288.rjw@sisk.pl> (raw)
In-Reply-To: <20120102065956.GA13015@ponder.secretlab.ca>

On Monday, January 02, 2012, Grant Likely wrote:
> On Mon, Dec 26, 2011 at 08:13:19PM +0100, Rafael J. Wysocki wrote:
> > Hi,
> > 
> > On Monday, December 12, 2011, 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.
> > 
> > That sounds fine except for one thing: PM domains are not devices, so adding
> > "device node" pointers to them is kind of confusing.  Perhaps there should be
> > something like struct dt_node, representing a more general device tree node?
> 
> struct device_node has nothing to do with struct device.  device_node is a
> generic device tree node.

So the name is kind of confusing. :-)

> Thomas' approach is fine.

Well, I guess so.

Thanks,
Rafael

WARNING: multiple messages have this Message-ID (diff)
From: rjw@sisk.pl (Rafael J. Wysocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] PM / Domains: Add OF support
Date: Tue, 3 Jan 2012 23:28:44 +0100	[thread overview]
Message-ID: <201201032328.45288.rjw@sisk.pl> (raw)
In-Reply-To: <20120102065956.GA13015@ponder.secretlab.ca>

On Monday, January 02, 2012, Grant Likely wrote:
> On Mon, Dec 26, 2011 at 08:13:19PM +0100, Rafael J. Wysocki wrote:
> > Hi,
> > 
> > On Monday, December 12, 2011, 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.
> > 
> > That sounds fine except for one thing: PM domains are not devices, so adding
> > "device node" pointers to them is kind of confusing.  Perhaps there should be
> > something like struct dt_node, representing a more general device tree node?
> 
> struct device_node has nothing to do with struct device.  device_node is a
> generic device tree node.

So the name is kind of confusing. :-)

> Thomas' approach is fine.

Well, I guess so.

Thanks,
Rafael

  reply	other threads:[~2012-01-03 22:25 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12 15:46 [PATCH 0/2] ARM: Exynos: Adapt to generic power domain Thomas Abraham
2011-12-12 15:46 ` Thomas Abraham
2011-12-12 15:46 ` [PATCH 1/2] PM / Domains: Add OF support Thomas Abraham
2011-12-12 15:46   ` Thomas Abraham
2011-12-12 15:46   ` [PATCH 2/2] ARM: Exynos: Hook up power domains to generic power domain infrastructure Thomas Abraham
2011-12-12 15:46     ` Thomas Abraham
2011-12-26 19:06     ` Mark Brown
2011-12-26 19:06       ` Mark Brown
2011-12-27 22:16       ` Sylwester Nawrocki
2011-12-27 22:16         ` Sylwester Nawrocki
2011-12-27 23:14     ` Sylwester Nawrocki
2011-12-27 23:14       ` Sylwester Nawrocki
2011-12-28  5:25       ` Thomas Abraham
2011-12-28  5:25         ` Thomas Abraham
2011-12-28 11:09         ` Sylwester Nawrocki
2011-12-28 11:09           ` Sylwester Nawrocki
2011-12-28 18:58     ` Sylwester Nawrocki
2011-12-28 18:58       ` Sylwester Nawrocki
2012-01-02  2:14       ` Thomas Abraham
2012-01-02  2:14         ` Thomas Abraham
2012-01-02 22:19         ` Sylwester Nawrocki
2012-01-02 22:19           ` Sylwester Nawrocki
     [not found]           ` <4F022D7D.3060802-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-01-03  8:23             ` Thomas Abraham
2012-01-03  8:23               ` Thomas Abraham
2012-01-04  7:00               ` Grant Likely
2012-01-04  7:00                 ` Grant Likely
2012-01-04  7:29                 ` Kukjin Kim
2012-01-04  7:29                   ` Kukjin Kim
2011-12-26 11:29   ` [PATCH 1/2] PM / Domains: Add OF support Mark Brown
2011-12-26 11:29     ` Mark Brown
2011-12-26 19:13   ` Rafael J. Wysocki
2011-12-26 19:13     ` Rafael J. Wysocki
2011-12-26 19:24     ` Mark Brown
2011-12-26 19:24       ` Mark Brown
2011-12-26 20:44       ` Rafael J. Wysocki
2011-12-26 20:44         ` Rafael J. Wysocki
2011-12-28  5:10         ` Thomas Abraham
2011-12-28  5:10           ` Thomas Abraham
2011-12-28 22:17           ` Rafael J. Wysocki
2011-12-28 22:17             ` Rafael J. Wysocki
2012-01-02  3:47             ` Thomas Abraham
2012-01-02  3:47               ` Thomas Abraham
2012-01-03 22:30               ` Rafael J. Wysocki
2012-01-03 22:30                 ` Rafael J. Wysocki
2012-01-05 15:42                 ` Thomas Abraham
2012-01-05 15:42                   ` Thomas Abraham
2012-01-02  6:59     ` Grant Likely
2012-01-02  6:59       ` Grant Likely
2012-01-03 22:28       ` Rafael J. Wysocki [this message]
2012-01-03 22:28         ` Rafael J. Wysocki

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=201201032328.45288.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=kgene.kim@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=patches@linaro.org \
    --cc=rob.herring@calxeda.com \
    --cc=thomas.abraham@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.