[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201112311659.48427.oliver@neukum.org>
Date: Sat, 31 Dec 2011 16:59:48 +0100
From: Oliver Neukum <oliver@...kum.org>
To: Alan Stern <stern@...land.harvard.edu>
Cc: Matthew Garrett <mjg@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Dave Jones <davej@...hat.com>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Larry Finger <Larry.Finger@...inger.net>,
Chaoming Li <chaoming_li@...lsil.com.cn>,
"John W. Linville" <linville@...driver.com>,
"Greg Kroah-Hartman" <gregkh@...e.de>,
USB list <linux-usb@...r.kernel.org>,
Linux Wireless List <linux-wireless@...r.kernel.org>
Subject: Re: loading firmware while usermodehelper disabled.
Am Samstag, 31. Dezember 2011, 16:33:12 schrieb Alan Stern:
> Nothing has changed in the USB layer -- it has always been true that
> devices could be reset during a suspend/resume cycle. This isn't a
> matter of how the stack is written or anything like that; some
> motherboards simply do not provide suspend power to their USB
> controllers. Or the firmware reinitializes the controllers and
> attached devices during resume, forcing Linux's USB core to reset
> every device on the affected buses.
>
> When it comes to suspend/resume, there are almost no guarantees. :-(
We are definitely going through do_unbind_rebind(). But I don't think
it matters why we got there. We seem to be calling probe() too early.
And we need to guarantee that a driver can request firmware in probe()
So something has changed in the resume code path further up.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists