From: Bjorn Helgaas <helgaas@kernel.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Murali Karicheri <m-karicheri2@ti.com>,
Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: PCI IO resource question.
Date: Wed, 16 Mar 2016 14:32:24 -0500 [thread overview]
Message-ID: <20160316193224.GB2703@localhost> (raw)
In-Reply-To: <20160316180936.GA7605@red-moon>
On Wed, Mar 16, 2016 at 06:09:36PM +0000, Lorenzo Pieralisi wrote:
> On Wed, Mar 16, 2016 at 12:20:08PM -0400, Murali Karicheri wrote:
> > [ 0.420648] PCI host bridge /soc/pcie@21020000 ranges:
> > [ 0.420659] No bus range found for /soc/pcie@21020000, using [bus 00-ff]
> > [ 0.420679] IO 0x23260000..0x400023263fff -> 0x00000000
> > [ 0.420685] Requested IO range too big, new size set to 64K
> > [ 0.420702] MEM 0x60000000..0x6fffffff -> 0x60000000
> > [ 0.420713] keystone-pcie 21021000.pcie: error -22: failed to map resource [io 0x0000-0x400000003fff]
>
> This unearthed an issue that we've got to fix. If the IO space remap
> fails (pci_remap_iospace()) we must remove the IO resource from the host
> bridge resources list, code below shows that we end up assigning IO space
> even if the remapping of the host bridge CPU physical address corresponding
> to IO space fails, which is wrong.
>
> Do you want me to fix the host bridges concerned in one go ?
Yes, that looks like a real problem we should fix.
Bjorn
next prev parent reply other threads:[~2016-03-16 19:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 16:20 PCI IO resource question Murali Karicheri
2016-03-16 16:45 ` Bjorn Helgaas
2016-03-16 18:08 ` Murali Karicheri
2016-03-16 19:29 ` Bjorn Helgaas
2016-03-16 20:13 ` Murali Karicheri
2016-03-16 21:47 ` Bjorn Helgaas
2016-03-17 17:11 ` Murali Karicheri
2016-03-17 21:28 ` Murali Karicheri
2016-03-18 11:28 ` Lorenzo Pieralisi
2016-03-18 14:13 ` Bjorn Helgaas
2016-03-18 15:09 ` Murali Karicheri
2016-03-18 15:25 ` Murali Karicheri
2016-03-18 15:28 ` Bjorn Helgaas
2016-03-18 18:12 ` Murali Karicheri
2016-03-18 19:34 ` Bjorn Helgaas
2016-03-18 19:51 ` Murali Karicheri
2016-03-18 23:05 ` Lorenzo Pieralisi
2016-03-21 15:24 ` Murali Karicheri
2016-03-21 18:02 ` Lorenzo Pieralisi
2016-03-22 19:41 ` Murali Karicheri
2016-03-23 22:02 ` Lorenzo Pieralisi
2016-03-16 18:09 ` Lorenzo Pieralisi
2016-03-16 19:32 ` Bjorn Helgaas [this message]
2016-03-16 20:33 ` Murali Karicheri
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=20160316193224.GB2703@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=m-karicheri2@ti.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).