mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tomas Winkler" <tomasw@gmail.com>
To: "Pierre Ossman" <drzeus@drzeus.cx>
Cc: linux-kernel@vger.kernel.org, benzizbit@gmail.com
Subject: Re: SDIO: IO-Ready Bit
Date: Mon, 24 Mar 2008 16:41:25 +0200	[thread overview]
Message-ID: <1ba2fa240803240741n5bf042c2j4aaa4d2f70cf8ef@mail.gmail.com> (raw)
In-Reply-To: <20080324145352.6262788b@mjolnir.drzeus.cx>

On Mon, Mar 24, 2008 at 3:53 PM, Pierre Ossman <drzeus@drzeus.cx> wrote:
> On Sun, 23 Mar 2008 00:10:19 +0200
>
> "Tomas Winkler" <tomasw@gmail.com> wrote:
>
>  >
>
> > I couldn't find anything that can prevent the probe function to be
>  > called in case the module is already loaded. I've looked at udev and
>  > HAL and no much I found.
>  > I will dig into kernel sources, maybe finding out how can be bus
>  > enumeration triggered again or something like this.
>  > Any pointers will be appreciated.
>  >
>
>  Here's the patch that added the functionality:
>
>  http://lkml.org/lkml/2007/4/27/466


Thanks a lot. I will look at this and how it can be used.

Anyhow I've seen that concept of parallel probe is not so new. It was
in 2.6.18 and removed in 2.619.
Probably different approach, maybe more would be adding a parallel
initial function.
Probe will just register to the bus and relevant subsystem, it will be fast.
Optional Initialization function will run after probe in different
thread, this would be the place for running FW download.
Device won't be considered initialized till this function haven't
completed or is not implemented.


Any comments are welcome.

Thanks
Tomas



>  Rgds
>  Pierre
>

  reply	other threads:[~2008-03-24 14:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18 11:00 Tomas Winkler
2008-03-18 11:33 ` Pierre Ossman
2008-03-18 17:43   ` Tomas Winkler
2008-03-18 18:20     ` Pierre Ossman
2008-03-22 22:10       ` Tomas Winkler
2008-03-24 13:53         ` Pierre Ossman
2008-03-24 14:41           ` Tomas Winkler [this message]
2008-03-29  8:04             ` Pierre Ossman

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=1ba2fa240803240741n5bf042c2j4aaa4d2f70cf8ef@mail.gmail.com \
    --to=tomasw@gmail.com \
    --cc=benzizbit@gmail.com \
    --cc=drzeus@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

all inboxes | Powered by JetHome®