feature(esp_tinyusb): TinyUSB task deletion notification driven (part 2/3)

[roma-jam]

Description

This is the second part of the plan: Add a test application for CPU load

The test case has been added to the runtime_config, which is the future will be used as a general esp_tinyusb device test.

Measuring values:

• Run Time (Amount of ticks, that works the TinyUSB task during enumeration): < 1800
• CPU load (Percentage of the CPU time): == 0 (as most of the time CPU spend in IDLE0 and IDLE1 tasks)

Name                   Run time CPU load
TinyUSB                    1741       0%
main                       8340       0%
IDLE1                    826544      50%
IDLE0                    824993      49%
ipc1                          0       0%
ipc0                          0       0%

Limitations

CPU Load is calculated based on the Run time value for the task. Precision of the current calculation is not enough to show the real CPU Load in percentage in our case (as it is less than 1%).

In the current PR we measure the Run Time value and expect it to be in the interval:

• ESP32-S2: 0 < Run Time < 5000
• ESP32-S3: 0 < Run Time < 3000
• ESP32-P4: 0 < Run Time < 1800
• assert if the target is not in the table

Related

• Prerequisites in refactor(esp_tinyusb): TinyUSB task deletion notification driven (part 1/3) #322
• Follow-up in: feature(esp_tinyusb): TinyUSB task deletion notification driven (part 3/3) (IEC-441) #272
• Relates IEC-351
• Blocked by fix(ci): Unlocks CI by temp disabling the usb host_managed tests on latest branch #324
• Increase precision for CPU Load calculation in [TODO: add a link to the PR ]

Testing

• Added test case: [CPU load] Install & Uninstall, default configuration", "[cpu_load] with pytest scenario

---

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.

[Copilot]

Pull Request Overview

This PR adds CPU load measurement capabilities to the TinyUSB test suite to ensure the task deletion notification-driven implementation doesn't introduce performance regressions. The test measures both runtime ticks and CPU load percentage during USB device enumeration.

Key Changes:

• Adds CPU load and runtime statistics measurement test for TinyUSB task
• Validates that TinyUSB task CPU load remains at 0% after enumeration
• Validates that TinyUSB runtime stays below 1800 ticks during enumeration

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 5 comments.

File	Description
sdkconfig.defaults	Enables FreeRTOS trace facility and runtime stats for CPU load measurement
pytest_runtime_config.py	Adds pytest test case to verify CPU load metrics are within expected thresholds
test_cpu_load.c	Implements CPU load measurement logic using FreeRTOS runtime statistics

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[roma-jam]

Hi

@tore-espressif
@peter-marcisovsky
@igi540

This one is also ready, PTAL after the part 1.

[peter-marcisovsky]

LGTM, no other comments.

[roma-jam]

Converted to draft to apply Peter's notes and resolve conflicts.

[cursor]

You have run out of free Bugbot PR reviews for this billing cycle. This will reset on December 20.

To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[roma-jam]

Hi
@tore-espressif,
@igi540,

This one is ready again, PTAL.