Fwd: USB Driver - Device No Response standard compliant

[Valdis.Kletnieks at vt.edu]

On Sun, 02 Aug 2015 00:04:44 -0300, Christian N said:

> I know that the presentation of the message is the responsibility of
> the application (user space), but to do this is necesary an event from
> usb driver (I think it).

A timeout with no activity at all can do it.. That's Userspace C 101 -
select() with a timeout...

>                          Nowdays when a non responsive device is
> attached, "unable to enumerate USB device on port... " is logged a in
> dmesg, but not event is dispatched (by example in usb_uevent).
> Without an event application should poll the log (loading the system
> unnecessarily) searching new "not responsive devices".
>
> To comply with the standard usb driver should be modified?

No, because userspace can detect the condition on its own and tell
a user about it.

> I'm probably confusing responsibilities of user and kernel space. I
> appreciate your opinion/answer.

Yes, you are.  Although I suspect the "standard" you're quoting is
confusing them as well....
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150801/56d95227/attachment.bin