diff options
| author | Pau Espin Pedrol <pespin@sysmocom.de> | 2019-11-12 16:30:30 +0100 |
|---|---|---|
| committer | Pau Espin Pedrol <pespin@sysmocom.de> | 2019-11-20 15:35:05 +0100 |
| commit | f8d0389c70ed97cbb0488c0b7e5ac594d566fdb5 (patch) | |
| tree | 80ade7bb419c27e2b6557c9e31e6ec38aa9ed6fa /tests/nanobts_omlattr | |
| parent | 26adddf1bfa37dbeff8e60594141e9fb3afdd46e (diff) | |
bsc: Send MS Power Control msg upon max MS power change
Lots of times, the MS power class is unknown until after the first
channel has been activated, at which point the MS power class is
received in messages such as LU update or CM Service Requet.
Since the MS Power level is sent upon CHAN ACT, the only way to
communicate the change of maximum MS Power (based on MS power class)
after CHAN ACT is to send a MS Power Control msg. Let's do that.
Related: OS#4244
Change-Id: I3d6b75578e5cb9b2ad474a0ad01362d846ebe135
Diffstat (limited to 'tests/nanobts_omlattr')
| -rw-r--r-- | tests/nanobts_omlattr/nanobts_omlattr_test.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/nanobts_omlattr/nanobts_omlattr_test.c b/tests/nanobts_omlattr/nanobts_omlattr_test.c index 65eb05563..a3ba8e006 100644 --- a/tests/nanobts_omlattr/nanobts_omlattr_test.c +++ b/tests/nanobts_omlattr/nanobts_omlattr_test.c @@ -318,3 +318,4 @@ bool on_gsm_ts_init(struct gsm_bts_trx_ts *ts) { return true; } void ts_fsm_alloc(struct gsm_bts_trx_ts *ts) {} +int rsl_chan_ms_power_ctrl(struct gsm_lchan *lchan) { return 0; } |