osmo-bts/src
Pau Espin 0468376c53 Move TA & Power Loops further up the stack, take DTXu flag into account
Only once we receive the Measurement Result on L3 from MS we are able to
find out whether DTXu was used, and hence whether SUB or FULL
measurement set should be used.

Let's move all control loops there to have them in one place together,
and have it at a similar level where it would lay if it was to be
implemented in the BSC.

Related: SYS#4917
Change-Id: Ic152473577ff7c33d30b3f4ee7e321fcb523f723
2021-09-28 12:02:15 +02:00
..
common Move TA & Power Loops further up the stack, take DTXu flag into account 2021-09-28 12:02:15 +02:00
osmo-bts-lc15 nm_*fsm: Make FSMs aware of object being properly configured or not 2021-09-22 12:56:58 +02:00
osmo-bts-oc2g nm_*fsm: Make FSMs aware of object being properly configured or not 2021-09-22 12:56:58 +02:00
osmo-bts-octphy nm_*fsm: Make FSMs aware of object being properly configured or not 2021-09-22 12:56:58 +02:00
osmo-bts-omldummy nm_*fsm: Make FSMs aware of object being properly configured or not 2021-09-22 12:56:58 +02:00
osmo-bts-sysmo nm_*fsm: Make FSMs aware of object being properly configured or not 2021-09-22 12:56:58 +02:00
osmo-bts-trx bts-trx: Fix rxgain & maxdly VTY values being reset 2021-09-27 20:20:18 +02:00
osmo-bts-virtual nm_*fsm: Make FSMs aware of object being properly configured or not 2021-09-22 12:56:58 +02:00
Makefile.am osmo-bts-lc15: use consistent name for containing directory 2020-11-05 03:39:50 +07:00