From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI fixes for 2.6.7
Date: Thu, 24 Jun 2004 14:46:07 -0700 [thread overview]
Message-ID: <1088113567782@kroah.com> (raw)
In-Reply-To: <10881135673488@kroah.com>
ChangeSet 1.1722.103.3, 2004/06/11 17:15:00-07:00, bjorn.helgaas@hp.com
[PATCH] PCI: clarify pci.txt wrt IRQ allocation
I think we should make it explicit that PCI IRQs shouldn't be relied
upon until after pci_enable_device(). This patch:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.7-rc3/2.6.7-rc3-mm1/broken-out/bk-acpi.patch
does PCI interrupt routing (based on ACPI _PRT) and IRQ allocation
at pci_enable_device()-time.
(To avoid breaking things in 2.6, the above patch still allocates
all PCI IRQs in pci_acpi_init(), before any drivers are initialized.
But that shouldn't be needed by correct drivers, and I'd like to
remove it in 2.7.)
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
Documentation/pci.txt | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff -Nru a/Documentation/pci.txt b/Documentation/pci.txt
--- a/Documentation/pci.txt 2004-06-24 13:51:35 -07:00
+++ b/Documentation/pci.txt 2004-06-24 13:51:35 -07:00
@@ -166,8 +166,9 @@
~~~~~~~~~~~~~~~~~~~
Before you do anything with the device you've found, you need to enable
it by calling pci_enable_device() which enables I/O and memory regions of
-the device, assigns missing resources if needed and wakes up the device
-if it was in suspended state. Please note that this function can fail.
+the device, allocates an IRQ if necessary, assigns missing resources if
+needed and wakes up the device if it was in suspended state. Please note
+that this function can fail.
If you want to use the device in bus mastering mode, call pci_set_master()
which enables the bus master bit in PCI_COMMAND register and also fixes
next prev parent reply other threads:[~2004-06-24 22:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 21:30 [BK PATCH] PCI fixes for 2.6.7 Greg KH
2004-06-24 21:46 ` [PATCH] " Greg KH
2004-06-24 21:46 ` Greg KH
2004-06-24 21:46 ` Greg KH [this message]
2004-06-24 21:46 ` Greg KH
2004-06-24 21:46 ` Greg KH
2004-06-24 21:46 ` Greg KH
2004-06-24 21:46 ` Greg KH
2004-06-24 21:46 ` Greg KH
2004-06-24 21:46 ` Greg KH
2004-06-24 21:46 ` Greg KH
2004-06-24 21:46 ` Greg KH
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=1088113567782@kroah.com \
--to=greg@kroah.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox