From: jakeo@microsoft.com
To: gregkh@linuxfoundation.org, kys@microsoft.com,
linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
olaf@aepfle.de, apw@canonical.com, vkuznets@redhat.com,
tglx@redhat.com, haiyangz@microsoft.com, marc.zyngier@arm.com,
jiang.liu@linux.intel.com, bhelgaas@google.com,
linux-pci@vger.kernel.org
Cc: Jake Oshins <jakeo@microsoft.com>
Subject: [PATCH v4 4/7] PCI: Add fwnode_handle to pci_sysdata
Date: Thu, 29 Oct 2015 23:46:13 +0000 [thread overview]
Message-ID: <1446162376-43419-5-git-send-email-jakeo@microsoft.com> (raw)
In-Reply-To: <1446162376-43419-1-git-send-email-jakeo@microsoft.com>
From: Jake Oshins <jakeo@microsoft.com>
This patch adds an fwnode_handle to struct pci_sysdata, which is
used by the next patch in the series when trying to locate an
IRQ domain associated with a root PCI bus.
Signed-off-by: Jake Oshins <jakeo@microsoft.com>
---
arch/x86/include/asm/pci.h | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/arch/x86/include/asm/pci.h b/arch/x86/include/asm/pci.h
index 4625943..10213a1 100644
--- a/arch/x86/include/asm/pci.h
+++ b/arch/x86/include/asm/pci.h
@@ -20,6 +20,9 @@ struct pci_sysdata {
#ifdef CONFIG_X86_64
void *iommu; /* IOMMU private data */
#endif
+#ifdef CONFIG_PCI_MSI_IRQ_DOMAIN
+ void *fwnode; /* IRQ domain for MSI assignment */
+#endif
};
extern int pci_routeirq;
@@ -41,6 +44,14 @@ static inline int pci_proc_domain(struct pci_bus *bus)
}
#endif
+#ifdef CONFIG_PCI_MSI_IRQ_DOMAIN
+static inline void *pci_fwnode(struct pci_bus *bus)
+{
+ struct pci_sysdata *sd = bus->sysdata;
+ return sd->fwnode;
+}
+#endif
+
/* Can be used to override the logic in pci_scan_bus for skipping
already-configured bus numbers - to be used for buggy BIOSes
or architectures with incomplete PCI setup by the loader */
--
1.9.1
next prev parent reply other threads:[~2015-10-29 23:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 23:46 [PATCH v4 0/7] PCI: hv: New paravirtual PCI front-end for Hyper-V VMs jakeo
2015-10-29 23:46 ` [PATCH v4 1/7] drivers:hv: Export a function that maps Linux CPU num onto Hyper-V proc num jakeo
2015-10-29 23:46 ` [PATCH v4 2/7] drivers:hv: Export hv_do_hypercall() jakeo
2015-10-29 23:46 ` [PATCH v4 3/7] PCI: Make it possible to implement a PCI MSI IRQ Domain in a module jakeo
2015-10-29 23:46 ` jakeo [this message]
2015-10-30 1:55 ` [PATCH v4 4/7] PCI: Add fwnode_handle to pci_sysdata Jiang Liu
2015-10-30 16:01 ` Jake Oshins
2015-10-29 23:46 ` [PATCH v4 5/7] PCI: irqdomain: Look up IRQ domain by fwnode_handle jakeo
2015-10-30 0:28 ` Andy Shevchenko
2015-10-30 15:58 ` Jake Oshins
2015-10-29 23:46 ` [PATCH v4 6/7] drivers:hv: Define the channel type for Hyper-V PCI Express pass-through jakeo
2015-10-30 0:44 ` Andy Shevchenko
2015-10-30 15:57 ` Jake Oshins
2015-10-30 16:52 ` Andy Shevchenko
2015-10-30 16:56 ` KY Srinivasan
2015-10-30 16:58 ` Andy Shevchenko
2015-10-30 17:30 ` KY Srinivasan
2015-10-29 23:46 ` [PATCH v4 7/7] PCI: hv: New paravirtual PCI front-end for Hyper-V VMs jakeo
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=1446162376-43419-5-git-send-email-jakeo@microsoft.com \
--to=jakeo@microsoft.com \
--cc=apw@canonical.com \
--cc=bhelgaas@google.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=jiang.liu@linux.intel.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=olaf@aepfle.de \
--cc=tglx@redhat.com \
--cc=vkuznets@redhat.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 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).