From: Kumar Gala <galak@codeaurora.org>
To: Rob Herring <robh+dt@kernel.org>,
Grant Likely <grant.likely@linaro.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: Kumar Gala <galak@codeaurora.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Liviu Dudau <liviu@dudau.co.uk>,
Kishon Vijay Abraham I <kishon@ti.com>
Subject: [PATCH] of: treat PCI config space as IORESOURCE_MEM type
Date: Thu, 29 May 2014 11:03:46 -0500 [thread overview]
Message-ID: <1401379426-9701-1-git-send-email-galak@codeaurora.org> (raw)
If we have a PCI config space specified in something like a ranges
property we should treat it as memory type resource.
Signed-off-by: Kumar Gala <galak@codeaurora.org>
---
drivers/of/address.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/of/address.c b/drivers/of/address.c
index cb4242a..4e7ee59 100644
--- a/drivers/of/address.c
+++ b/drivers/of/address.c
@@ -122,6 +122,9 @@ static unsigned int of_bus_pci_get_flags(const __be32 *addr)
u32 w = be32_to_cpup(addr);
switch((w >> 24) & 0x03) {
+ case 0x00: /* cfg space */
+ flags |= IORESOURCE_MEM;
+ break;
case 0x01:
flags |= IORESOURCE_IO;
break;
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next reply other threads:[~2014-05-29 16:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 16:03 Kumar Gala [this message]
2014-05-29 20:44 ` [PATCH] of: treat PCI config space as IORESOURCE_MEM type Rob Herring
2014-05-29 20:51 ` Kumar Gala
2014-05-29 21:50 ` Rob Herring
2014-05-30 0:56 ` Liviu Dudau
2014-05-30 1:29 ` Bjorn Helgaas
2014-05-30 1:41 ` Liviu Dudau
2014-05-30 20:37 ` Jason Gunthorpe
2014-05-30 20:44 ` Kumar Gala
2014-05-30 20:45 ` Kumar Gala
2014-05-30 23:11 ` Liviu Dudau
2014-05-30 23:16 ` Bjorn Helgaas
2014-05-30 23:30 ` Liviu Dudau
2014-05-31 0:36 ` Liviu Dudau
2014-05-31 0:36 ` [PATCH 1/2] pci: Add IORESOURCE_BIT entry for PCIe ECAM resources Liviu Dudau
2014-05-31 18:41 ` Arnd Bergmann
2014-06-01 11:26 ` Liviu Dudau
2014-06-02 15:09 ` Grant Likely
2014-06-02 15:40 ` Kumar Gala
2014-06-02 16:23 ` Grant Likely
2014-06-02 18:09 ` Kumar Gala
2014-06-02 19:15 ` Arnd Bergmann
2014-06-02 20:43 ` Kumar Gala
2014-06-02 20:44 ` Arnd Bergmann
2014-06-03 8:44 ` Grant Likely
2014-06-03 9:21 ` Arnd Bergmann
2014-06-03 11:38 ` Grant Likely
2014-05-31 0:36 ` [PATCH 2/2] of: treat PCI config space as IORESOURCE_MEM type with special flags Liviu Dudau
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=1401379426-9701-1-git-send-email-galak@codeaurora.org \
--to=galak@codeaurora.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liviu@dudau.co.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).