Skip to content

Migrate from bisync to maybe-async - #6

Open
Gioelio wants to merge 2 commits into
STMicroelectronics:mainfrom
Gioelio:main
Open

Gioelio wants to merge 2 commits into
STMicroelectronics:mainfrom
Gioelio:main

Conversation

@Gioelio

@Gioelio Gioelio commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Due to a yanked version of bisync, the available solutions (I found) were:

  • Vendor bisync: Include a vendor/bisync folder by cloning the project. This would lose author support and macro updates, while any bug fixes would require updating every driver.
  • Fork bisync into a new crate: This avoids updating every driver individually and reduces duplicated code, but still lacks upstream updates.
  • Migrate from bisync to maybe-async: Replaces the dependency entirely and get community support.

This PR implements the third option. If approved, the remaining steps are:

  1. Release a new major version of both st-mem-bank-macro and st-mems-bus.
  2. Update all sensor drivers (a straightforward change; once the major releases are published, I will open the necessary PRs).

If anyone has a better proposal or solution, feel free to share it here.

Change code to support maybe-async code generation.
Add is_sync feature to switch between sync OR async mode.
Update README accordingly

Signed-off-by: Gioele Fiorenza <gioele.fiorenza2000@gmail.com>
Change macro code to generate implementation based on maybe-async macros
instead of bisync.
Update README accordingly

Signed-off-by: Gioele Fiorenza <gioele.fiorenza2000@gmail.com>
This was referenced Sep 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants