From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM:Orion5x: Fix panic at boot for PCI IO reservation
Date: Mon, 18 Jun 2012 09:39:33 -0500 [thread overview]
Message-ID: <4FDF3DA5.4030602@gmail.com> (raw)
In-Reply-To: <20120618141901.GQ4799@lunn.ch>
On 06/18/2012 09:19 AM, Andrew Lunn wrote:
> On Mon, Jun 18, 2012 at 10:06:34AM +0200, Andrew Lunn wrote:
>> Orion5x, and all other orion based systems have a PCI(E) IO window
>> size of 1Mbyte. Recent changes to mach/io.h mean that by default the
>> kernel does not allow such large windows, it refuses to reserve that
>> much resource space, triggering a panic.
>>
>> Reduce the PCI(E) IO window size to the normal 64K.
>
> It turns out this patch does not work...
>
> There are two PCI devices on Orion5x. So the first one takes all the
> available 64K IO space and the second one fails it allocation.
>
> We need to put back parts of mach/io.h to increase the available size to
> 128Kbytes.
>
> It has been said in another email, the plan is to put the IO window at
> one fixed address. How will this work for devices with multiple PCI
> busses? Most Orion chips for have two separate PCI busses.
It supports up to 16 64K windows mapped into a 1MB area. So
IO_RESOURCE_LIMIT will be 1MB in that case.
If the h/w can support i/o at 0, then it would be good make __io(x) be
the form of ((x) + <host phys base>). Unfortunately, it seems the only
way to figure this out is change it and see if it breaks people which
isn't very nice.
Rob
prev parent reply other threads:[~2012-06-18 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 8:06 [PATCH] ARM:Orion5x: Fix panic at boot for PCI IO reservation Andrew Lunn
2012-06-18 14:19 ` Andrew Lunn
2012-06-18 14:39 ` Rob Herring [this message]
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=4FDF3DA5.4030602@gmail.com \
--to=robherring2@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).