diff options
| author | Sylvain Munaut <tnt@246tNt.com> | 2010-04-26 21:33:26 +0200 |
|---|---|---|
| committer | Sylvain Munaut <tnt@246tNt.com> | 2010-04-28 10:17:04 +0200 |
| commit | 2afc002e1255f711325abc44e1d670d32a8b25a6 (patch) | |
| tree | 197c86a92caad3e9859d575c7786c4a37a4e0d03 /src/target/firmware/layer1/prim_fbsb.c | |
| parent | afc0ee79c466f74194c19770489d01ce1370f9da (diff) | |
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>
Diffstat (limited to 'src/target/firmware/layer1/prim_fbsb.c')
| -rw-r--r-- | src/target/firmware/layer1/prim_fbsb.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/target/firmware/layer1/prim_fbsb.c b/src/target/firmware/layer1/prim_fbsb.c index 98a88486..3cd14c4d 100644 --- a/src/target/firmware/layer1/prim_fbsb.c +++ b/src/target/firmware/layer1/prim_fbsb.c @@ -416,8 +416,8 @@ static int l1s_sbdet_resp(__unused uint8_t p1, uint8_t attempt, if (l1s.sb.count > 10 && sb_time.t3 == 41) { l1s_reset_hw(); /* enable the MF Task for BCCH reading */ - l1s.mf_tasks |= (1 << MF_TASK_BCCH_NORM); - l1s.mf_tasks |= (1 << MF_TASK_CCCH_COMB); + mframe_enable(MF_TASK_BCCH_NORM); + mframe_enable(MF_TASK_CCCH_COMB); } else { /* We have just seen a SCH burst, we know the next one * is not in less than 7 TDMA frames from now */ |