[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.58.0811280145290.24816@shell4.speakeasy.net>
Date: Fri, 28 Nov 2008 01:51:04 -0800 (PST)
From: Trent Piepho <xyzzy@...akeasy.org>
To: "Darrick J. Wong" <djwong@...ibm.com>
cc: Alex Chiang <achiang@...com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
linux-pci <linux-pci@...r.kernel.org>
Subject: Re: [PATCH] fakephp: Allocate PCI resources before adding the device
On Wed, 26 Nov 2008, Darrick J. Wong wrote:
> On Wed, Nov 26, 2008 at 03:55:35PM -0700, Alex Chiang wrote:
> > > Maybe it's different on powerpc then? My pseudo-hotplugable device is also
> > > the only thing connected to the PCI-E host bus controller. At boot the
> > > controller is empty and so I think some code to enable its BARs gets
> > > skipped. But without the pci_enable_device(), I get this:
> > >
> > > 01:00.0 Signal processing controller: Freescale Semiconductor Inc Aurora Nexus Trace Interface
> > > Flags: fast devsel, IRQ 255
> > > Memory at 40000000 (64-bit, prefetchable) [disabled] [size=4K]
> Are you referring to this? ^^^^^^^^^^
>
> Without seeing the raw dump of the PCI config space, it looks to me like
> the memory space enable bit of the PCICMD register is unset. Probably
> the device driver should call pci_enable_device() at init time, though I
> suppose you did say earlier that there is no driver.
Yes, that's it. It seems like since the BARs are normally enabled after a
device is scanned at boot time that they should also be enabled when a
device is found by a fakephp rescan. So I thought it seemed reasonable to
put pci_enable_device() in fakephp.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists