Thread (45 messages) flat view 45 messages, 9 authors, 2015-06-02

Re: [RESEND][PATCH] Bluetooth: Make request workqueue freezable

From: Oliver Neukum <oneukum@suse.com>
Date: 2015-05-22 11:31:37
Also in: lkml, netdev

On Thu, 2015-05-21 at 22:46 +0200, Arend van Spriel wrote:
On 05/21/15 19:32, Takashi Iwai wrote:
quoted
quoted
quoted
quoted
quoted
Well, if the probe requires the access to a user-space file, it can't
be done during resume.  That's the very problem we're seeing now.
The firmware loader can't help much alone if it's a new device
object.
So you are saying each device driver should come up with some retry 
mechanism. Would make more sense to come up with something like that 
behind the scenes in the firmware loader so all device drivers can rely 
on one and the same solution.
There is already a notifier for this. I don't see why the firmware
layer couldn't retrigger a match for all unbound devices, just like
we do when a new driver is loaded.

	Regards
		Oliver
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help