All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Chiang <achiang@hp.com>
To: jbarnes@virtuousgeek.org
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Trent Piepho <xyzzy@speakeasy.org>, Alex Chiang <achiang@hp.com>
Subject: [RFC PATCH v2 02/12] PCI: pci_scan_slot() returns newly found devices
Date: Fri, 13 Feb 2009 13:19:03 -0700	[thread overview]
Message-ID: <20090213201903.19262.63239.stgit@bob.kio> (raw)
In-Reply-To: <20090213201135.19262.67924.stgit@bob.kio>

From: Trent Piepho <xyzzy@speakeasy.org>

pci_scan_slot() has been rewritten to be less complex and will now
return the number of *new* devices found.

Existing callers need not worry because they already assume that
they can't call pci_scan_slot() on an already-scanned slot.

Thus, there is no semantic change for existing callers: returning
newly found devices (this patch) is exactly equal to returning all
found devices (before this patch).

This patch adds some more groundwork to allow us to rescan the
PCI bus during runtime to discover newly added devices.

Signed-off-by: Trent Piepho <xyzzy@speakeasy.org>
Reviewed-by: Alex Chiang <achiang@hp.com>
Signed-off-by: Alex Chiang <achiang@hp.com>
---

 drivers/pci/probe.c |   35 +++++++++++++----------------------
 1 files changed, 13 insertions(+), 22 deletions(-)

diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
index 66b5d1c..d392813 100644
--- a/drivers/pci/probe.c
+++ b/drivers/pci/probe.c
@@ -1030,35 +1030,26 @@ EXPORT_SYMBOL(pci_scan_single_device);
  * Scan a PCI slot on the specified PCI bus for devices, adding
  * discovered devices to the @bus->devices list.  New devices
  * will not have is_added set.
+ *
+ * Returns the number of new devices found.
  */
 int pci_scan_slot(struct pci_bus *bus, int devfn)
 {
-	int func, nr = 0;
-	int scan_all_fns;
-
-	scan_all_fns = pcibios_scan_all_fns(bus, devfn);
-
-	for (func = 0; func < 8; func++, devfn++) {
-		struct pci_dev *dev;
+	int fn, nr = 0;
+	struct pci_dev *dev;
 
-		dev = pci_scan_single_device(bus, devfn);
-		if (dev) {
+	if ((dev = pci_scan_single_device(bus, devfn)))
+		if (!dev->is_added)	/* new device? */
 			nr++;
 
-			/*
-		 	 * If this is a single function device,
-		 	 * don't scan past the first function.
-		 	 */
-			if (!dev->multifunction) {
-				if (func > 0) {
-					dev->multifunction = 1;
-				} else {
- 					break;
-				}
+	if ((dev && dev->multifunction) ||
+	    (!dev && pcibios_scan_all_fns(bus, devfn))) {
+		for (fn = 1; fn < 8; fn++) {
+			if ((dev = pci_scan_single_device(bus, devfn + fn))) {
+				if (!dev->is_added)
+					nr++;
+				dev->multifunction = 1;
 			}
-		} else {
-			if (func == 0 && !scan_all_fns)
-				break;
 		}
 	}
 


  parent reply	other threads:[~2009-02-13 20:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-13 20:18 [RFC PATCH v2 00/12] PCI core learns hotplug Alex Chiang
2009-02-13 20:18 ` [RFC PATCH v2 01/12] PCI: don't scan existing devices Alex Chiang
2009-02-13 20:19 ` Alex Chiang [this message]
2009-02-13 20:19 ` [RFC PATCH v2 03/12] PCI: always scan child buses Alex Chiang
2009-02-13 20:19 ` [RFC PATCH v2 04/12] PCI: properly clean up ASPM link state on device remove Alex Chiang
2009-02-13 20:19 ` [RFC PATCH v2 05/12] PCI: beef up pci_do_scan_bus() Alex Chiang
2009-02-13 20:19 ` [RFC PATCH v2 06/12] PCI: Introduce /sys/bus/pci/rescan Alex Chiang
2009-02-13 20:19 ` [RFC PATCH v2 07/12] PCI: Introduce /sys/bus/pci/devices/.../remove Alex Chiang
2009-02-13 20:19 ` [RFC PATCH v2 08/12] PCI: Introduce /sys/bus/pci/devices/.../rescan Alex Chiang
2009-02-13 20:19 ` [RFC PATCH v2 09/12] PCI Hotplug: restore fakephp interface with complete reimplementation Alex Chiang
2009-02-13 20:19 ` [RFC PATCH v2 10/12] PCI Hotplug: rename legacy_fakephp to fakephp Alex Chiang
2009-02-13 20:19 ` [RFC PATCH v2 11/12] PCI Hotplug: schedule fakephp for feature removal Alex Chiang
2009-02-13 20:19 ` [RFC PATCH v2 12/12] PCI: more whitespace cleanups Alex Chiang

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=20090213201903.19262.63239.stgit@bob.kio \
    --to=achiang@hp.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=xyzzy@speakeasy.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.