public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
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-pci@vger.kernel.org>,
	"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] PCI: rcar: Add support for ARM64 and multiple instances
Date: Thu, 29 Oct 2015 19:48:00 +0100	[thread overview]
Message-ID: <20151029184800.GB8992@katana> (raw)
In-Reply-To: <PS1PR06MB11804B39B09D6FCAA9B3D9DCF5200@PS1PR06MB1180.apcprd06.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]

On Thu, Oct 29, 2015 at 04:44:06PM +0000, Phil Edworthy wrote:
> Hi Wolfram,
> 
> On 29 October 2015 16:40, Wolfram wrote:
> > > Ouch, my bad. I have been working with our out-of-tree BSP for the Salvator-X
> > board on
> > > http://git.kernel.org/cgit/linux/kernel/git/horms/renesas-bsp.git,  rcar-3.0.2
> > tag along
> > > with some patches from colleagues. I hadn't noticed this patch:
> > 
> > Thanks! Any plans for pushing this upstream? We will have the build error
> > otherwise...
> After some digging, that patch won't be accepted upstream. I'm looking into how the
> driver can be modified so it doesn't need to call this, but I don't expect a small or
> imminent fix.

Yes, I'd think so, too. However, a fix for 4.4 would be needed to
prevent having a final release with a build error.

> > > > Any news if this is really HW related?
> > > I found out that the PCIe controller HW only supports 32-bit AXI bus addresses,
> > so it
> > > works fine if you limit the available memory. The driver will need some work to
> > use
> > > the IPMMU at some point.
> > 
> > Ah, okay.
> > 
> > Can you send the dts patches, too? I checked the BSP this time, but to
> > no avail...
> I will once I sort out the arm64 IO resources problem and the MSI problem.

What MSI problem?

And can't you send the DTS patches as RFC so I can add some testing?


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-10-29 18:48 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 ` [PATCH 0/4] PCI: rcar: Add support for ARM64 and " Bjorn Helgaas
2015-10-19  0:24   ` 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 [this message]
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=20151029184800.GB8992@katana \
    --to=wsa@the-dreams.de \
    --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