usb: Use composite equipment codes as universal codes for enumeration

[zyfeier]

Summary

The enumeration process in each class driver is similar. Extracting the common enumeration process code to composite.c can reduce redundant code. In this PR, only the adb class has been modified, and it will be applicable to all classes in the next PR.

Impact

usb enumeration

Testing

sim:usbdev and bes board

[raiden00pl]

I don't think coupling USB device class logic with composite device logic is a good idea. These are two separate functionalities, and device class logic should not depend on composite logic.

Why not move the common USB device logic to a separate file, private for drivers/usbdev e.g. usbdev_common.c/usbdev_common.h ?

[zyfeier]

I don't think coupling USB device class logic with composite device logic is a good idea. These are two separate functionalities, and device class logic should not depend on composite logic.

Why not move the common USB device logic to a separate file, private for drivers/usbdev e.g. usbdev_common.c/usbdev_common.h ?

Hi, raiden00pl:
I initially extracted the common code, but found that it was almost identical to the code in composite.c. Additionally, the main difference between composite and non-composite devices is that composite devices support multiple functions, which can be distinguished through configuration. Therefore, I felt that it was more appropriate to directly use composite.c.

[raiden00pl]

Then composite devices and other USB devices should use common USB device logic. Now the code gives the impression that non-composite USB device is just composite device with one supported device - which is wrong and confusing.

[xiaoxiang781216]

Then composite devices and other USB devices should use common USB device logic. Now the code gives the impression that non-composite USB device is just composite device with one supported device - which is wrong and confusing.

so @raiden00pl do you want to rename the current composite driver to a general name and let's composite driver forward the call to these common function?

[raiden00pl]

@xiaoxiang781216 it would actually make sense that way but composite specific functionality should be keep in the composite.c (eg. composite_ep0submit())

[xiaoxiang781216]

Ok, let's do it in the next step.