mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Jordan_Hargrave@Dell.com>
To: <bhelgaas@google.com>, <helgaas@kernel.org>, <tglx@linutronix.de>,
	<mingo@redhat.com>, <hpa@zytor.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>,
	<x86@kernel.org>, <jharg93@gmail.com>
Subject: [PATCH v3] Create pci slot files for SMBIOS Type 9 entries
Date: Thu, 18 Feb 2016 20:40:32 +0000	[thread overview]
Message-ID: <1455827823254.98505@Dell.com> (raw)

The following diff builds on the "[PATCHv3] Save SMBIOS Type 9 System Slots"

This will create a /sys/bus/pci/slots/XXX file for each Type 9 entry.  This will be \
used for systemd enumeration of NICs.

Only build if CONFIG_DMI is set

Signed-off-by: Jordan Hargrave <Jordan_Hargrave@dell.com>
---
 arch/x86/pci/common.c | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/arch/x86/pci/common.c b/arch/x86/pci/common.c
index eccd4d9..bfa3c85 100644
--- a/arch/x86/pci/common.c
+++ b/arch/x86/pci/common.c
@@ -173,6 +173,27 @@ void pcibios_fixup_bus(struct pci_bus *b)
 
 void pcibios_add_bus(struct pci_bus *bus)
 {
+#ifdef CONFIG_DMI
+	const struct dmi_device *dmi;
+	struct dmi_dev_onboard *dslot;
+	char sname[128];
+
+	dmi = NULL;
+	while ((dmi = dmi_find_device(DMI_DEV_TYPE_DEV_SLOT,
+				      NULL, dmi)) != NULL) {
+		dslot = dmi->device_data;
+		if (dslot->segment == pci_domain_nr(bus) &&
+		    dslot->bus == bus->number) {
+			dev_info(&bus->dev, "Found SMBIOS Slot %s\n",
+				 dslot->dev.name);
+			snprintf(sname, sizeof(sname), "%s-%d",
+				 dslot->dev.name,
+				 dslot->instance);
+			pci_create_slot(bus, dslot->devfn,
+					sname, NULL);
+		}
+	}
+#endif
 	acpi_pci_add_bus(bus);
 }
 
-- 
2.5.0






 
--jordan hargrave
 Dell Enterprise Linux Engineering  

             reply	other threads:[~2016-02-18 20:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18 20:40 Jordan_Hargrave [this message]
2016-04-10 22:17 ` Bjorn Helgaas
2016-04-12 23:36   ` Jordan Hargrave
2016-04-13  6:31     ` Bjorn Helgaas

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=1455827823254.98505@Dell.com \
    --to=jordan_hargrave@dell.com \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=hpa@zytor.com \
    --cc=jharg93@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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

Powered by JetHome