All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kristen Accardi <kristen.c.accardi@intel.com>
To: pcihpd-discuss@lists.sourceforge.net,
	acpi-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	rajesh.shah@intel.com, greg@kroah.com, len.brown@intel.com
Subject: [patch 4/4] pci: call pci_read_irq for bridges
Date: Wed, 02 Nov 2005 16:24:42 -0800	[thread overview]
Message-ID: <1130977482.8321.42.camel@whizzy> (raw)
In-Reply-To: 20051103001540.365407000@whizzy

Call pci_read_irq() for bridges too, this ensures that the pin
value is stored for later use for bridges that require interrupts.

 drivers/pci/probe.c |    1 +
 1 files changed, 1 insertion(+)

Index: linux-2.6.13/drivers/pci/probe.c
===================================================================
--- linux-2.6.13.orig/drivers/pci/probe.c
+++ linux-2.6.13/drivers/pci/probe.c
@@ -624,6 +624,7 @@ static int pci_setup_device(struct pci_d
 		/* The PCI-to-PCI bridge spec requires that subtractive
 		   decoding (i.e. transparent) bridge must have programming
 		   interface code of 0x01. */ 
+		pci_read_irq(dev);
 		dev->transparent = ((dev->class & 0xff) == 1);
 		pci_read_bases(dev, 2, PCI_ROM_ADDRESS1);
 		break;

--

  parent reply	other threads:[~2005-11-03  0:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051103001540.365407000@whizzy>
2005-11-03  0:24 ` [patch 1/4] pci: store PCI_INTERRUPT_PIN in pci_dev Kristen Accardi
2005-11-03  0:24 ` [patch 2/4] apci: use pin stored " Kristen Accardi
2005-11-03  0:24   ` Kristen Accardi
2005-11-03  0:24 ` [patch 3/4] pci: " Kristen Accardi
2005-11-03  0:24   ` Kristen Accardi
2005-11-03  0:24 ` Kristen Accardi [this message]
2005-11-03  0:55   ` [patch 4/4] pci: call pci_read_irq for bridges Kristen Accardi
2005-11-03  0:55     ` Kristen Accardi

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=1130977482.8321.42.camel@whizzy \
    --to=kristen.c.accardi@intel.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=greg@kroah.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pcihpd-discuss@lists.sourceforge.net \
    --cc=rajesh.shah@intel.com \
    /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.