From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 8610BB7C8E for ; Tue, 26 Jan 2010 13:59:58 +1100 (EST) Subject: Re: [RFC PATCH] PCI-E broken on PPC (regression) From: Benjamin Herrenschmidt To: Jesse Barnes In-Reply-To: <20100125175025.4c74f412@jbarnes-piketon> References: <4B5D9FC5.5070600@linux.vnet.ibm.com> <20100125123849.111fa2d1@jbarnes-piketon> <20100125175025.4c74f412@jbarnes-piketon> Content-Type: text/plain; charset="UTF-8" Date: Tue, 26 Jan 2010 13:59:31 +1100 Message-ID: <1264474771.3601.110.camel@pasglop> Mime-Version: 1.0 Cc: Linux PCI , Jay Vosburgh , Ron Mercer , kaneshige.kenji@jp.fujitsu.com, linuxppc-dev@lists.ozlabs.org, Breno Leitao List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 2010-01-25 at 17:50 -0800, Jesse Barnes wrote: > > You mean dev->is_pcie? > > > > Why isn't pci_scan_device calling pci_setup_device for you? That > > should do the proper PCIe init depending on the device, along with > > extracting other device info... > > Cc'ing Ben for PPC. Ben, should PPC use pci_scan_device when probing > its root busses? Sounds like it just uses pci_device_add for each one > it finds instead? > > If you don't actually need scanning (though what about hotplug?) we can > move the call to device_add instead... I need to give it more brain cells than I have available today :-) I'll have a look tomorrow. In some case we build the PCI stuff up from the firmware device-tree without actually doing any config space scanning, so the root busses are treated a bit special. Cheers, Ben.