Do not depend on embassy-time directly

Author: bugadani

Cargo.toml

@@ -23,13 +23,11 @@ log = { version = "0.4", default-features = false }
 futures-io = { version = "0.3", default-features = false, optional = true, features = ["std"] }
 futures-lite = { version = "2", default-features = false, optional = true }
 embassy-time-driver = { version = "0.2", optional = true }
-embassy-time = { version = "0.4", optional = true }
 
 [dev-dependencies]
 futures-io = "0.3"
 futures-lite = "2"
-embassy-time = { version = "0.4", features = ["std"] }
-embassy-time-queue-utils = { version = "0.1", features = ["generic-queue-64"] }
+embassy-time = { version = "0.4", features = ["std", "generic-queue-64"] }
 async-channel = "2"
 env_logger = "0.10"
 

README.md

@@ -39,7 +39,7 @@ Further, `async-io` has a non-trivial set of dependencies (again - for MCUs; for
 
 ## Enhancements
 
-The `Timer` type of `async_io_mini` is based on the `embassy-time` crate, and as such should offer a higher resolution on embedded operating systems like the ESP-IDF than what can be normally achieved by implementing timers using the `timeout` parameter of the `select` syscall (as `async-io` does). 
+The `Timer` type of `async_io_mini` is based on the `embassy-time` crate, and as such should offer a higher resolution on embedded operating systems like the ESP-IDF than what can be normally achieved by implementing timers using the `timeout` parameter of the `select` syscall (as `async-io` does).
 
 The reason for this is that on the ESP-IDF, the `timeout` parameter of `select` provides a resolution of 10ms (one FreeRTOS sys-tick), while
 `embassy-time` is implemented using the [ESP-IDF Timer service](https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-reference/system/esp_timer.html), which provides resolutions up to 1 microsecond.
@@ -64,7 +64,7 @@ To wait for the next I/O event, the "async-io-mini" thread uses the [select](htt
 
 ### Timer
 
-As per above, the `Timer` type is a wrapper around the functionality provided by the `embassy-time` crate.
+As per above, the `Timer` type is a wrapper around the functionality provided by the `embassy-time` crate. This means your application needs to select and use an `embassy-time-driver` implementation. Such an implementation is provided by HAL crates, or `embassy-time` implements one for `std`.
 
 ## Examples
 

src/timer.rs

@@ -92,8 +92,6 @@ impl Timer {
     /// # });
     /// ```
     pub fn never() -> Timer {
-        let _fix_linking = embassy_time::Timer::after(embassy_time::Duration::from_secs(1));
-
         Timer {
             when: None,
             period: Duration::MAX,