public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Johannes Stezenbach <js@sig21.net>
Cc: "Tim Bird" <tim.bird@am.sony.com>,
	"Josh Boyer" <jwboyer@gmail.com>, "Jörn Engel" <joern@logfs.org>,
	linux-embedded <linux-embedded@vger.kernel.org>,
	"linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Recommendation for activating a deferred module init in the	kernel
Date: Wed, 18 Jun 2008 02:10:42 +0200	[thread overview]
Message-ID: <48585282.4020508@s5r6.in-berlin.de> (raw)
In-Reply-To: <20080618000306.GA25466@linuxtv.org>

Johannes Stezenbach wrote:
> I think the USB bus enumeration can take significant time:
> recognize a device is connected, turn on bus power, try
> to read descriptors (bus powered devices might be slow to
> respond after power up). And this will happen even with
> drivers_autoprobe == 0, right?

Probably... I don't know which particular steps happen in the USB core 
before upper layer drivers are bound.  Not binding the [eou]hci-hcd PCI 
driver would certainly be more effective.
-- 
Stefan Richter
-=====-==--- -==- =--=-
http://arcgraph.de/sr/

  reply	other threads:[~2008-06-18  0:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <48580116.9070504@am.sony.com>
     [not found] ` <20080617190750.GA31224@logfs.org>
2008-06-17 19:52   ` Recommendation for activating a deferred module init in the kernel Tim Bird
2008-06-17 19:55     ` Tim Bird
2008-06-17 20:23       ` Jörn Engel
2008-06-17 20:35         ` Josh Boyer
2008-06-17 22:48           ` Stefan Richter
2008-06-18  0:03             ` Johannes Stezenbach
2008-06-18  0:10               ` Stefan Richter [this message]
2008-06-18  9:38                 ` Johannes Stezenbach
2008-06-17 20:19     ` Jörn Engel
     [not found]   ` <20080617192248.GH11921@sovereign.org>
2008-06-17 20:06     ` Tim Bird

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=48585282.4020508@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=joern@logfs.org \
    --cc=js@sig21.net \
    --cc=jwboyer@gmail.com \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim.bird@am.sony.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