From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
Kumar Gala <galak@codeaurora.org>,
Rob Herring <robherring2@gmail.com>,
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>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: [PATCH] of: treat PCI config space as IORESOURCE_MEM type
Date: Fri, 30 May 2014 14:37:41 -0600 [thread overview]
Message-ID: <20140530203741.GA30134@obsidianresearch.com> (raw)
In-Reply-To: <20140530014116.GF1677@bart.dudau.co.uk>
On Fri, May 30, 2014 at 02:41:17AM +0100, Liviu Dudau wrote:
> Agree, I'm only concerned that if this ECAM config space gets added to
> the list of pci_host_bridge windows it will be indistinguishable from
> IORESOURCE_MEM resources and pci_create_root_bus() will add it to the
> bus and allow devices present on that bus to be assigned addresses from
> that range. Which might not be what one wants for certain BARs.
I wouldn't worry about supporting config in ranges. ECAM is the
logical use for config ranges, but it isn't specified and probably
will never be.
Will's driver the is the only driver I've seen to support ECAM and it
didn't use ranges.
Jason
next prev parent reply other threads:[~2014-05-30 20:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 16:03 [PATCH] of: treat PCI config space as IORESOURCE_MEM type Kumar Gala
2014-05-29 20:44 ` Rob Herring
2014-05-29 20:51 ` Kumar Gala
2014-05-29 21:50 ` Rob Herring
2014-05-30 0:56 ` Liviu Dudau
[not found] ` <20140530005602.GE1677-hOhETlTuV5niMG9XS5x8Mg@public.gmane.org>
2014-05-30 1:29 ` Bjorn Helgaas
2014-05-30 1:41 ` Liviu Dudau
2014-05-30 20:37 ` Jason Gunthorpe [this message]
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=20140530203741.GA30134@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.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=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=robherring2@gmail.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).