diff options
| author | Holger Hans Peter Freyther <holger@moiji-mobile.com> | 2013-10-25 18:32:16 +0200 |
|---|---|---|
| committer | Holger Hans Peter Freyther <holger@moiji-mobile.com> | 2013-10-25 19:14:44 +0200 |
| commit | 6321c72522897b2e8df787a73441f699b5af28d9 (patch) | |
| tree | 6febed4d7dc06a3576a963d102f572c866b4080d /include | |
| parent | e851e134134b37113adc82d052bb5ba7e227797d (diff) | |
rsl/pcu: Do not send a CHAN ACT to the BSC on PCU usage
The PCU is forcing the activation of a PDCH. Currently the BSC
will receive a channel act ack for a channel that was not
activated at all. Use the "release_reason" flag of the lchan
to see if we have requested a normal activation or a silent
one.
It feels a bit odd to do it in the TX function but it is the
most easy solution right now. I have added logging so it will
not be totally silent.
Diffstat (limited to 'include')
| -rw-r--r-- | include/osmo-bts/rsl.h | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/include/osmo-bts/rsl.h b/include/osmo-bts/rsl.h index 251cd23d..ede9edc8 100644 --- a/include/osmo-bts/rsl.h +++ b/include/osmo-bts/rsl.h @@ -1,6 +1,15 @@ #ifndef _RSL_H #define _RSL_H +/** + * What kind of release/activation is done? A silent one for + * the PDCH or one triggered through RSL? + */ +enum { + LCHAN_REL_ACT_RSL, + LCHAN_REL_ACT_PCU, +}; + int down_rsl(struct gsm_bts_trx *trx, struct msgb *msg); int rsl_tx_rf_res(struct gsm_bts_trx *trx); int rsl_tx_chan_rqd(struct gsm_bts_trx *trx, struct gsm_time *gtime, |