mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus@drzeus.cx>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: linux-kernel@vger.kernel.org, benzizbit@gmail.com
Subject: Re: SDIO: IO-Ready Bit
Date: Sat, 29 Mar 2008 09:04:34 +0100	[thread overview]
Message-ID: <20080329090434.7bfb7509@mjolnir.drzeus.cx> (raw)
In-Reply-To: <1ba2fa240803240741n5bf042c2j4aaa4d2f70cf8ef@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]

On Mon, 24 Mar 2008 16:41:25 +0200
"Tomas Winkler" <tomasw@gmail.com> wrote:

> 
> 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.
> 

I would suspect that would just slow things down in most cases. Most
busses have shared bandwidth, so letting each device take turns is
usually faster than a thundering herd.

Feel free to make your case to the device core maintainers though.

Rgds
Pierre

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2008-03-29  8:05 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
2008-03-29  8:04             ` Pierre Ossman [this message]

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=20080329090434.7bfb7509@mjolnir.drzeus.cx \
    --to=drzeus@drzeus.cx \
    --cc=benzizbit@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomasw@gmail.com \
    /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®