[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1470431358.25630.249.camel@buserror.net>
Date: Fri, 05 Aug 2016 16:09:18 -0500
From: Scott Wood <oss@...error.net>
To: york sun <york.sun@....com>, Michael Ellerman <mpe@...erman.id.au>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>
Cc: "morbidrsa@...il.com" <morbidrsa@...il.com>,
Stuart Yoder <stuart.yoder@....com>,
"bp@...en8.de" <bp@...en8.de>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
Kevin Hao <haokexin@...il.com>,
Andrew Donnellan <andrew.donnellan@....ibm.com>,
Yinghai Lu <yinghai@...nel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [Patch v3 01/11] arch/powerpc/pci: Fix compiling error for
mpc85xx_edac
On Fri, 2016-08-05 at 20:29 +0000, york sun wrote:
> On 08/04/2016 08:43 PM, Michael Ellerman wrote:
> >
> > Does the driver really need to use these routines? They're meant for use
> > early in boot, before PCI is setup.
> >
> > AFAICS this is just a regular driver, so when it's probed the PCI
> > devices should have already been scanned. In which case pci_get_device()
> > could work couldn't it? (I see other edac drivers doing that).
> I am trying to fix this but need some help. We are dealing with PCIe
> controller here. Does it have a bus number assigned at this point? If
> yes, how can I find it? I seem not able to find out where the
> platform_data is filled as well. Can someone kindly point it out to me?
The platform data comes from add_err_dev() in arch/powerpc/sysdev/fsl_pci.c.
-Scott
Powered by blists - more mailing lists