diff options
author | Pau Espin Pedrol <pespin@sysmocom.de> | 2021-09-09 14:21:18 +0200 |
---|---|---|
committer | Pau Espin Pedrol <pespin@sysmocom.de> | 2021-09-09 14:21:21 +0200 |
commit | df93b188ec73191df57dae5f6150c2b20689060a (patch) | |
tree | df32140fa17e804d4a39a958b87ba4ee238b2fc4 /m4 | |
parent | cf9cfb66214c785b6ff155ccd7225ca606665058 (diff) |
lchan_fsm: Avoid inheriting bs_power from old lchan
So far we were inherting the bs_power in used when activating an lchan
for an MS for which we already had previous lchan. For instance, when an
MS is first assigned an SDCCH, and later on, it is assigned a TCH to
place a voice call.
Doing so is, however, not correct because current and old lchans may be
placed on different TS or even on different TRX, which means they will
have different BS Power restrictions. In the scenario described above,
for instance, an SDCCH could have been assigned on C0 and hence have
a bs_power of 0, and later on, whenever the TCH lchan as created, it
would have inherited the C0 bs_power despite it may have been possible
to use a different (lower) max bs power.
Furthermore, the lchan->bs_power_db basically stores the *maximum* bs
power reduction. Hence it makes not sense at all to copy over the value,
since it is anyway not updated from MS measurement reports so far
anyway.
Fixes: 997a257f8dabe5dd940a1271e56e676a871896d7
Related: SYS#4919
Change-Id: I4a7736aa9a1395e0cc118b98b69896bd0f1e94e6
Diffstat (limited to 'm4')
0 files changed, 0 insertions, 0 deletions