From: Rene Herman <rene.herman@keyaccess.nl>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Andrew Morton <akpm@osdl.org>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Pierre Ossman <drzeus@drzeus.cx>, Pavel Machek <pavel@suse.cz>,
Ondrej Zary <linux@rainbow-software.org>,
Jaroslav Kysela <perex@perex.cz>,
ALSA development <alsa-devel@alsa-project.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Takashi Iwai <tiwai@suse.de>,
linux-pm@lists.linux-foundation.org
Subject: Re: -mm: pnp-do-not-stop-start-devices-in-suspend-resume-path.patch breaks resuming isapnp cards
Date: Sun, 13 Jan 2008 07:13:35 +0100 [thread overview]
Message-ID: <4789AC0F.9030007@keyaccess.nl> (raw)
In-Reply-To: <200801122250.44220.bjorn.helgaas@hp.com>
On 13-01-08 06:50, Bjorn Helgaas wrote:
> On Saturday 12 January 2008 1:08:01 pm Rene Herman wrote:
>> pnp-do-not-stop-start-devices-in-suspend-resume-path.patch in current -mm
>> breaks resuming isapnp cards from hibernation. They need the pnp_start_dev
>> to enable the device again after hibernation.
>>
>> They don't really need the pnp_stop_dev() which the above mentioned patch
>> also removes but with the pnp_start_dev() restored it seems pnp_stop_dev()
>> should also stay. Bjorn Helgaas should decide -- currently the patch as
>> you have it breaks drivers though. Could you drop it?
>
> Yes, please drop pnp-do-not-stop-start-devices-in-suspend-resume-path.patch
> for now.
Okay, thanks for the reply. And, now that I have your attention, while it's
not important to the issue anymore with the tests removed as the submitted
patch did, do you have an opinion on (include/linux/pnp.h):
/* pnp driver flags */
#define PNP_DRIVER_RES_DO_NOT_CHANGE 0x0001 /* do not change the state
of the device */
#define PNP_DRIVER_RES_DISABLE 0x0003 /* ensure the device is
disabled */
I find DISABLE including DO_NOT_CHANGE rather unexpected...
By the way, I also still have this next one outstanding for you... :-/
http://lkml.org/lkml/2008/1/9/168
Rene.
next prev parent reply other threads:[~2008-01-13 6:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 22:43 PNP_DRIVER_RES_DISABLE breaks swsusp at least with snd_cs4236 Ondrej Zary
2008-01-10 1:53 ` [alsa-devel] " Rene Herman
2008-01-10 7:58 ` Jaroslav Kysela
2008-01-11 1:19 ` Rene Herman
2008-01-11 7:01 ` Pierre Ossman
2008-01-11 14:21 ` Rene Herman
2008-01-11 18:40 ` Ondrej Zary
2008-01-12 1:23 ` Rene Herman
2008-01-12 11:12 ` Pierre Ossman
2008-01-12 13:39 ` Rene Herman
2008-01-12 15:21 ` Pierre Ossman
2008-01-12 16:46 ` Ondrej Zary
2008-01-12 17:00 ` Rene Herman
2008-01-12 19:08 ` Rafael J. Wysocki
2008-01-12 20:08 ` -mm: pnp-do-not-stop-start-devices-in-suspend-resume-path.patch breaks resuming isapnp cards Rene Herman
2008-01-13 5:50 ` Bjorn Helgaas
2008-01-13 6:13 ` Rene Herman [this message]
2008-01-14 22:26 ` Bjorn Helgaas
2008-01-14 23:46 ` Rene Herman
2008-01-15 7:51 ` Jaroslav Kysela
2008-01-16 17:46 ` Bjorn Helgaas
2008-01-16 18:03 ` Ondrej Zary
2008-01-16 18:16 ` Rene Herman
2008-01-12 19:01 ` [alsa-devel] PNP_DRIVER_RES_DISABLE breaks swsusp at least with snd_cs4236 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=4789AC0F.9030007@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=akpm@osdl.org \
--cc=alsa-devel@alsa-project.org \
--cc=bjorn.helgaas@hp.com \
--cc=drzeus@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux@rainbow-software.org \
--cc=pavel@suse.cz \
--cc=perex@perex.cz \
--cc=rjw@sisk.pl \
--cc=tiwai@suse.de \
/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