From 2afc002e1255f711325abc44e1d670d32a8b25a6 Mon Sep 17 00:00:00 2001 From: Sylvain Munaut Date: Mon, 26 Apr 2010 21:33:26 +0200 Subject: 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 --- src/target/firmware/layer1/l23_api.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/target/firmware/layer1/l23_api.c') diff --git a/src/target/firmware/layer1/l23_api.c b/src/target/firmware/layer1/l23_api.c index e54d72bd..fec6183e 100644 --- a/src/target/firmware/layer1/l23_api.c +++ b/src/target/firmware/layer1/l23_api.c @@ -204,7 +204,7 @@ static void l1a_l23_rx_cb(uint8_t dlci, struct msgb *msg) } /* FIXME: set TSC of ded chan according to est_req.h0.tsc */ /* figure out which MF tasks to enable */ - l1s.mf_tasks = (1 << chan_nr2mf_task(ul->chan_nr)); + l1a_mftask_set(1 << chan_nr2mf_task(ul->chan_nr)); break; case L1CTL_RACH_REQ: rach_req = (struct l1ctl_rach_req *) ul->payload; -- cgit v1.2.3