[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160714152714.GD30657@red-moon>
Date: Thu, 14 Jul 2016 16:27:14 +0100
From: Lorenzo Pieralisi <lorenzo.pieralisi@....com>
To: Arnd Bergmann <arnd@...db.de>
Cc: Bharat Kumar Gogada <bharat.kumar.gogada@...inx.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
"Liviu.Dudau@....com" <Liviu.Dudau@....com>,
nofooter <nofooter@...inx.com>,
"thomas.petazzoni@...e-electrons.com"
<thomas.petazzoni@...e-electrons.com>
Subject: Re: Purpose of pci_remap_iospace
On Thu, Jul 14, 2016 at 05:12:01PM +0200, Arnd Bergmann wrote:
> On Thursday, July 14, 2016 3:56:24 PM CEST Lorenzo Pieralisi wrote:
> > On Thu, Jul 14, 2016 at 01:32:13PM +0000, Bharat Kumar Gogada wrote:
> >
> > [...]
> >
> > > Hi Lorenzo,
> > >
> > > I missed something in my device tree now I corrected it.
> > >
> > > ranges = <0x01000000 0x00000000 0xe0000000 0x00000000 0xe0000000 0 0x00010000 //io
> >
> > You have not missed anything, you changed the PCI bus address at
> > which your host bridge responds to IO space and it must match
> > your configuration.
>
> I'd always recommend mapping the I/O space to PCI address zero, but
> evidently the hardware is not configured that way here.
+1 and it is a message that must be heeded by Xiling folks before
merging the host controller changes and respective DT bindings/dts.
Lorenzo
Powered by blists - more mailing lists