feat(uac_host): Add global suspend/resume

[peter-marcisovsky]

Description

This MR adds Suspend/Resume events for UAC class driver as a follow-up for the Global/Suspend resume MR in esp-idf

Changes

Added Suspend and Resume UAC Host driver events

/**
 * @brief USB UAC Device (Interface) event id
*/
typedef enum {
    UAC_HOST_DEVICE_EVENT_RX_DONE = 0x00,                /*!< RX Done: the receive buffer data size exceeds the threshold */
    UAC_HOST_DEVICE_EVENT_TX_DONE,                       /*!< TX Done: the transmit buffer data size falls below the threshold */
    UAC_HOST_DEVICE_EVENT_TRANSFER_ERROR,                /*!< UAC Device transfer error */
    UAC_HOST_DRIVER_EVENT_DISCONNECTED,                  /*!< UAC Device has been disconnected */
    UAC_HOST_DEVICE_EVENT_SUSPENDED,                     /*!< UAC Device has been suspended */
    UAC_HOST_DEVICE_EVENT_RESUMED,                       /*!< UAC Device has been resumed */
} uac_host_device_event_t;

As the global Suspend issued by the USB Host Halts and flushes all EPs of all connected devices. The UAC Host driver must submit the in transfer(s) upon Resuming the root port

Related

• Closes Suspend/Resume support for HID Class driver

Testing

TODO add tests

---

Checklist

Before submitting a Pull Request, please ensure the following:

• 🚨 This PR does not introduce breaking changes.
• All CI checks (GH Actions) pass.
• Documentation is updated as needed.
• Tests are updated or added as necessary.
• Code is well-commented, especially in complex areas.
• Git history is clean — commits are squashed to the minimum necessary.

[peter-marcisovsky]

Hi @leeebo in this MR I am adding support for global suspend/resume of the root port.

In the current uac driver, there are public API functions like:

/**
 * @brief Resume a UAC stream with same stream configuration
 */
esp_err_t uac_host_device_resume(uac_host_device_handle_t uac_dev_handle);

and

/**
 * @brief Suspend a UAC stream
 *
 * @param[in] uac_dev_handle  UAC device handle
 */
esp_err_t uac_host_device_suspend(uac_host_device_handle_t uac_dev_handle);

And other static functions like uac_host_interface_suspend(), uac_host_interface_resume().

Which are suspending and resuming the UAC stream, not the device itself in terms of power consumption lowering.

My concern here is, that users might get confused with naming of those functions. And might mistakenly call uac_host_device_suspend() with intention to put a UAC device into a suspended state, to lower it's power consumption. But the function only suspends a UAC stream.

Do you thinks we should consider renaming the functions to something like uac_host_device_suspend_stream() and uac_host_device_resume_stream() ? Can you PTAL and advise how to handle this?

[leeebo]

Yes, I think rename to _suspend_stream() and _resume_stream() is a good choice

[peter-marcisovsky]

@leeebo renaming the public api would cause a breaking change for the UAC component.
Should should we consider bumping a Major version when releasing this feature ?

[leeebo]

@peter-marcisovsky The implements LGTM! Thanks