fix(esp_tinyusb): Pinned tinyusb task to the CPU1 by default

[roma-jam]

esp_tinyusb component, v1.5.0

Requirements

A problem could be present in a high-loaded systems (with several interfaces) and when large amounts of data were being sent and received simultaneously, the dcd_event_xfer_complete event was not triggered.

Description

Pinned tinyusb FreeRTOS task to CPU1 by default in the dual-core systems.

Related

• Releated to IDF-4552

Testing

N/A

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.

[tore-espressif]

@roma-jam

• please add the change to CHANGELOG.md
• Make sure it works as expected in single core system (ESP32-S2)

[roma-jam]

@tore-espressif If we have the CI such as: Build and Run USB Test Application (which builds and runs the test_apps on esp32s2), does it counts that it works "as expected"?

Or you are talking about something else?

[tore-espressif]

does it counts that it works "as expected"?

Yes, that is actually enough :D Maybe just add a comment that it is OK top pin to CPU1 on single CPU system. The users might get confused