public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: pci: add to global list before sysfs?
Date: Sat, 5 Apr 2008 08:53:23 -0700	[thread overview]
Message-ID: <20080405155323.GA27252@suse.de> (raw)
In-Reply-To: <20080405115727.1265e8a9@mjolnir.drzeus.cx>

On Sat, Apr 05, 2008 at 11:57:27AM +0200, Pierre Ossman wrote:
> On Fri, 4 Apr 2008 14:01:32 -0700
> Greg KH <gregkh@suse.de> wrote:
> 
> > 
> > What "global list"?  You mean the one that I just deleted with my
> > patchset that is in -mm and going to be in 2.6.26?  :)
> > 
> 
> *gnn*

Well the "global list" was not being used for anything, and it was being
created at the same time the driver core list was, so unless you wanted
to change the way that all pci devices were probed/created, it would not
have worked out.

> > How will changing the addition of the device to the list affect this
> > behavior?  Do you want to walk the list in your driver's probe function,
> > looking for the "subfunction" that is not yet added to the list?
> > 
> 
> Yes. Things work fine when the driver is loaded after the entire PCI
> bus has been scanned, but not when new cards are hotplugged with the
> driver already present. I'd like the behaviour to be the same in both
> cases.

Why not just create a thread in your driver, or timer, and sleep until
you see the other devices?  If after a certian time you never do, then
bail out.

That should work properly for you for both cases (startup and loading
later.)

thanks,

greg k-h

  reply	other threads:[~2008-04-05 15:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04 17:13 pci: add to global list before sysfs? Pierre Ossman
2008-04-04 21:01 ` Greg KH
2008-04-05  9:57   ` Pierre Ossman
2008-04-05 15:53     ` Greg KH [this message]
2008-04-05 16:55       ` Pierre Ossman
2008-04-05 17:12         ` Greg KH
2008-04-05 18:27           ` Pierre Ossman
2008-04-08  3:41             ` Greg KH
2008-04-13 12:33               ` Pierre Ossman
2008-04-13 17:51                 ` Greg KH
2008-04-13 21:37         ` Benjamin Herrenschmidt
2008-04-14  8:35           ` Pierre Ossman
2008-04-14  8:57             ` Benjamin Herrenschmidt
2008-04-14  8:58             ` Benjamin Herrenschmidt
2008-04-14 10:58               ` Pierre Ossman
2008-04-13 21:35   ` Benjamin Herrenschmidt
2008-04-15 19:13     ` Greg KH
2008-04-15 21:53       ` Benjamin Herrenschmidt

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=20080405155323.GA27252@suse.de \
    --to=gregkh@suse.de \
    --cc=drzeus-list@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    /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