From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Tanmay Inamdar <tinamdar@apm.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Rob Landley <rob@landley.net>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, patches <patches@apm.com>,
Jon Masters <jcm@redhat.com>, Liviu Dudau <Liviu.Dudau@arm.com>
Subject: Re: [RFC PATCH V3 1/4] pci: APM X-Gene PCIe controller driver
Date: Mon, 3 Feb 2014 15:15:59 -0700 [thread overview]
Message-ID: <20140203221559.GG2519@obsidianresearch.com> (raw)
In-Reply-To: <4985267.LnsktRmabM@wuerfel>
On Mon, Feb 03, 2014 at 09:12:32PM +0100, Arnd Bergmann wrote:
> Are you sure that is true for the root bridge as well? I don't
> remember the details, but I though that for the host bridge,
> we don't actually look at the BARs at all.
That is right, but this isn't a host bridge device, it is a PCI-PCI
bridge with root complex registers. The root complex bridge is not the
same as the host bridge.
Unfortunately the implementation is non-conforming. :(
Jason
WARNING: multiple messages have this Message-ID (diff)
From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH V3 1/4] pci: APM X-Gene PCIe controller driver
Date: Mon, 3 Feb 2014 15:15:59 -0700 [thread overview]
Message-ID: <20140203221559.GG2519@obsidianresearch.com> (raw)
In-Reply-To: <4985267.LnsktRmabM@wuerfel>
On Mon, Feb 03, 2014 at 09:12:32PM +0100, Arnd Bergmann wrote:
> Are you sure that is true for the root bridge as well? I don't
> remember the details, but I though that for the host bridge,
> we don't actually look at the BARs at all.
That is right, but this isn't a host bridge device, it is a PCI-PCI
bridge with root complex registers. The root complex bridge is not the
same as the host bridge.
Unfortunately the implementation is non-conforming. :(
Jason
next prev parent reply other threads:[~2014-02-03 22:16 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 21:32 [RFC PATCH V3 0/4] APM X-Gene PCIe controller Tanmay Inamdar
2014-01-24 21:32 ` Tanmay Inamdar
2014-01-24 21:32 ` [RFC PATCH V3 1/4] pci: APM X-Gene PCIe controller driver Tanmay Inamdar
2014-01-24 21:32 ` Tanmay Inamdar
2014-01-30 14:16 ` Arnd Bergmann
2014-01-30 14:16 ` Arnd Bergmann
2014-01-30 14:16 ` Arnd Bergmann
2014-02-03 19:42 ` Tanmay Inamdar
2014-02-03 19:42 ` Tanmay Inamdar
2014-02-03 20:12 ` Arnd Bergmann
2014-02-03 20:12 ` Arnd Bergmann
2014-02-03 20:14 ` Tanmay Inamdar
2014-02-03 20:14 ` Tanmay Inamdar
2014-02-03 22:15 ` Jason Gunthorpe [this message]
2014-02-03 22:15 ` Jason Gunthorpe
2014-02-04 19:22 ` Arnd Bergmann
2014-02-04 19:22 ` Arnd Bergmann
2014-01-24 21:32 ` [RFC PATCH V3 2/4] arm64: dts: APM X-Gene PCIe device tree nodes Tanmay Inamdar
2014-01-24 21:32 ` Tanmay Inamdar
2014-01-30 14:09 ` Arnd Bergmann
2014-01-30 14:09 ` Arnd Bergmann
2014-01-30 14:09 ` Arnd Bergmann
2014-01-24 21:32 ` [RFC PATCH V3 3/4] dt-bindings: pci: xgene pcie device tree bindings Tanmay Inamdar
2014-01-24 21:32 ` Tanmay Inamdar
2014-01-24 21:32 ` [RFC PATCH V3 4/4] MAINTAINERS: entry for APM X-Gene PCIe host driver Tanmay Inamdar
2014-01-24 21:32 ` Tanmay Inamdar
2014-01-25 16:09 ` [RFC PATCH V3 0/4] APM X-Gene PCIe controller Dann Frazier
2014-01-25 16:09 ` Dann Frazier
2014-01-27 22:58 ` Tanmay Inamdar
2014-01-27 22:58 ` Tanmay Inamdar
2014-01-30 0:18 ` Bjorn Helgaas
2014-01-30 0:18 ` Bjorn Helgaas
2014-01-30 0:40 ` Tanmay Inamdar
2014-01-30 0:40 ` Tanmay Inamdar
2014-01-30 14:21 ` Arnd Bergmann
2014-01-30 14:21 ` Arnd Bergmann
2014-01-30 18:06 ` Bjorn Helgaas
2014-01-30 18:06 ` Bjorn Helgaas
2014-01-30 14:17 ` Arnd Bergmann
2014-01-30 14:17 ` Arnd Bergmann
2014-01-30 14:17 ` Arnd Bergmann
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=20140203221559.GG2519@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=Liviu.Dudau@arm.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=jcm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=patches@apm.com \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=tinamdar@apm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.