6 Commits

Author	SHA1	Message	Date
Scott Mabin	19c9cef9a8	auto enable interrupts (#1014) ... * auto enable interrupts * changelog * cfgs	2023-12-12 17:55:37 +00:00
Dániel Buga	39519dfdc9	RISC-V executors (#947) ... * RISC-V executors * Add multiprio example to RISC-V SoCs * Check new examples * Hack in support for generic queue * Reserve SoftwareInterrupt0 for multicore thread-mode executors * Merge interrupt executors * Merge thread-mode executors * Document the new features and expand on time drivers * Main tasks don't have to return ! * Unify multiprio examples * Undo C6 log output change	2023-11-22 14:36:53 +00:00
Björn Quentin	a0ebdf0399	embassy #[main] convenience for RISC-V / Xtensa (#841)	2023-10-11 12:10:14 +01:00
Dániel Buga	44e968f7a8	Make sure examples can actually build with defmt enabled, build some examples in CI (#810) ... * Make sure examples can build with defmt * Remove duplicate example checks * Fix examples * Add changelog entry * Actually build some examples with defmt feature enabled * Add the defmt linker script in each package's build script	2023-10-05 12:13:09 -07:00
Scott Mabin	db409ffe7b	Unify the system peripheral (#832) ... * Unify the system peripheral Whilst the PCR, SYSTEM and DPORT peripherals are different, we currently use them all in the same way. This PR unifies the peripheral name in the hal to `SYSTEM`. The idea is that they all do the same sort of thing, so we can collect them under the same name, and later down the line we can being to expose differences under an extended API. The benifits to this are imo quite big, the examples now are all identical, which makes things easier for esp-wifi, and paves a path towards the multichip hal. Why not do this in the PAC? Imo the pac should be as close to the hardware as possible, and the HAL is where we should abstractions such as this. * changelog	2023-09-29 08:14:50 -07:00
Björn Quentin	a642ee40da	Async RMT (#787) ... * Async RMT * Add CHANGELOG item * Pin toml_edit transitive dependency	2023-09-13 09:02:36 +02:00