From: jchandra@broadcom.com (Jayachandran C.)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] PCI: generic: remove dependency on hw_pci
Date: Tue, 12 May 2015 05:37:47 +0530 [thread overview]
Message-ID: <20150512000746.GA31418@jayachandranc.netlogicmicro.com> (raw)
In-Reply-To: <20150505155346.GJ1550@arm.com>
On Tue, May 05, 2015 at 04:53:46PM +0100, Will Deacon wrote:
> On Tue, May 05, 2015 at 03:02:12AM +0100, Jayachandran C wrote:
> > The current code in pci-host-generic.c uses pci_common_init_dev()
> > from the arch/arm/ to do a part of the PCI initialization, and this
> > prevents it from being used on arm64.
> >
> > The initialization done by pci_common_init_dev() that is really
> > needed by pci-host-generic.c can be done in the same file without
> > using the hw_pci API of ARM.
> >
> > The ARM platform requires a pci_sys_data as sysdata for the PCI bus,
> > this is be handled by setting up 'struct gen_pci' to embed a
> > pci_sys_data variable as the first element on the ARM platform.
> >
> > Signed-off-by: Jayachandran C <jchandra@broadcom.com>
> > ---
> > Here's v2 of the patches, this enables use of pci-host-generic on
> > arm64.
> >
> > This has been tested on both qemu and fast model for arm64, and on
> > qemu for arm32.
> >
> > v1->v2
> > - Address comments from Arnd Bergmann and Lorenzo Pieralisi
> > - move contents of gen_pci_init to gen_pci_probe
> > - assign resources only when !probe_only
> > - tested on ARM32 with qemu option -M virt
>
> I tried this with an arm64 kernel running under kvmtool, but I get the
> following errors (a 32-bit ARM kernel does seem to work):
>
> PCI host bridge /pci ranges:
> IO 0x00000000..0x0000ffff -> 0x00000000
> MEM 0x41000000..0x7fffffff -> 0x41000000
> pci-host-generic 40000000.pci: PCI host bridge to bus 0000:00
> pci_bus 0000:00: root bus resource [bus 00-01]
> pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
> pci_bus 0000:00: root bus resource [mem 0x41000000-0x7fffffff]
> pci_bus 0000:00: scanning bus
> pci 0000:00:00.0: [1af4:1009] type 00 class 0xff0000
> pci 0000:00:00.0: reg 0x10: [mem 0x41000000-0x410003ff]
> pci 0000:00:00.0: reg 0x14: [io 0x6200-0x65ff]
> pci 0000:00:00.0: reg 0x18: [mem 0x41000400-0x410005ff]
> pci 0000:00:01.0: [1af4:1009] type 00 class 0xff0000
> pci 0000:00:01.0: reg 0x10: [mem 0x41000800-0x41000bff]
> pci 0000:00:01.0: reg 0x14: [io 0x6600-0x69ff]
> pci 0000:00:01.0: reg 0x18: [mem 0x41000c00-0x41000dff]
> pci_bus 0000:00: fixups for bus
> pci_bus 0000:00: bus scan returning with max=00
> pci 0000:00:00.0: fixup irq: got 10
> pci 0000:00:00.0: assigning IRQ 10
> pci 0000:00:01.0: fixup irq: got 11
> pci 0000:00:01.0: assigning IRQ 11
> virtio-pci 0000:00:00.0: can't enable device: BAR 0 [mem 0x41000000-0x410003ff] not claimed
> virtio-pci: probe of 0000:00:00.0 failed with error -22
> virtio-pci 0000:00:01.0: can't enable device: BAR 0 [mem 0x41000800-0x41000bff] not claimed
> virtio-pci: probe of 0000:00:01.0 failed with error -22
PCI_PROBE_ONLY does not work yet for arm64, this will need further changes
in either arm64 or pci as noted by Lorenzo. This is not due to a problem with
this patch per se.
More importantly, this does not change the current arm32 behavior and adds
support for arm64 for two very useful cases
- we can use "pci-host-ecam-generic" for a host bridge controller that is
initialized by firmware, without adding a custom driver.
- qemu virt platform works on arm64
If you think there are any furhter changes needed in this patchset please
let me know.
Thanks,
JC.
next prev parent reply other threads:[~2015-05-12 0:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 2:02 [PATCH v2 1/2] PCI: generic: remove dependency on hw_pci Jayachandran C
2015-05-05 2:02 ` [PATCH v2 2/2] PCI: generic: add arm64 support Jayachandran C
2015-05-05 15:53 ` [PATCH v2 1/2] PCI: generic: remove dependency on hw_pci Will Deacon
2015-05-05 15:58 ` Arnd Bergmann
2015-05-05 16:03 ` Lorenzo Pieralisi
2015-05-06 14:18 ` Lorenzo Pieralisi
2015-05-06 15:18 ` Bjorn Helgaas
2015-05-07 3:32 ` Suravee Suthikulanit
2015-05-12 13:34 ` Bjorn Helgaas
2015-05-12 16:34 ` Lorenzo Pieralisi
2015-05-12 19:20 ` Bjorn Helgaas
2015-05-13 12:47 ` Suravee Suthikulanit
2015-05-13 13:54 ` Bjorn Helgaas
2015-05-13 15:05 ` Suravee Suthikulanit
2015-05-13 15:11 ` Bjorn Helgaas
2015-05-12 0:07 ` Jayachandran C. [this message]
2015-05-19 23:09 ` Bjorn Helgaas
2015-05-20 17:29 ` Will Deacon
2015-05-20 20:46 ` Bjorn Helgaas
2015-05-21 6:37 ` Jayachandran C.
2015-05-26 9:59 ` Will Deacon
2015-05-26 10:38 ` 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=20150512000746.GA31418@jayachandranc.netlogicmicro.com \
--to=jchandra@broadcom.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).