From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] io.h clean-up for PCI
Date: Mon, 30 Jul 2012 09:56:56 -0500 [thread overview]
Message-ID: <5016A0B8.5010607@gmail.com> (raw)
In-Reply-To: <20120730143119.GN6802@n2100.arm.linux.org.uk>
On 07/30/2012 09:31 AM, Russell King - ARM Linux wrote:
> On Mon, Jul 30, 2012 at 06:05:04AM -0500, Rob Herring wrote:
>> On 07/28/2012 09:38 AM, Will Deacon wrote:
>>> Hi Rob,
>>>
>>> On Fri, Jul 27, 2012 at 10:59:18PM +0100, Rob Herring wrote:
>>>> Please pull updated io.h cleanup for PCI branch. I rebased this as the
>>>> changes shifted things around a bit. This has the following changes:
>>>>
>>>> - Incorporated fixes from you and Stephen
>>>> - Add early i/o mapping pci_map_io_early and enable on footbridge and
>>>> integrator for VGA console
>>>
>>> Unfortunately, I still experience the same hang on integrator with this
>>> revised patch series. Given the turnaround time for testing this, I don't
>>> think this should block the series, but I would like to get to the bottom of
>>> it if possible.
>>>
>>> I tried annotating the PCI code (including fault handlers) and the VGA
>>> console code but I couldn't find the culprit. I suppose the next step is
>>> JTAG, but that requires steal^Wborrowing some hardware from work.
>>
>> I did do some tests with qemu by adding i/o setup to integrator/cp.
>> Without it, I would abort on 0xfee003xx (vga regs). Once I added the
>> setup, I got to an abort on a PCI memory address which I did not setup.
>>
>> We can always revert integrator change if we can figure this out...
>
> Err, Integrator/CP doesn't have PCI nor does it have VGA. Only the
> Integrator/AP has that.
Yes, I know. But there is no AP model within qemu. I added the mapping
to AP and enabled VGA console to do some basic checks that i/o accesses
happen. It didn't really have to be integrator platform at all for this
test. I know it's not much of a test, but it's something beyond
compiling and staring at the code.
I've also tested PCI i/o with versatile under qemu.
Rob
next prev parent reply other threads:[~2012-07-30 14:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 22:15 [GIT PULL] io.h clean-up for PCI Rob Herring
2012-07-17 20:53 ` Arnd Bergmann
2012-07-19 14:12 ` Arnd Bergmann
2012-07-24 12:33 ` Rob Herring
2012-07-24 12:43 ` Arnd Bergmann
2012-07-24 13:25 ` Rob Herring
2012-07-24 14:18 ` Arnd Bergmann
2012-07-25 14:41 ` Rob Herring
2012-07-25 15:52 ` Arnd Bergmann
2012-07-19 14:16 ` Arnd Bergmann
2012-07-23 0:35 ` Rob Herring
2012-07-27 21:59 ` Rob Herring
2012-07-28 14:38 ` Will Deacon
2012-07-30 11:05 ` Rob Herring
2012-07-30 14:31 ` Russell King - ARM Linux
2012-07-30 14:56 ` Rob Herring [this message]
2012-08-27 8:27 ` Russell King - ARM Linux
2012-08-28 0:14 ` Rob Herring
2012-07-29 23:07 ` Olof Johansson
2012-08-14 9:14 ` Will Deacon
2012-08-14 9:37 ` Arnd Bergmann
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=5016A0B8.5010607@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.