From: Dilip Kota <eswara.kota@linux.intel.com>
To: linux-pci@vger.kernel.org
Cc: lorenzo.pieralisi@arm.com, gustavo.pimentel@synopsys.com,
andrew.murray@arm.com, linux-kernel@vger.kernel.org,
andriy.shevchenko@intel.com, rdunlap@infradead.org,
cheol.yong.kim@intel.com, chuanhua.lei@linux.intel.com,
qi-ming.wu@intel.com, Dilip Kota <eswara.kota@linux.intel.com>
Subject: [PATCH v1 1/1] PCI: dwc: Kconfig: Mark intel PCIe driver depends on MSI IRQ Domain
Date: Thu, 28 Nov 2019 16:31:13 +0800 [thread overview]
Message-ID: <96078df4bfb6bb252e9a0a447a65a47c70d1fe7d.1574929426.git.eswara.kota@linux.intel.com> (raw)
In-Reply-To: <cover.1574929426.git.eswara.kota@linux.intel.com>
In-Reply-To: <cover.1574929426.git.eswara.kota@linux.intel.com>
Kernel compilation fails for i386 architecture as PCI_MSI_IRQ_DOMAIN
is not set.
Synopsys DesignWare framework depends on the PCI_MSI_IRQ_DOMAIN.
So mark the Intel PCIe controller driver dependency on PCI_MSI_IRQ_DOMAIN
as it uses the Synopsys DesignWare framework.
Reported-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Dilip Kota <eswara.kota@linux.intel.com>
---
drivers/pci/controller/dwc/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/pci/controller/dwc/Kconfig b/drivers/pci/controller/dwc/Kconfig
index e580ae036d77..d8116ed7f3a4 100644
--- a/drivers/pci/controller/dwc/Kconfig
+++ b/drivers/pci/controller/dwc/Kconfig
@@ -212,6 +212,7 @@ config PCIE_ARTPEC6_EP
config PCIE_INTEL_GW
bool "Intel Gateway PCIe host controller support"
depends on OF && (X86 || COMPILE_TEST)
+ depends on PCI_MSI_IRQ_DOMAIN
select PCIE_DW_HOST
help
Say 'Y' here to enable PCIe Host controller support on Intel
--
2.11.0
next prev parent reply other threads:[~2019-11-28 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 8:31 [PATCH v1 0/1]Fix build warning and errors Dilip Kota
2019-11-28 8:31 ` Dilip Kota [this message]
2019-11-28 18:18 ` [PATCH v1 1/1] PCI: dwc: Kconfig: Mark intel PCIe driver depends on MSI IRQ Domain Randy Dunlap
2019-11-28 10:19 ` [PATCH v1 0/1]Fix build warning and errors Lorenzo Pieralisi
2019-11-28 14:46 ` Bjorn Helgaas
2019-12-05 16:23 ` Lorenzo Pieralisi
2019-12-06 6:35 ` Dilip Kota
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=96078df4bfb6bb252e9a0a447a65a47c70d1fe7d.1574929426.git.eswara.kota@linux.intel.com \
--to=eswara.kota@linux.intel.com \
--cc=andrew.murray@arm.com \
--cc=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=chuanhua.lei@linux.intel.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=qi-ming.wu@intel.com \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).