From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "linux-pm" <linux-pm@lists.linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, Len Brown <lenb@kernel.org>,
Pavel Machek <pavel@ucw.cz>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Arjan van de Ven <arjan@infradead.org>,
Zhang Rui <rui.zhang@intel.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Linux PCI <linux-pci@vger.kernel.org>
Subject: Re: [PATCH 1/6] PM: Introduce PM links framework
Date: Fri, 28 Aug 2009 21:11:19 +0200 [thread overview]
Message-ID: <200908282111.19925.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0908281114520.4116-100000@iolanthe.rowland.org>
On Friday 28 August 2009, Alan Stern wrote:
> On Wed, 26 Aug 2009, Rafael J. Wysocki wrote:
>
> > From: Rafael J. Wysocki <rjw@sisk.pl>
> >
> > Introduce a framework for representing off-tree PM dependencies
> > between devices.
> >
> > There are PM dependencies between devices that are not reflected by
> > the structure of the device tree. In other words, as far as PM is
> > concerned, a device may depend on some other devices which are not
> > its children and none of which is its parent.
> >
> > Every such dependency involves two devices, one of which is a
> > "master" and the other of which is a "slave", meaning that the
> > "slave" have to be suspended before the "master" and cannot be
> > woken up before it. Thus every device can be given two lists of
> > "dependency objects", one for the dependencies where the device is
> > the "master" and the other for the dependencies where the device is
> > the "slave". Then, each "dependency object" can be represented as
>
>
> > Index: linux-2.6/drivers/base/power/common.c
> > ===================================================================
> > --- /dev/null
> > +++ linux-2.6/drivers/base/power/common.c
>
> > +/**
> > + * device_for_each_master - Execute given function for each master of a device.
> > + * @slave: Device whose masters to execute the function for.
> > + * @data: Data pointer to pass to the function.
> > + * @fn: Function to execute for each master of @slave.
> > + *
> > + * The function is executed for the parent of the device, if there is one, and
> > + * for each device connected to it via a pm_link object where @slave is the
> > + * "slave".
> > + */
> > +int device_for_each_master(struct device *slave, void *data,
> > + int (*fn)(struct device *dev, void *data))
> > +{
> > + struct pm_link *link;
> > + int idx;
> > + int error = 0;
> > +
> > + if (slave->parent) {
> > + error = fn(slave->parent, data);
> > + if (error)
> > + return error;
> > + }
> > +
> > + idx = srcu_read_lock(&pm_link_ss);
> > +
> > + list_for_each_entry(link, &slave->power.slave_links, slave_hook) {
>
> This needs to use list_for_each_entry_rcu. Likewise in
> device_for_each_slave().
OK, I wasn't sure about that.
Thanks,
Rafael
next prev parent reply other threads:[~2009-08-28 19:10 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 20:17 [PATCH 0/6] PM: Asynchronous suspend and resume of devices Rafael J. Wysocki
2009-08-26 20:20 ` [PATCH 1/6] PM: Introduce PM links framework Rafael J. Wysocki
2009-08-28 15:16 ` Alan Stern
2009-08-28 19:11 ` Rafael J. Wysocki [this message]
2009-08-26 20:21 ` [PATCH 2/6] PM: Asynchronous resume of devices Rafael J. Wysocki
2009-08-28 15:43 ` Alan Stern
2009-08-28 19:38 ` Rafael J. Wysocki
2009-08-28 19:59 ` Alan Stern
2009-08-28 22:22 ` Rafael J. Wysocki
2009-08-28 23:20 ` Rafael J. Wysocki
2009-08-29 2:06 ` Alan Stern
2009-08-29 12:49 ` Rafael J. Wysocki
2009-08-29 19:17 ` Rafael J. Wysocki
2009-08-30 0:53 ` Alan Stern
2009-08-30 0:48 ` Alan Stern
2009-08-30 13:15 ` Rafael J. Wysocki
2009-08-30 21:13 ` [PATCH 10] PM: Measure suspend and resume times for individual devices (was: Re: [PATCH 2/6] PM: Asynchronous resume of devices) Rafael J. Wysocki
2009-08-31 7:25 ` Ingo Molnar
2009-08-31 12:53 ` Rafael J. Wysocki
2009-08-31 13:52 ` Ingo Molnar
2009-08-31 15:56 ` Rafael J. Wysocki
2009-08-31 21:32 ` [PATCH 10 update] PM: Measure suspend and resume times for individual devices Rafael J. Wysocki
2009-09-04 7:51 ` [PATCH 10] PM: Measure suspend and resume times for individual devices (was: Re: [PATCH 2/6] PM: Asynchronous resume of devices) Ingo Molnar
2009-09-04 14:42 ` Rafael J. Wysocki
2009-09-04 19:12 ` Ingo Molnar
2009-09-04 21:56 ` [PATCH 10 update 2x] PM: Measure suspend and resume times for individual devices Rafael J. Wysocki
2009-09-06 4:44 ` Ingo Molnar
2009-09-06 12:13 ` Rafael J. Wysocki
2009-08-31 14:09 ` [PATCH 10] PM: Measure suspend and resume times for individual devices (was: Re: [PATCH 2/6] PM: Asynchronous resume of devices) Alan Stern
2009-08-31 16:00 ` Rafael J. Wysocki
2009-08-30 6:45 ` [PATCH 2/6] PM: Asynchronous resume of devices Pavel Machek
2009-08-30 13:09 ` Rafael J. Wysocki
2009-08-26 20:21 ` [PATCH 3/6] PM: Asynchronous suspend " Rafael J. Wysocki
2009-08-26 20:22 ` [PATCH 4/6] PM: Allow PCI devices to suspend/resume asynchronously Rafael J. Wysocki
2009-08-26 20:23 ` [PATCH 5/6] PM: Allow ACPI " Rafael J. Wysocki
2009-08-26 20:24 ` [PATCH 6/6] PM: Allow serio input " Rafael J. Wysocki
2009-08-27 20:08 ` Dmitry Torokhov
2009-08-27 20:58 ` Rafael J. Wysocki
2009-08-26 22:25 ` [PATCH 0/6] PM: Asynchronous suspend and resume of devices Rafael J. Wysocki
2009-08-27 19:17 ` Rafael J. Wysocki
2009-08-27 19:19 ` [PATCH 7] PM: Add a switch for disabling/enabling asynchronous suspend/resume Rafael J. Wysocki
2009-08-27 20:07 ` Dmitry Torokhov
2009-08-27 22:22 ` [PATCH 7 updated] " Rafael J. Wysocki
2009-08-28 5:22 ` Dmitry Torokhov
2009-08-28 19:42 ` Rafael J. Wysocki
2009-08-27 19:20 ` [PATCH 8] PM: Allow user space to change the power.async_suspend flag of devices Rafael J. Wysocki
2009-08-27 20:04 ` Dmitry Torokhov
2009-08-27 22:24 ` Rafael J. Wysocki
2009-08-28 7:01 ` Pavel Machek
2009-08-29 19:20 ` [PATCH 8 update] " Rafael J. Wysocki
2009-08-27 20:46 ` [PATCH 0/6] PM: Asynchronous suspend and resume " Alan Stern
2009-08-27 21:18 ` Rafael J. Wysocki
2009-08-29 19:22 ` [PATCH 9] PM: Measure device suspend and resume times (was: Re: [PATCH 0/6] PM: Asynchronous suspend and resume of devices) 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=200908282111.19925.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=arjan@infradead.org \
--cc=dmitry.torokhov@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
--cc=rui.zhang@intel.com \
--cc=stern@rowland.harvard.edu \
/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