<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/base/power/suspend.c, branch linux-2.6.23.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.23.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.23.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2007-07-11T23:09:02Z</updated>
<entry>
<title>PM: Do not check parent state in suspend and resume core code</title>
<updated>2007-07-11T23:09:02Z</updated>
<author>
<name>Rafael J. Wysocki</name>
</author>
<published>2007-06-17T17:50:51Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=43a49f8baa6b0e7e5b68ed0ee141e1efacfd9ae6'/>
<id>urn:sha1:43a49f8baa6b0e7e5b68ed0ee141e1efacfd9ae6</id>
<content type='text'>
The checks if the device's parent is in the right state done in
drivers/base/power/suspend.c and drivers/base/power/resume.c serve no particular
purpose, since if the parent is in a wrong power state, the device's suspend or
resume callbacks are supposed to return an error anyway.  Moreover, they are
also useless from the sanity checking point of view, because they rely on the
code being checked to set dev-&gt;parent-&gt;power.power_state.event appropriately,
which need not happen if that code is buggy.  For these reasons they can be
removed.

Signed-off-by: Rafael J. Wysocki &lt;rjw@sisk.pl&gt;
Acked-by: David Brownell &lt;dbrownell@users.sourceforge.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>PM: Remove power_state.event checks from suspend core code</title>
<updated>2007-07-11T23:09:02Z</updated>
<author>
<name>Rafael J. Wysocki</name>
</author>
<published>2007-06-17T17:49:20Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1c3f7d1c79425dd8f627b8da139fd1855f096b6e'/>
<id>urn:sha1:1c3f7d1c79425dd8f627b8da139fd1855f096b6e</id>
<content type='text'>
The suspend routines should be called for every device during a system sleep
transition, regardless of the device's state, so that drivers can regard these
method calls as notifications that the system is about to go to sleep, rather
than as directives to put their devices into the 'off' state.

This is documented in Documentation/power/devices.txt and is already done in
the core resume code, so it seems reasonable to make the core suspend code
behave accordingly.

Signed-off-by: Rafael J. Wysocki &lt;rjw@sisk.pl&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>PM: Remove prev_state from struct dev_pm_info</title>
<updated>2007-07-11T23:09:02Z</updated>
<author>
<name>Rafael J. Wysocki</name>
</author>
<published>2007-06-17T17:48:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=515c53576299e32d6bdb6295cfa2fe1307516eb4'/>
<id>urn:sha1:515c53576299e32d6bdb6295cfa2fe1307516eb4</id>
<content type='text'>
The prev_state member of struct dev_pm_info (defined in include/linux/pm.h) is
only used during a resume to check if the device's state before the suspend was
'off', in which case the device is not resumed.  However, in such cases the
decision whether or not to resume the device should be made on the driver level
and the resume callbacks from the device's bus and class should be executed
anyway (the may be needed for some things other than just powering on the
device).

Signed-off-by: Rafael J. Wysocki &lt;rjw@sisk.pl&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>PM: Simplify suspend_device</title>
<updated>2007-07-11T23:09:01Z</updated>
<author>
<name>Rafael J. Wysocki</name>
</author>
<published>2007-06-13T14:19:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9e584a4fe58881e2dc8f09bdf8444b199ab5ecaf'/>
<id>urn:sha1:9e584a4fe58881e2dc8f09bdf8444b199ab5ecaf</id>
<content type='text'>
Reduce code duplication in drivers/base/suspend.c by introducing a separate
function for printing diagnostic messages.

Signed-off-by: Rafael J. Wysocki &lt;rjw@sisk.pl&gt;
Acked-by: Pavel Machek &lt;pavel@ucw.cz&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>PM: Remove pm_parent from struct dev_pm_info</title>
<updated>2007-07-11T23:09:01Z</updated>
<author>
<name>Rafael J. Wysocki</name>
</author>
<published>2007-06-13T13:53:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9cddad77574313fcee36c5e60122718daa7c0361'/>
<id>urn:sha1:9cddad77574313fcee36c5e60122718daa7c0361</id>
<content type='text'>
The pm_parent member of struct dev_pm_info (defined in include/linux/pm.h) is
only used to check if the device's parent is in the right state while the
device is being suspended or resumed.  However, this can be done just as well
with the help of the parent pointer in struct device, so pm_parent can be
removed along with some code that handles it.

