Hi all,

I've been using the `Clock` trait  from the (inactive) `embedded-time` crate, and I was wondering if there's any activity around setting up a canonical means of encapsulating some clock-realated interfaces in `embedded-hal`?

Here is how I'm (roughly) using the `Clock` trait in my project:

```rust
struct Timer0<TG: TimerGroupInstance> {
    timer: esp_hal::timer::Timer<esp_hal::timer::Timer0<TG>, Blocking>,
}

impl<TG: TimerGroupInstance> Timer0<TG> {
    fn init(timer: esp_hal::timer::Timer<esp_hal::timer::Timer0<TG>, Blocking>) -> Self {
        timer.enable_peripheral();
        Self { timer }
    }
}
impl<TG: TimerGroupInstance> embedded_time::Clock for Timer0<TG> {
    type T = u64;

    const SCALING_FACTOR: Fraction = <Fraction>::new(1, 80_000_000);

    fn try_now(&self) -> Result<embedded_time::Instant<Self>, embedded_time::clock::Error> {
        Ok(Instant::new(esp_hal::timer::Instance::now(&*self.timer)))
    }
}
```

so with this struct implementing the `Clock` trait, I can write my library to be platform agnostic, similarly to how the `InputPin` trait allows code to be platform agnostic when it comes to reading the state of an input pin.