From: David Brownell <david-b@pacbell.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Colin Leroy <colin@colino.net>,
<linux-usb-devel@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: [linux-usb-devel] 2.6.10-rc1 OHCI usb error messages
Date: Thu, 28 Oct 2004 09:51:35 -0700 [thread overview]
Message-ID: <200410280951.35639.david-b@pacbell.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0410281044070.1088-100000@ida.rowland.org>
On Thursday 28 October 2004 07:46, Alan Stern wrote:
> On Wed, 27 Oct 2004, David Brownell wrote:
>
> > So: since it's not being actively used then, why shouldn't the
> > root hub (or any other device) be suspended? During boot, or at
> > any other time. So long as it works when you plug in a USB device,
> > it looks to me like everything is behaving quite reasonably.
>
> The root hub _is_ actively being used during initial probing and
> enumeration, even though no devices may be plugged into it. Is it
> guaranteed that the root hub isn't suspended until after
> usb_register_root_hub returns?
It's never going to be suspended until after the hub driver has
set everything up -- that's the essential constraint. Since that
routine is called in a preemptible context, some systems could
end up preempting that call, so it'd suspend before that call
manages to return. That'd be OK, since everything's set up.
- Dave
prev parent reply other threads:[~2004-10-28 16:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 15:28 2.6.10-rc1 OHCI usb error messages Colin Leroy
2004-10-26 16:05 ` [linux-usb-devel] " David Brownell
2004-10-27 7:19 ` [PATCH] usb: don't spit out too much errors with suspended devices Colin Leroy
2004-10-27 23:13 ` David Brownell
2004-10-28 6:37 ` Colin Leroy
2004-10-27 9:07 ` [linux-usb-devel] 2.6.10-rc1 OHCI usb error messages Colin Leroy
2004-10-27 22:59 ` David Brownell
2004-10-28 9:07 ` Colin Leroy
2004-10-28 14:10 ` David Brownell
2004-10-28 14:46 ` Alan Stern
2004-10-28 16:51 ` David Brownell [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=200410280951.35639.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=colin@colino.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.