diff options
| author | Harald Welte <laforge@gnumonks.org> | 2010-02-28 22:58:30 +0100 |
|---|---|---|
| committer | Harald Welte <laforge@gnumonks.org> | 2010-03-01 23:48:45 +0100 |
| commit | 2f60aee6d93c509926fc017a80352fff62149992 (patch) | |
| tree | 7858300f45854b8a23bb9ad96328af1c0bd4785a /src/target/firmware/layer1/mframe_sched.c | |
| parent | aa4225d2cb41c8d42fa91e464a27f8af23c38bd8 (diff) | |
extend TDMA scheduler functions to use third parameter (p3)
The idea of the third parameter is that it can be specified on a
tdma_schedule_set() level. The multi-frame scheduler can thus use
it to pass some context information into the l1s_{cmd,resp}_*()
functions, such as the MF TASK and whether or not it is SDCCH or
SACCH.
Diffstat (limited to 'src/target/firmware/layer1/mframe_sched.c')
| -rw-r--r-- | src/target/firmware/layer1/mframe_sched.c | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/src/target/firmware/layer1/mframe_sched.c b/src/target/firmware/layer1/mframe_sched.c index 7bae6cad..502d102f 100644 --- a/src/target/firmware/layer1/mframe_sched.c +++ b/src/target/firmware/layer1/mframe_sched.c @@ -45,7 +45,7 @@ struct mframe_sched_item { /* At which number inside the modulo shall we be scheduled */ uint16_t frame_nr; /* bit-mask of flags */ - uint32_t flags; + uint16_t flags; }; /* FIXME: properly clean this up */ @@ -246,7 +246,8 @@ static void mframe_schedule_set(const struct mframe_sched_item *set) unsigned int current = (l1s.current_time.fn + SCHEDULE_AHEAD) % si->modulo; if (current == trigger) { /* FIXME: what to do with SACCH Flag etc? */ - tdma_schedule_set(SCHEDULE_AHEAD-SCHEDULE_LATENCY, si->sched_set); + tdma_schedule_set(SCHEDULE_AHEAD-SCHEDULE_LATENCY, + si->sched_set, si->flags); } } } |