usbd_hid: Add .suspend/.resume callbacks

[ndreys]

Add .suspend/.resume callbacks to pass those events to the users, so they can react accordingly.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[josuah]

Hello @ndreys,

This PR could interest you as it seems almost the same:

• usb: device_next: hid: add a suspend callback #99123

[ndreys]

Hello @ndreys,

This PR could interest you as it seems almost the same:

• usb: device_next: hid: add a suspend callback #99123

Thanks, yeah.

@jfischer-no

An interface cannot be suspended, and there is nothing like that in the HID specification. To get notifications when a USB device is suspended, please use USBD_MSG_SUSPEND and USBD_MSG_RESUME. There is no reason to have additional callbacks in each function/class implementation.

Whether interface can or cannot be suspended seems orthogonal. You can suspend a device and then take local, interface-specific actions when that happens. I have a composite device with multiple HID interfaces and having those callbacks allows to easily separate the concerns of each of those devices. Using USBD_MSG_SUSPEND requires registering a shared message callback and then dispatch that to individual interfaces which creates another layer of unnecessary interconnetions.

Can we please revisit this?