linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: michal.k.k.piotrowski@gmail.com, rbrito@gmail.com,
	"Kristian Høgsberg" <krh@redhat.com>,
	linux-kernel@vger.kernel.org, rjw@sisk.pl,
	linuxppc-dev@ozlabs.org, debian-powerpc@lists.debian.org,
	linux-pm@lists.linux-foundation.org,
	"Tim Teulings" <rael@edge.ping.de>
Subject: [PATCH] Re: Sleep problems with kernels >= 2.6.21 on powerpc
Date: Wed, 5 Sep 2007 20:06:50 +0200 (CEST)	[thread overview]
Message-ID: <tkrat.7174534bdd0ddaff@s5r6.in-berlin.de> (raw)
In-Reply-To: <46DEEBBE.4070201@s5r6.in-berlin.de>

From: Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: firewire: fw-ohci: ignore failure of pci_set_power_state (fix suspend regression)

Fixes "Sleep problems with kernels >= 2.6.21 on powerpc",
http://lkml.org/lkml/2007/8/25/155.

Like it was suggested earlier in http://lkml.org/lkml/2006/10/24/13,
we do *not* fail .suspend anymore if pci_set_power_state failed.

Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
---
 drivers/firewire/fw-ohci.c |    5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

Index: linux-2.6.23-rc4/drivers/firewire/fw-ohci.c
===================================================================
--- linux-2.6.23-rc4.orig/drivers/firewire/fw-ohci.c
+++ linux-2.6.23-rc4/drivers/firewire/fw-ohci.c
@@ -1946,8 +1946,11 @@ static int pci_suspend(struct pci_dev *p
 	}
 	err = pci_set_power_state(pdev, pci_choose_state(pdev, state));
 	if (err) {
+		/*
+		 * Some Apple onboard controllers are known to fail here.
+		 * Ignore it and let the machine proceed to suspend.
+		 */
 		fw_error("pci_set_power_state failed\n");
-		return err;
 	}
 
 	return 0;

-- 
Stefan Richter
-=====-=-=== =--= --=-=
http://arcgraph.de/sr/

  reply	other threads:[~2007-09-05 18:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-26  2:37 Sleep problems with kernels >= 2.6.21 on powerpc Rogério Brito
2007-08-26 23:21 ` Michal Piotrowski
2007-08-27  6:52   ` Rogério Brito
2007-08-27  7:14     ` Tim Teulings
2007-08-30 20:42       ` Tim Teulings
2007-09-05 17:07         ` Andrew Morton
2007-09-05 17:28           ` Randy Dunlap
2007-09-05 17:43             ` Stefan Richter
2007-09-05 17:58               ` Randy Dunlap
2007-09-05 17:47           ` Stefan Richter
2007-09-05 18:06             ` Stefan Richter [this message]
2007-09-05 18:24               ` [PATCH] " Stefan Richter
2007-09-05 19:01             ` firewire in prebuilt kernel packages (was Re: Sleep problems with kernels >= 2.6.21 on powerpc) Stefan Richter
2007-09-05 19:44             ` Sleep problems with kernels >= 2.6.21 on powerpc Andrew Morton
2007-09-05 20:12               ` Stefan Richter
2007-09-06  7:50                 ` [PATCH update] " Stefan Richter
2007-08-27  8:37     ` Michel Dänzer
2007-08-27  9:55     ` Pavel Machek

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=tkrat.7174534bdd0ddaff@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=akpm@linux-foundation.org \
    --cc=debian-powerpc@lists.debian.org \
    --cc=krh@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=rael@edge.ping.de \
    --cc=rbrito@gmail.com \
    --cc=rjw@sisk.pl \
    /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;
as well as URLs for NNTP newsgroup(s).