You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is related to issue #19
We might have to implement some variant of activate wait, like delay_us() or delay_ms() for every arch & every clock speed.
This is not that obvious withotu a massive refactoring, unless maybe arch_counter() might be used differently (as a freerunnning counter, similar to MIPS and RISC-V).
The text was updated successfully, but these errors were encountered:
Here's a possible workaround: let the clock driver allow to wait for a certain number of cycles / ns.
This won't fix the sync between clock domains that occur on almost any sam related driver, though.
This is related to issue #19
We might have to implement some variant of activate wait, like delay_us() or delay_ms() for every arch & every clock speed.
This is not that obvious withotu a massive refactoring, unless maybe arch_counter() might be used differently (as a freerunnning counter, similar to MIPS and RISC-V).
The text was updated successfully, but these errors were encountered: