mirror of
https://github.com/esp-rs/esp-hal.git
synced 2025-09-28 04:40:52 +00:00
571760884b
* Add a timer-driven task * Spawn another timer * Log * foo * Do not access current time on each schedule * Update generic queue * Minimize alarm priorities * Point to github with patches * Fix build without any queue impl selected * Remove explicit generic-queue features * Define cfgs, fix calling something uninitialized * Clean up RefCell+generic queue * Fix arg order * Feature * Fix single integrated-timer queue * Fix next expiration when arming * Add note * Adjust impl to latest changes * Local patch * Refactor the refactor refactor * Track the timer item's owner * Clear owner on dequeue * Clean up * Point at the right branch * Fix panic message * Hide private function * Remove integrated-timer references * Point at upstream embassy * Configure via esp-config * Document, clean up, fix * Hack * Remove patches * Update config separator, test the complex variant * Undo esp-config hack * Remove trouble example, update edge-net * Update test deps * Document * Update bt-hci. * Fix generic queue * Fix panic message * Fix UB * Fix rebase * Resolve UB * Avoid mutable reference in interrupt executor --------- Co-authored-by: Dario Nieuwenhuis <dirbaio@dirbaio.net>
2.1 KiB
2.1 KiB
Migration Guide from 0.5.x to v0.6.x
Crate configuration changes
To prevent ambiguity between configurations, we had to change the naming format of configuration
keys. Before, we used {prefix}_{key}, which meant that esp-hal and esp-hal-* configuration keys
were impossible to tell apart. To fix this issue, we are changing the separator from one underscore
character to _CONFIG_. This also means that users will have to change their config.toml
configurations to match the new format.
[env]
-ESP_HAL_EMBASSY_LOW_POWER_WAIT="false"
+ESP_HAL_EMBASSY_CONFIG_LOW_POWER_WAIT="false"
Removal of integrated-timers
The integrated-timers feature has been replaced by two new configuration options:
ESP_HAL_EMBASSY_CONFIG_TIMER_QUEUE: selects a timer queue implementation, which allows tuning based on a few requirements. Possible options:generic: a generic queue implementation is used. This option does not depend on embassy-executor, uses a global critical section to access the timer queue, and its capacity determines how many tasks can wait for timers at the same time. You need to pass only a single timer toesp_hal_embassy::init.single-integrated: This option requires embassy-executor and theexecutorsfeature, uses a global critical section to access the timer queue. You need to pass only a single timer toesp_hal_embassy::init. This is slightly faster thangenericand does not need a capacity configuration. This is the default option when theexecutorsfeature is enabled.multiple-integrated: This option requires embassy-executor and theexecutorsfeature, uses more granular locks to access the timer queue. You need to pass one timer for each embassy executor toesp_hal_embassy::initand the option does not need a capacity configuration. This is the most performant option.
ESP_HAL_EMBASSY_CONFIG_GENERIC_QUEUE_SIZE: determines the capacity of the timer queue when using thegenericoption.esp_hal_embassyignores theembassy-time/generic-queue-*features.