On Tue, Jan 5, 2021 at 7:49 AM Greg KH [off-list ref] wrote:

On Tue, Jan 05, 2021 at 02:02:16AM +0100, Tomasz Grobelny wrote:

quoted

Any idea why this might be the case? Can I somehow enforce that the
device reintroduces itself on the bus and gets new address? Can I
somehow debug what happens when my device is connected as gadget (eg.
see control messages for device/configuration/string descriptors)?

Why does it matter what USB "address" your device gets?  That's a random
number that nothing should care about as the USB spec allows it to be
reused if the host controller wants to.

Not that I know 100% it matters, but until now this is the only
observable difference in dmesg. It is just my guess that something
might have gone wrong with reinitialization. Also see other questions
how to debug this.

What requires a "different" address each time?  Shouldn't that userspace
bug be fixed instead?

The userspace code does not require different address, not even sure
it could get one via functionfs.

Best regards,
Tomasz Grobelny