fw/layer1: Encapsulate mframe scheduler function better

There was some code meddling with mf_tasks directly. This is
fine if it's just setting/clearing a bit but since we're
gonna need some 'cleverness' into when to activate what to prevent
conflict, it's better to abstract that logic.

Signed-off-by: Sylvain Munaut <tnt@246tNt.com>

1 files changed, 2 insertions, 2 deletions

diff --git a/src/target/firmware/layer1/sync.c b/src/target/firmware/layer1/sync.c
index bf027a82..f5629cfc 100644
--- a/src/target/firmware/layer1/sync.c
+++ b/src/target/firmware/layer1/sync.c
@@ -257,7 +257,7 @@ static void l1_sync(void)
 	//dsp_end_scenario();
 
 	/* schedule new / upcoming TDMA items */
-	mframe_schedule(l1s.mf_tasks);
+	mframe_schedule();
 	/* schedule new / upcoming one-shot events */
 	sched_gsmtime_execute(l1s.current_time.fn);
 
@@ -335,7 +335,7 @@ void l1s_reset(void)
 	l1s.sb.count = 0;
 
 	/* reset scheduler and hardware */
-	l1s.mf_tasks = 0;
+	mframe_reset();
 	tdma_sched_reset();
 	l1s_dsp_abort();
 }