Am Dienstag, 30. Januar 2007 19:16 schrieb Alan Stern:
> On Tue, 30 Jan 2007, Oliver Neukum wrote:

[..] 

> > Furthermore, what about input? It seems to me that it also can call 
> > wake_up()?
> 
> You mean the control-IN queue?  Same thing: either stop the queue or wait 
> for it to drain.

No, I am talking about interrupt-in.
hid_resume() calls hid_start_in(), which submits  an URB, which may
finish any time afterwards. hid_irq_in() may call hid_input_report().

> > Is this a specific limitation of suspend2?
> 
> What do you mean?

If calling wake_up() in suspend() is not a problem, why is it problematic
in resume(). Does ordinary swsusp allow that?

        Regards
                Oliver

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to