On Wed, Nov 29, 2023 at 04:33:58PM +0100, Oliver Neukum wrote: > On 29.11.23 16:16, Jose Ignacio Tornos Martinez wrote: > > Hi, > > > The reason is that although the device is detached, normal stop and > > unbind operations are commanded. Avoid these unnecessary operations > > when the device is detached (state is USB_STATE_NOTATTACHED) so as > > not to get the error messages. > > I am sorry, but this is a layering violation. You are looking > at an internal state of the USB layer to surpress logging > -ENODEV. If you think these messages should go away, filter > for ENODEV where they are generated. Indeed. In addition, you should be more careful about the distinction between "unbound" and "disconnected". It's possible for the driver to be unbound from the device even while the device is still plugged in. In this situation, submitting URBs will fail with an error even though the device state isn't USB_STATE_NOTATTACHED. Alan Stern
