From: linas@austin.ibm.com (Linas Vepstas)
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: [PATCH] powerpc initialize pci device channel state.
Date: Tue, 19 Dec 2006 14:00:34 -0600 [thread overview]
Message-ID: <20061219200034.GH5506@austin.ibm.com> (raw)
In-Reply-To: <17799.34168.811328.653008@cargo.ozlabs.ibm.com>
Paul,
This patch is critical. Even if the last few looked to be
of low importance, this one is not.
--linas
Initialize the pci device pci channel state. This is critical
for having the pci_channel_offline() routine (in pci.h) to
function correctly.
Signed-off-by: Linas Vepstas <linas@austin.ibm.com>
----
arch/powerpc/kernel/pci_64.c | 1 +
1 file changed, 1 insertion(+)
Index: linux-2.6.19-git7/arch/powerpc/kernel/pci_64.c
===================================================================
--- linux-2.6.19-git7.orig/arch/powerpc/kernel/pci_64.c 2006-12-19 13:50:53.000000000 -0600
+++ linux-2.6.19-git7/arch/powerpc/kernel/pci_64.c 2006-12-19 13:53:29.000000000 -0600
@@ -360,6 +360,7 @@ struct pci_dev *of_create_pci_dev(struct
DBG(" class: 0x%x\n", dev->class);
dev->current_state = 4; /* unknown power state */
+ dev->error_state = pci_channel_io_normal;
if (!strcmp(type, "pci") || !strcmp(type, "pciex")) {
/* a PCI-PCI bridge */
prev parent reply other threads:[~2006-12-19 20:00 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 6:23 Bug fixes for 2.6.20 Paul Mackerras
2006-12-19 9:54 ` [PATCH] Probe Efika platform before CHRP David Woodhouse
2006-12-19 11:39 ` Benjamin Herrenschmidt
2006-12-19 11:55 ` Sylvain Munaut
2006-12-19 14:29 ` David Woodhouse
2006-12-19 15:46 ` Grant Likely
2006-12-19 19:58 ` Benjamin Herrenschmidt
2006-12-19 22:33 ` Sylvain Munaut
2007-01-02 21:29 ` David Woodhouse
2007-01-02 21:37 ` Benjamin Herrenschmidt
2007-01-02 22:04 ` David Woodhouse
2007-01-02 23:04 ` Grant Likely
[not found] ` <45A01416.6080401@genesi-usa.com>
2007-01-06 22:23 ` Grant Likely
2007-01-06 23:13 ` David Woodhouse
2007-01-06 23:37 ` Grant Likely
2007-01-07 2:55 ` Sylvain Munaut
2007-01-07 9:11 ` Raquel Velasco and Bill Buck
2007-03-31 13:15 ` David Woodhouse
2007-03-31 13:18 ` Raquel Velasco and Bill Buck
2007-03-31 13:21 ` David Woodhouse
2007-05-09 11:42 ` Olaf Hering
2007-05-09 11:45 ` Raquel Velasco and Bill Buck
2007-01-07 20:09 ` Matt Sealey
2007-01-07 20:24 ` Segher Boessenkool
2007-01-07 22:10 ` Matt Sealey
2007-01-07 22:35 ` Benjamin Herrenschmidt
2007-01-07 22:35 ` Sylvain Munaut
2007-01-07 23:04 ` Segher Boessenkool
2007-01-07 23:07 ` Matt Sealey
2007-01-07 23:38 ` Sylvain Munaut
2007-01-08 0:37 ` Benjamin Herrenschmidt
2007-01-07 22:32 ` Matt Sealey
2007-01-07 22:39 ` Matt Sealey
2007-01-07 23:27 ` Segher Boessenkool
2007-01-07 21:16 ` Benjamin Herrenschmidt
2007-01-08 2:17 ` David Woodhouse
2007-01-08 9:18 ` Matt Sealey
2007-01-08 12:52 ` Sylvain Munaut
2007-01-08 13:16 ` Sylvain Munaut
2007-01-08 17:25 ` Matt Sealey
2007-01-08 15:44 ` Sylvain Munaut
2007-01-08 17:25 ` Matt Sealey
2007-01-08 17:24 ` Matt Sealey
2007-01-08 17:59 ` Sylvain Munaut
2006-12-19 19:02 ` [PATCH] powerpc export rtas_set_slot_reset() Linas Vepstas
2006-12-19 22:08 ` Brian King
2006-12-19 19:06 ` [PATCH] powerpc fixup error message Linas Vepstas
2006-12-19 20:00 ` Linas Vepstas [this message]
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=20061219200034.GH5506@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 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).