Displaying 2 results from an estimated 2 matches for "release_interface".
2014 Apr 19
3
usbhid-ups pull request for consideration
...1. Scale values for some of the SMART1500LCD parameters.
2. With my hardware and kernel, usbhid-ups wouldn't run more than 10
minutes before exiting with a fatal error. This seems to be related to
holding usb_claim_interface() the entire life of the program. I've
refactored claim_interface/release_interface calls to be around only when
work is being done. Now usbhid-ups has run for 24+ hours without issue.
3. The very nature of USB in a home means that sometimes the driver will
lose communications with the UPS (accidently unplug the hub, needed a port
for a camera, etc). This shouldn't be a fatal...
2014 Apr 24
0
usbhid-ups pull request for consideration
...s for some of the SMART1500LCD parameters.
Thanks!
> 2. With my hardware and kernel, usbhid-ups wouldn't run more than 10 minutes before exiting with a fatal error. This seems to be related to holding usb_claim_interface() the entire life of the program. I've refactored claim_interface/release_interface calls to be around only when work is being done. Now usbhid-ups has run for 24+ hours without issue.
Given how long we have been running with code that claims the interface at driver startup, I am a wary about changing this behavior. Have you had a chance to raise this with the Linux USB folks? I...