From: Rajesh Shah <rajesh.shah@intel.com>
To: Christoph Hellwig <hch@infradead.org>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
Greg KH <greg@kroah.com>,
akpm@osdl.org, Rajesh Shah <rajesh.shah@intel.com>,
Grant Grundler <grundler@parisc-linux.org>,
"bibo,mao" <bibo.mao@intel.com>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH 4/4] Make Emulex lpfc driver legacy I/O port free
Date: Wed, 7 Jun 2006 10:26:37 -0700 [thread overview]
Message-ID: <20060607102637.A25175@unix-os.sc.intel.com> (raw)
In-Reply-To: <20060607145203.GA13951@infradead.org>; from hch@infradead.org on Wed, Jun 07, 2006 at 03:52:03PM +0100
On Wed, Jun 07, 2006 at 03:52:03PM +0100, Christoph Hellwig wrote:
> On Wed, Jun 07, 2006 at 10:56:07PM +0900, Kenji Kaneshige wrote:
> > Christoph Hellwig wrote:
> > >On Wed, Jun 07, 2006 at 10:11:12PM +0900, Kenji Kaneshige wrote:
> > >
> > >>I mean the right order is
> > >>
> > >> (1) pci_request_regions()
> > >> (2) pci_enable_device*()
> > >
> > >
> > >no, pci_enable_device should be first.
> > >
> > >
> >
> > I had the same wrong assumption before. But to prevent two
> > devices colliding on the same address range, pci_request_regions()
> > should be called first. Please see the following discussions:
>
> No. That's what the pci_driver matching is for. Without pci_enable_device
> pci_request_regions could do the wrong thing when fixups aren't run.
I don't see how driver matching will help here. It seems wrong to
enable a device first, and then check if the resources it is
decoding actually conflict with some other device's resources.
Regarding quirks, all the ones that mess around with resources
are marked as HEADER quirks. So they should be called right
after a device is probed and before its driver can call
pci_request_regions(). What problems do you see if regions are
requested before the device is enabled?
Rajesh
next prev parent reply other threads:[~2006-06-07 17:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 7:05 [BUG](-mm)pci_disable_device function clear bars_enabled element bibo,mao
2006-06-01 9:46 ` Rajesh Shah
2006-06-01 17:15 ` Grant Grundler
2006-06-01 18:36 ` Rajesh Shah
2006-06-02 2:57 ` Kenji Kaneshige
2006-06-02 5:56 ` Grant Grundler
2006-06-02 7:31 ` Kenji Kaneshige
2006-06-03 23:21 ` Grant Grundler
2006-06-04 21:01 ` Greg KH
2006-06-05 12:40 ` [BUG][PATCH 2.6.17-rc5-mm3] bugfix: PCI legacy I/O port free driver Kenji Kaneshige
2006-06-06 7:58 ` Greg KH
2006-06-06 8:17 ` Kenji Kaneshige
2006-06-07 3:10 ` Kenji Kaneshige
2006-06-07 3:12 ` [PATCH 1/4] Changes to generic pci code Kenji Kaneshige
2006-06-07 3:13 ` [PATCH 2/4] Update Documentation/pci.txt Kenji Kaneshige
2006-06-07 3:14 ` [PATCH 3/4] Make Intel e1000 driver legacy I/O port free Kenji Kaneshige
2006-06-07 5:10 ` Auke Kok
2006-06-07 7:39 ` Kenji Kaneshige
2006-06-07 14:40 ` Auke Kok
2006-06-08 12:31 ` Jeff Garzik
2006-06-08 13:35 ` Kenji Kaneshige
2006-06-08 14:46 ` Jeff Garzik
2006-06-08 17:00 ` Kenji Kaneshige
2006-06-07 3:15 ` [PATCH 4/4] Make Emulex lpfc " Kenji Kaneshige
2006-06-07 8:24 ` Christoph Hellwig
2006-06-07 12:23 ` Kenji Kaneshige
2006-06-07 12:43 ` Christoph Hellwig
2006-06-07 13:11 ` Kenji Kaneshige
2006-06-07 13:40 ` Christoph Hellwig
2006-06-07 13:56 ` Kenji Kaneshige
2006-06-07 14:52 ` Christoph Hellwig
2006-06-07 17:26 ` Rajesh Shah [this message]
2006-06-02 4:42 ` [BUG](-mm)pci_disable_device function clear bars_enabled element Grant Grundler
2006-06-02 16:50 ` Rajesh Shah
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=20060607102637.A25175@unix-os.sc.intel.com \
--to=rajesh.shah@intel.com \
--cc=akpm@osdl.org \
--cc=bibo.mao@intel.com \
--cc=greg@kroah.com \
--cc=grundler@parisc-linux.org \
--cc=hch@infradead.org \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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