From: Phil Edworthy <phil.edworthy@renesas.com>
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 3/3] ARM: Enable PCI domains
Date: Mon, 22 Sep 2014 09:51:10 +0000 [thread overview]
Message-ID: <1411379470-20639-4-git-send-email-phil.edworthy@renesas.com> (raw)
In-Reply-To: <1411379470-20639-1-git-send-email-phil.edworthy@renesas.com>
Since there are ARM devices with multiple independant PCI controllers, enable
PCI domains for all ARM devices.
Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
---
Marked as RFC as I am not sure of the impact of enabling PCI domains for all
ARM devices. In the march to 'one kernel to rule them all', I steered clear of
mach specific changes.
arch/arm/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 32cbbd5..8741d3d 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -1274,6 +1274,7 @@ config ISA_DMA_API
config PCI
bool "PCI support" if MIGHT_HAVE_PCI
+ select PCI_DOMAINS
help
Find out whether you have a PCI motherboard. PCI is the name of a
bus system, i.e. the way the CPU talks to the other stuff inside
@@ -1282,7 +1283,6 @@ config PCI
config PCI_DOMAINS
bool
- depends on PCI
config PCI_NANOENGINE
bool "BSE nanoEngine PCI support"
--
2.1.0
next prev parent reply other threads:[~2014-09-22 9:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 9:51 [PATCH 0/3] Add PCI domain support to R-Car drivers Phil Edworthy
2014-09-22 9:51 ` [PATCH 1/3] PCI: rcar-pcie: Add call to get domain nr Phil Edworthy
2014-09-22 9:51 ` [PATCH 2/3] PCI: rcar-internal-pci: " Phil Edworthy
2014-09-22 9:51 ` Phil Edworthy [this message]
2014-09-22 11:28 ` [PATCH 0/3] Add PCI domain support to R-Car drivers Liviu Dudau
2014-09-22 11:40 ` Phil Edworthy
2014-09-22 12:02 ` Liviu Dudau
2014-09-22 21:00 ` Bjorn Helgaas
2014-09-23 10:10 ` Phil Edworthy
2014-09-23 10:32 ` Liviu Dudau
2014-09-23 11:00 ` Phil Edworthy
2014-09-23 11:10 ` Liviu Dudau
2014-09-23 11:38 ` Phil Edworthy
2014-09-23 12:10 ` Liviu Dudau
2014-09-23 12:40 ` Phil Edworthy
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=1411379470-20639-4-git-send-email-phil.edworthy@renesas.com \
--to=phil.edworthy@renesas.com \
--cc=linux-arm-kernel@lists.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).