[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080112162150.1ec9cad0@poseidon.drzeus.cx>
Date: Sat, 12 Jan 2008 16:21:50 +0100
From: Pierre Ossman <drzeus@...eus.cx>
To: Rene Herman <rene.herman@...access.nl>
Cc: Pavel Machek <pavel@...e.cz>, "Rafael J. Wysocki" <rjw@...k.pl>,
Ondrej Zary <linux@...nbow-software.org>,
Jaroslav Kysela <perex@...ex.cz>,
ALSA development <alsa-devel@...a-project.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Bjorn Helgaas <bjorn.helgaas@...com>,
Andrew Morton <akpm@...l.org>, Takashi Iwai <tiwai@...e.de>,
linux-pm@...ts.linux-foundation.org
Subject: Re: [alsa-devel] PNP_DRIVER_RES_DISABLE breaks swsusp at least with
snd_cs4236
On Sat, 12 Jan 2008 14:39:47 +0100
Rene Herman <rene.herman@...access.nl> wrote:
> On 12-01-08 12:12, Pierre Ossman wrote:
>
> > I'm a bit confused here. Bjorn Helgaas wanted to remove the pnp_start/stop_dev() calls completely, and you want them called all the time. :)
>
> Wanted where? Haven't seen a coment from Bjorn? But -- while removing them
> both looks (as) sensible from a mirror-image viewpoint, this wouldn't fix
> the problem.
>
Ah, sorry. It was a different thread. Look for a mail with the subject "PNP: do not stop/start devices in suspend/resume path" in the LKML och linux-pm archives.
>
> But we certainly need the pnp_start_dev() in the current flow of things. It
> not being called is the problem this fixes...
>
I think the previous suggestion was that the drivers should call this, not the core, so that it behaved more like other parts of the kernel (e.g. PCI).
Rgds
Pierre
Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)
Powered by blists - more mailing lists