From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"Liviu.Dudau@arm.com" <Liviu.Dudau@arm.com>,
nofooter <nofooter@xilinx.com>,
"thomas.petazzoni@free-electrons.com"
<thomas.petazzoni@free-electrons.com>
Subject: Re: Purpose of pci_remap_iospace
Date: Thu, 14 Jul 2016 16:27:14 +0100 [thread overview]
Message-ID: <20160714152714.GD30657@red-moon> (raw)
In-Reply-To: <5073702.5KYvV2f0PW@wuerfel>
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
next prev parent reply other threads:[~2016-07-14 15:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 6:57 Purpose of pci_remap_iospace Bharat Kumar Gogada
2016-07-12 8:31 ` Arnd Bergmann
2016-07-12 8:40 ` Bharat Kumar Gogada
2016-07-13 8:11 ` Bharat Kumar Gogada
2016-07-13 8:30 ` Arnd Bergmann
2016-07-13 12:30 ` Bharat Kumar Gogada
2016-07-13 13:28 ` Arnd Bergmann
2016-07-13 15:16 ` Bharat Kumar Gogada
2016-07-13 15:28 ` Arnd Bergmann
2016-07-13 15:42 ` Liviu.Dudau
2016-07-13 16:13 ` Lorenzo Pieralisi
2016-07-13 13:46 ` Lorenzo Pieralisi
2016-07-14 6:03 ` Bharat Kumar Gogada
2016-07-14 13:32 ` Bharat Kumar Gogada
2016-07-14 14:56 ` Lorenzo Pieralisi
2016-07-14 15:05 ` Bharat Kumar Gogada
2016-07-14 15:20 ` Lorenzo Pieralisi
2016-07-14 15:12 ` Arnd Bergmann
2016-07-14 15:27 ` Lorenzo Pieralisi [this message]
2016-07-15 5:21 ` Bharat Kumar Gogada
2016-07-15 6:55 ` Arnd Bergmann
2016-07-13 13:24 ` Liviu.Dudau
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=20160714152714.GD30657@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=Liviu.Dudau@arm.com \
--cc=arnd@arndb.de \
--cc=bharat.kumar.gogada@xilinx.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nofooter@xilinx.com \
--cc=thomas.petazzoni@free-electrons.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).