Signed-off-by: Rafael J. Wysocki &lt;rjw@sisk.pl&gt;
Acked-by: David Brownell &lt;dbrownell@users.sourceforge.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>Power Management: use mutexes instead of semaphores</title>
<updated>2007-07-11T23:09:01Z</updated>
<author>
<name>Matthias Kaehlcke</name>
</author>
<published>2007-05-23T21:19:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=11048dcf333c414f237bb713c422e68f67b115a3'/>
<id>urn:sha1:11048dcf333c414f237bb713c422e68f67b115a3</id>
<content type='text'>
The Power Management code uses semaphores as mutexes.  Use the mutex API
instead of the (binary) semaphores.

Signed-off-by: Matthias Kaehlcke &lt;matthias.kaehlcke@gmail.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>Driver core: add suspend() and resume() to struct device_type</title>
<updated>2007-04-27T17:57:29Z</updated>
<author>
<name>Dmitry Torokhov</name>
</author>
<published>2007-04-03T05:08:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f89cbc399ecd924c4bd879344e662aace2274b4f'/>
<id>urn:sha1:f89cbc399ecd924c4bd879344e662aace2274b4f</id>
<content type='text'>
Driver core: add suspend() and resume() to struct device_type

In cases when there are devices of different types in the same class
we can't use class's implementation of suspend and resume methods and
we need to add them to struct device_type instead.

Also fix error handling in resume code (we should not try to call
class's resume method iof bus's resume method for the device failed.

Signed-off-by: Dmitry Torokhov &lt;dtor@mail.ru&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>PM: device_suspend/resume may sleep</title>
<updated>2006-09-26T04:08:38Z</updated>
<author>
<name>Pavel Machek</name>
</author>
<published>2006-09-01T05:02:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bb84c89f94851161f387285d0a449b4a3f29f4df'/>
<id>urn:sha1:bb84c89f94851161f387285d0a449b4a3f29f4df</id>
<content type='text'>
This adds warning when someone tries them from atomic context.

Signed-off-by: Pavel Machek &lt;pavel@suse.cz&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>PM: no suspend_prepare() phase</title>
<updated>2006-09-26T04:08:38Z</updated>
<author>
<name>David Brownell</name>
</author>
<published>2006-08-30T21:09:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1d3a82af45428c5e8deaa119cdeb79611ae46371'/>
<id>urn:sha1:1d3a82af45428c5e8deaa119cdeb79611ae46371</id>
<content type='text'>
Remove the new suspend_prepare() phase.  It doesn't seem very usable,
has never been tested, doesn't address fault cleanup, and would need
a sibling resume_complete(); plus there are no real use cases.  It
could be restored later if those issues get resolved.

Signed-off-by: David Brownell &lt;dbrownell@users.sourceforge.net&gt;
Cc: Linus Torvalds &lt;torvalds@osdl.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>PM: issue PM_EVENT_PRETHAW</title>
<updated>2006-09-26T04:08:37Z</updated>
<author>
<name>David Brownell</name>
</author>
<published>2006-08-15T06:11:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f1cc0a894c963923b766eb2d455747495e6e982d'/>
<id>urn:sha1:f1cc0a894c963923b766eb2d455747495e6e982d</id>
<content type='text'>
This patch is the first of this series that should actually change any
behavior ...  by issuing the new event, now tha the rest of the kernel is
prepared to receive it.

This converts the PM core to issue the new PRETHAW message, which the rest of
the kernel is now ready to receive.

Signed-off-by: David Brownell &lt;dbrownell@users.sourceforge.net&gt;
Cc: "Rafael J. Wysocki" &lt;rjw@sisk.pl&gt;
Cc: Pavel Machek &lt;pavel@ucw.cz&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
</feed>
