From: Arnd Bergmann <arnd@arndb.de>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Tanmay Inamdar <tinamdar@apm.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Rob Landley <rob@landley.net>, Liviu Dudau <liviu.dudau@arm.com>,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, patches@apm.com, jcm@redhat.com
Subject: Re: [PATCH v10 0/4] APM X-Gene PCIe host controller
Date: Thu, 02 Oct 2014 14:20:49 +0200 [thread overview]
Message-ID: <2135522.DVGa59N1mx@wuerfel> (raw)
In-Reply-To: <20141001191403.GC22713@google.com>
On Wednesday 01 October 2014 13:14:03 Bjorn Helgaas wrote:
> On Fri, Sep 26, 2014 at 02:08:23PM -0700, Tanmay Inamdar wrote:
> > This patch adds support for AppliedMicro X-Gene PCIe host controller. The
> > driver is tested on X-Gene platform with different gen1/2/3 PCIe endpoint
> > cards.
> >
> > X-Gene PCIe controller driver has depedency on the pcie arm64 arch support.
> > Liviu Dudau from ARM has sent a patch set for pcie arm64 arch support and
> > support for creating generic pcie bridge from device tree. Liviu's patches
> > are available here
> > https://lkml.org/lkml/2014/9/23/852
> >
> > If someone wishes to test PCIe on X-Gene with this patch set, above mentioned
> > patches from Liviu must be applied before the patches in this patch set. Also
> > please use latest xgene u-boot firmware.
>
> I applied these on pci/host-xgene (based on pci/host-generic). I hope to
> merge these for v3.18. It'd be nice to have a device tree person like Arnd
> or Rob take a look at the arch/arm64/boot/dts/ bits.
Those changes should normally go through the arm-soc tree, but we
have not done that so far for arm64 stuff, so I'm not blaming anybody.
The dts changes all look good to me, and I think it's ok to have them
go through your tree this time.
Acked-by: Arnd Bergmann <arnd@arndb.de>
In the future, we should all have an eye on this more to ensure that
the .dts changes all go through arm-soc.
Arnd
next prev parent reply other threads:[~2014-10-02 12:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 21:08 [PATCH v10 0/4] APM X-Gene PCIe host controller Tanmay Inamdar
2014-09-26 21:08 ` [PATCH v10 1/4] pci:host: APM X-Gene PCIe host controller driver Tanmay Inamdar
2014-09-26 21:08 ` [PATCH v10 2/4] arm64: dts: APM X-Gene PCIe device tree nodes Tanmay Inamdar
2014-09-26 21:08 ` [PATCH v10 3/4] dt-bindings: pci: xgene pcie device tree bindings Tanmay Inamdar
2014-09-26 21:08 ` [PATCH v10 4/4] MAINTAINERS: entry for APM X-Gene PCIe host driver Tanmay Inamdar
2014-10-01 19:14 ` [PATCH v10 0/4] APM X-Gene PCIe host controller Bjorn Helgaas
2014-10-02 12:20 ` Arnd Bergmann [this message]
2014-10-02 14:36 ` Bjorn Helgaas
2014-10-02 19:24 ` 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=2135522.DVGa59N1mx@wuerfel \
--to=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=jgunthorpe@obsidianresearch.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=liviu.dudau@arm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox