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
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
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
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
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
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
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
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
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
the `-rie` arguments of `sed` were probably meant as `-r -i -e`,
however, due to the way it was written it ended up being `-r -i e`, thus
causing `-i` (edit in-place) to generate backup files. so for every
edited `Cargo.toml` it also created a `Cargo.tomle` with the previous
content.
`-e` is anyway not needed as the last argument of `sed` here is the
expression to be executed.
new() now resets the opamp and enables its clock. The clock is
disabled when the opamp is dropped. On families that use
SYSCFGEN (F3 and G4), this is not done because this
clock is always on in Embassy.
This change makes use of the RCC driver, which uses a reference
counter to prevent conflicts. The opamp itself is still disabled
when its output is dropped.
