From: Ondrej Zary <linux@rainbow-software.org>
To: Linux List <linux-kernel@vger.kernel.org>
Subject: [patch] [resend] Fix swsusp with PNP BIOS
Date: Mon, 24 Jul 2006 20:28:01 +0200 [thread overview]
Message-ID: <200607242028.01666.linux@rainbow-software.org> (raw)
Hello,
swsusp is unable to suspend my machine (DTK FortisPro TOP-5A notebook) with
kernel 2.6.17.5 because it's unable to suspend PNP device 00:16 (mouse).
The problem is in PNP BIOS. pnp_bus_suspend() calls pnp_stop_dev() for the
device if the device can be disabled according to pnp_can_disable(). The
problem is that pnpbios_disable_resources() returns -EPERM if the device is
not dynamic (!pnpbios_is_dynamic()) but insert_device() happily sets
PNP_DISABLE capability/flag even if the device is not dynamic. So we try to
disable non-dynamic devices which will fail.
This patch prevents insert_device() from setting PNP_DISABLE if the device is
not dynamic and fixes suspend on my system.
Signed-off-by: Ondrej Zary <linux@rainbow-software.org>
--- linux-2.6.17.5-orig/drivers/pnp/pnpbios/core.c 2006-07-15 04:38:43.000000000 +0200
+++ linux-2.6.17.5/drivers/pnp/pnpbios/core.c 2006-07-22 18:44:36.000000000 +0200
@@ -346,7 +346,7 @@
dev->flags = node->flags;
if (!(dev->flags & PNPBIOS_NO_CONFIG))
dev->capabilities |= PNP_CONFIGURABLE;
- if (!(dev->flags & PNPBIOS_NO_DISABLE))
+ if (!(dev->flags & PNPBIOS_NO_DISABLE) && pnpbios_is_dynamic(dev))
dev->capabilities |= PNP_DISABLE;
dev->capabilities |= PNP_READ;
if (pnpbios_is_dynamic(dev))
--
Ondrej Zary
next reply other threads:[~2006-07-24 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 18:28 Ondrej Zary [this message]
2006-07-24 21:25 ` [patch] [resend] Fix swsusp with PNP BIOS Rafael J. Wysocki
2006-07-24 22:56 ` Pavel Machek
2006-07-24 23:23 ` Nigel Cunningham
2006-07-25 19:17 ` Adam Belay
2006-07-25 19:52 ` 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=200607242028.01666.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=linux-kernel@vger.kernel.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.