From: Will Deacon <will.deacon@arm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>
Subject: Re: [PATCH v3 3/3] PCI: ARM: add support for generic PCI host controller
Date: Tue, 18 Feb 2014 19:36:54 +0000 [thread overview]
Message-ID: <20140218193654.GK2010@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1411925.bMiMyFpUnW@wuerfel>
On Tue, Feb 18, 2014 at 07:32:33PM +0000, Arnd Bergmann wrote:
> On Tuesday 18 February 2014 19:09:29 Will Deacon wrote:
> >
> > > Regarding the 0x6200.. There are two conflicting issues there
> > > - You really don't want to let the PCI core assign resources to that
> > > range, it probably won't work.
> >
> > Right, with kvmtool we don't support resource assignment (the BARs are fixed)
> > so everything is PCI_PROBE_ONLY.
>
> Ok, I looked at the source now and can confirm:
>
> * 0x0-0x1000 are used for lots of legacy ISA devices.
> * PCI devices get assigned IO addresses in 0x400 steps starting at 0x6200.
> * There are three PCI drivers doing this: VESA, PCI-SHMEM and virtio-pci.
>
> Regarding the PCI_PROBE_ONLY flag, how do you set that? Should we
> have a standard DT property for that? On PowerPC we already specified
> "linux,pci-probe-only" and "linux,pci-assign-all-buses", which seems
> reasonable to use in architecture independent code as well.
For arch/arm/ it's done on the command line (pci=firmware) but yes, for the
generic driver it sounds like a good idea to put this in the device-tree.
I'll look at adding the ppc properties in the next version.
Cheers,
Will
next prev parent reply other threads:[~2014-02-18 19:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 12:20 [PATCH v3 0/3] ARM: PCI: implement generic PCI host controller Will Deacon
2014-02-18 12:20 ` [PATCH v3 1/3] ARM: mach-virt: allow PCI support to be selected Will Deacon
2014-02-18 12:20 ` [PATCH v3 2/3] ARM: bios32: use pci_enable_resource to enable PCI resources Will Deacon
2014-02-18 15:41 ` Russell King - ARM Linux
2014-02-18 19:10 ` Will Deacon
2014-02-20 11:12 ` Will Deacon
2014-02-20 19:39 ` Bjorn Helgaas
2014-02-21 0:36 ` Jason Gunthorpe
2014-02-21 13:49 ` Will Deacon
2014-02-18 12:20 ` [PATCH v3 3/3] PCI: ARM: add support for generic PCI host controller Will Deacon
2014-02-18 13:46 ` Arnd Bergmann
2014-02-18 19:10 ` Will Deacon
2014-02-19 11:07 ` Will Deacon
2014-02-19 14:17 ` Arnd Bergmann
2014-02-19 15:25 ` Will Deacon
2014-02-18 18:21 ` Jason Gunthorpe
2014-02-18 18:44 ` Will Deacon
2014-02-18 18:47 ` Arnd Bergmann
2014-02-18 18:51 ` Will Deacon
2014-02-18 19:11 ` Arnd Bergmann
2014-02-18 19:16 ` Will Deacon
2014-02-18 18:59 ` Jason Gunthorpe
2014-02-18 19:09 ` Will Deacon
2014-02-18 19:32 ` Arnd Bergmann
2014-02-18 19:36 ` Will Deacon [this message]
2014-02-18 19:57 ` Will Deacon
2014-02-18 20:19 ` Arnd Bergmann
2014-02-19 10:57 ` Will Deacon
2014-02-18 20:15 ` Arnd Bergmann
2014-02-19 10:54 ` Will Deacon
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=20140218193654.GK2010@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.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).