From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4 v3] PCI: add DT bindings for Faraday Technology PCI Host Bridge
Date: Thu, 2 Mar 2017 10:31:26 -0600 [thread overview]
Message-ID: <20170302163126.imrelpsfzeucfy3r@rob-hp-laptop> (raw)
In-Reply-To: <20170227190720.31409-1-linus.walleij@linaro.org>
On Mon, Feb 27, 2017 at 08:07:17PM +0100, Linus Walleij wrote:
> This adds device tree bindings for the Faraday technology PCI
> Host Bridge. This IP is found in the Storlink/Storm/Cortina
> Gemini SoC platform.
>
> Cc: Janos Laube <janos.dev@gmail.com>
> Cc: Paulius Zaleckas <paulius.zaleckas@gmail.com>
> Cc: Hans Ulli Kroll <ulli.kroll@googlemail.com>
> Cc: Florian Fainelli <f.fainelli@gmail.com>
> Cc: devicetree at vger.kernel.org
> Cc: Feng-Hsin Chiang <john453@faraday-tech.com>
> Cc: Greentime Hu <green.hu@gmail.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v2->v3:
> - Reinstate the specific-to-generic bindings also specifying the
> "cortina,gemini-pci" fixture for the Faraday block.
> - Set compatible to "faraday,ftpci100" and "faraday,ftpci100-dual"
> this is clearly closer to or equal to what the IP blocks from
> Faraday are actually named.
> - Add "dma-ranges" property, after deciphering that some hardcoded
> constants in the driver is really about this.
> ChangeLog v1->v2:
> - Rename from Cortina prefixes to Faraday. This is clearly
> a Faraday IP block.
> - Support both the version with cascaded interrupts and the
> "dual" version with 1-to-1 mapped interrupts.
> - Change bus-range to <0x00 0xff>
> - Fix spelling mistake
> - Write a bit about swizzling interrupts on the interrupt
> controller side
> - Reasonable swizzling in the interrupt mapping example
>
> This can be merged to the PCI tree whenever it is considered
> fine for inclusion.
> ---
> .../devicetree/bindings/pci/faraday,ftpci100.txt | 129 +++++++++++++++++++++
> 1 file changed, 129 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/pci/faraday,ftpci100.txt
Acked-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2017-03-02 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 19:07 [PATCH 1/4 v3] PCI: add DT bindings for Faraday Technology PCI Host Bridge Linus Walleij
2017-02-27 19:07 ` [PATCH 2/4 v3] PCI: add driver for Faraday Technology " Linus Walleij
2017-02-27 19:07 ` [PATCH 3/4 v3] ARM: gemini: select MIGHT_HAVE_PCI Linus Walleij
2017-03-02 16:29 ` Rob Herring
2017-03-02 23:31 ` Linus Walleij
2017-02-27 19:07 ` [PATCH 4/4 v3] ARM: dts: add PCI to the Gemini device trees Linus Walleij
2017-03-02 16:31 ` Rob Herring [this message]
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=20170302163126.imrelpsfzeucfy3r@rob-hp-laptop \
--to=robh@kernel.org \
--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