-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fails to load after suspend/ resume #1
Comments
Probably... I never really handled resume/suspend. I had enough issues just getting the damn thing to work how I wanted. It still doesn't work correctly whenever you unload the module (although, I feel this is partially due to the fault of how unclear the Linux kernel interface is when letting it automatically unload the USB module). Although, this should be fixed to at least the point of not causing issues. Thinks for reminding me. |
By the way, I've not tried that. Does the driver not do anything or does it work despite giving that message? |
for testing I set a timeout of 500ms for obviously LED submission (and probably FF) did not work, but the input device is created and works. I also found out that plugging the receiver in and out solves the issue. So I guess this has something to do with the Linux USB interface. |
I'd imagine we can kill the recieving urb on suspend and start it back up on resume. That's probably the most appropriate. I'm working on getting a virtual machine running again... EDIT: We also need to set the LED appropriately as if the computer shut off, then make sure no urbs are active. |
when trying to load the driver after suspend/ resume:
the same error also exists in the orginal xpad codebase:
paroj/xpad#6
can you reproduce this? or is it just my kernel/ hardware combination?
The text was updated successfully, but these errors were encountered: