linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Phil Edworthy <phil.edworthy@renesas.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Simon Horman <horms@verge.net.au>,
	Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-pci@vger.kernel.org, linux-sh@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] PCI: rcar: Add support for ARM64 and multiple instances
Date: Fri, 16 Oct 2015 16:34:43 -0500	[thread overview]
Message-ID: <20151016213443.GD21346@localhost> (raw)
In-Reply-To: <1443781507-5011-1-git-send-email-phil.edworthy@renesas.com>

On Fri, Oct 02, 2015 at 11:25:03AM +0100, Phil Edworthy wrote:
> Fixes and changes to get PCIe working on ARM64 with mulitple instances.
> 
> I've tested these on ARM (Koelsch board), and it works fine.
> I've also tested on ARM64 (Salvator-X board), but I currently have an issue
> with inbound PCI accesses. I am reasonably sure that this problem is hardware
> related.
> 
> Phil Edworthy (4):
>   PCI: rcar-pcie: Make PCI aware of the IO resources
>   PCI: rcar-pcie: Remove dependency on ARM-specific struct hw_pci
>   PCI: rcar-pcie: Set root bus nr to that provided in DT
>   PCI: rcar-pcie: Fix IO offset for multiple instances

This all looks pretty reasonable to me, but I'm waiting for an ack from
Simon before merging it.

Bjorn

  parent reply	other threads:[~2015-10-16 21:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 10:25 [PATCH 0/4] PCI: rcar: Add support for ARM64 and multiple instances Phil Edworthy
2015-10-02 10:25 ` [PATCH 1/4] PCI: rcar-pcie: Make PCI aware of the IO resources Phil Edworthy
2015-10-02 10:25 ` [PATCH 2/4] PCI: rcar-pcie: Remove dependency on ARM-specific struct hw_pci Phil Edworthy
2015-10-16 21:34   ` Bjorn Helgaas
2015-10-19  8:54     ` Phil Edworthy
2015-10-02 10:25 ` [PATCH 3/4] PCI: rcar-pcie: Set root bus nr to that provided in DT Phil Edworthy
2015-10-02 10:25 ` [PATCH 4/4] PCI: rcar-pcie: Fix IO offset for multiple instances Phil Edworthy
2015-10-16 21:34 ` Bjorn Helgaas [this message]
2015-10-19  0:24   ` [PATCH 0/4] PCI: rcar: Add support for ARM64 and " Simon Horman
2015-10-19 23:16 ` Bjorn Helgaas
2015-10-20  1:36   ` Simon Horman
2015-10-20  7:37     ` Geert Uytterhoeven
2015-10-20  8:00       ` Phil Edworthy
2015-10-20 12:49         ` Bjorn Helgaas
2015-10-20 13:21           ` Phil Edworthy
2015-10-29 12:37 ` Wolfram Sang
2015-10-29 13:00   ` Phil Edworthy
2015-10-29 16:39     ` Wolfram Sang
2015-10-29 16:44       ` Phil Edworthy
2015-10-29 18:48         ` Wolfram Sang
2015-10-29 23:03           ` Bjorn Helgaas
2015-10-30  7:19             ` Phil Edworthy
2015-10-30  7:24               ` Phil Edworthy
2015-10-30  9:00               ` Phil Edworthy
2015-10-30 13:31                 ` Bjorn Helgaas
2015-11-02 10:56                   ` Phil Edworthy
2015-10-30 11:51           ` Phil Edworthy
2015-10-30 12:04             ` Wolfram Sang

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=20151016213443.GD21346@localhost \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=nobuhiro.iwamatsu.yj@renesas.com \
    --cc=phil.edworthy@renesas.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).