From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: RFC: [PATCH 1/3] Enhance platform support for PCI Date: Fri, 20 Feb 2015 13:37:21 +0000 Message-ID: <1424439441.30924.235.camel@citrix.com> References: <54E71BDE.5020106@caviumnetworks.com> <54E7229C.7000301@linaro.org> <54E72452.3090801@caviumnetworks.com> <54E72688.9010005@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54E72688.9010005@linaro.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Julien Grall Cc: Prasun.kapoor@cavium.com, "Kumar, Vijaya" , xen-devel@lists.xen.org, "Stefano Stabellini (Stefano.Stabellini@citrix.com)" , Manish Jaggi List-Id: xen-devel@lists.xenproject.org On Fri, 2015-02-20 at 12:20 +0000, Julien Grall wrote: > Overall, I would prefer to have a separate file and structure for > handling PCI host. Also, I think we could re-use the Linux code for this > purpose. (caveat; I've not looked at the code yet) I had expected that PCI host controllers would be discovered via the existing device model stuff and compatible string matching, e.g. DT_DEVICE_START(some_pcihost, "SOME PCI HOST CONTROLLER", DEVICE_PCIBUS) which would reference a set of compatible strings and a probe function, the probe function would then call some pci bus registration function to hook that bus into the system. Ian.