From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/4] arm64: dts: APM X-Gene PCIe device tree nodes
Date: Wed, 26 Mar 2014 10:35:13 -0600 [thread overview]
Message-ID: <20140326163513.GB2440@obsidianresearch.com> (raw)
In-Reply-To: <CAL_Jsq+XxAtUeNKFi0hH=ehb_fhFvkM0U1Zm_j1LdtQZbvSzfA@mail.gmail.com>
On Wed, Mar 26, 2014 at 09:28:42AM -0500, Rob Herring wrote:
> Where is the right place for config space? This binding has it here
> and others have it in ranges.
I think all the drivers in drivers/pci/host use 'reg', this was
discussed in the dt-bindings list and AFAIK no new drivers have used
ranges since it was brought up.
> Given that config space type is defined for ranges, I would think
> that is the right place. But Liviu's patches do not process config
> space entries in ranges. Perhaps we need a config space resource
> populated in the bridge struct.
When we talked about this earlier on the DT bindings list the
consensus seemed to be that configuration MMIO ranges should only be
used if the underlying memory was exactly ECAM, and was not to be used
for random configuration related register blocks.
The rational being that generic code, upon seeing that ranges entry,
could just go ahead and assume ECAM mapping.
Jason
next prev parent reply other threads:[~2014-03-26 16:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 23:12 [PATCH v5 0/4] APM X-Gene PCIe controller Tanmay Inamdar
2014-03-19 23:12 ` [PATCH v5 1/4] pci: APM X-Gene PCIe controller driver Tanmay Inamdar
2014-03-21 10:15 ` Sunil Kovvuri
2014-03-21 18:23 ` Tanmay Inamdar
2014-03-25 14:05 ` Liviu Dudau
2014-03-25 19:56 ` Bjorn Helgaas
2014-03-25 8:52 ` Phil.Edworthy at renesas.com
2014-03-25 21:52 ` Tanmay Inamdar
2014-03-25 14:02 ` Liviu Dudau
2014-03-25 22:12 ` Tanmay Inamdar
2014-03-26 10:13 ` Liviu Dudau
2014-03-19 23:12 ` [PATCH v5 2/4] arm64: dts: APM X-Gene PCIe device tree nodes Tanmay Inamdar
2014-03-26 14:28 ` Rob Herring
2014-03-26 15:35 ` Liviu Dudau
2014-03-26 16:35 ` Jason Gunthorpe [this message]
2014-04-16 17:05 ` Liviu Dudau
2014-04-16 21:21 ` Jason Gunthorpe
2014-04-17 0:20 ` Liviu Dudau
2014-04-17 1:24 ` Jason Gunthorpe
2014-04-22 12:49 ` Liviu Dudau
2014-03-19 23:12 ` [PATCH v5 3/4] dt-bindings: pci: xgene pcie device tree bindings Tanmay Inamdar
2014-03-19 23:12 ` [PATCH v5 4/4] MAINTAINERS: entry for APM X-Gene PCIe host driver Tanmay Inamdar
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=20140326163513.GB2440@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.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).