embassy/embassy-executor/src/arch/spin.rs, branch fix-input-sync-bypass Unnamed repository; edit this file 'description' to name the repository. Rustfmt for edition 2024. 2025-10-06T21:19:53+00:00 Dario Nieuwenhuis dirbaio@dirbaio.net 2025-10-06T20:56:31+00:00 8730a013c395cf0bf4c2fa8eeb7f138288103039 






Edition 2024.
2025-10-06T21:19:53+00:00

Dario Nieuwenhuis
dirbaio@dirbaio.net

2025-10-06T20:55:38+00:00

abc8e450f936567ad42cb34b5d2a7941b206aa5d












Refactor integrated-timers
2024-12-10T20:31:42+00:00

Dániel Buga
bugadani@gmail.com

2024-11-26T22:54:21+00:00

5a5495aac43d75610735f2ca80fb6c8e8f31ed71












Add initialize
2024-11-19T15:25:17+00:00

Dániel Buga
bugadani@gmail.com

2024-11-19T14:59:31+00:00

8ebe059ecb311ee949f92dde33f2cb8d972b0f7b












executor/spin: introduce an architecture agnostic executor
2024-10-07T06:33:34+00:00

Dummyc0m
xieyuanchu@gmail.com

2024-10-07T06:23:33+00:00

9e6e09a8d747ec90aae215df8471dfe349993487

Spin polls the raw executor and never sleeps. It is useful for disabling
any power features associated with wfi/wfe-like instructions.

When implementing support for the CH32V30x MCU, the wfi instruction
had issues interacting with the USB OTG peripheral and appeared to be
non-spec-compliant.

1. When sending a USB Data-in packet, the USB peripheral appears to be
unable to read the system main memory while in WFI. This manifests in
the USB peripheral sending all or partially zeroed DATA packets.
Disabling WFI works around this issue.

2. The WFI instruction does not wake up the processor when MIE is
disabled. The MCU provides a WFITOWFE bit to emulate the WFE instruction
on arm, which, when enabled, ignores the MIE and allows the processor to
wake up. This works around the non-compliant WFI implementation.

Co-authored-by: Codetector <codetector@codetector.org>
Co-authored-by: Dummyc0m <y@types.moe>





Spin polls the raw executor and never sleeps. It is useful for disabling
any power features associated with wfi/wfe-like instructions.

When implementing support for the CH32V30x MCU, the wfi instruction
had issues interacting with the USB OTG peripheral and appeared to be
non-spec-compliant.

1. When sending a USB Data-in packet, the USB peripheral appears to be
unable to read the system main memory while in WFI. This manifests in
the USB peripheral sending all or partially zeroed DATA packets.
Disabling WFI works around this issue.

2. The WFI instruction does not wake up the processor when MIE is
disabled. The MCU provides a WFITOWFE bit to emulate the WFE instruction
on arm, which, when enabled, ignores the MIE and allows the processor to
wake up. This works around the non-compliant WFI implementation.

Co-authored-by: Codetector <codetector@codetector.org>
Co-authored-by: Dummyc0m <y@types.moe>