80bb09cdb1
this requires you to install [`cargo-release`]. note that this does not include a URL pointing to the diff on GitHub as is usually done in changelogs since `embassy` is a mono-repo and the GH UI doesn't offer a commit view per folder (see the [GH feature request] for this). [`cargo-release`]: https://crates.io/crates/cargo-release [GH feature request]: https://github.com/orgs/community/discussions/162131
embassy-time-driver
This crate contains the driver trait necessary for adding embassy-time support
for a new hardware platform.
If you want to use embassy-time with already made drivers, you should depend on the main embassy-time crate, not on this crate.
If you are writing a driver, you should depend only on this crate, not on the main embassy-time crate.
This will allow your driver to continue working for newer embassy-time major versions, without needing an update,
if the driver trait has not had breaking changes.
How it works
embassy-time is backed by a global "time driver" specified at build time.
Only one driver can be active in a program.
All methods and structs transparently call into the active driver. This makes it
possible for libraries to use embassy-time in a driver-agnostic way without
requiring generic parameters.