aboutsummaryrefslogtreecommitdiffstats
path: root/src/osmo-bts-trx/loops.h
diff options
context:
space:
mode:
authorPau Espin Pedrol <pespin@sysmocom.de>2019-11-05 12:41:28 +0100
committerPau Espin Pedrol <pespin@sysmocom.de>2019-11-12 14:19:08 +0100
commit80f2bc4855ea101e0bc95a86cf9a49ad1f1c9026 (patch)
tree8a9a94b7fcca6c700ef6fc952c7346ef0b54e712 /src/osmo-bts-trx/loops.h
parent000b13ef523f3d5f3b77f649ea129b1e59095381 (diff)
bts-trx: Implement MS Power control loop calculations using dBm instead of ctl levels
Some bands, such as DCS1800, contain power levels such as 29, 30 and 31 not following same unified sequence other power levels follow regarding conversion to dBm values. This makes extremly complex and prone to error comparing different power levels. Let's instead use dBm values to calculate and crop desired new value, and then convert it back to TS 05.05 ms power control level value. With this commit the control loop should be able to manage correctly the MS power levels explained above. Related: OS#4244 Change-Id: I0160637c5ffa606ee3081ad30be8e6f2a42b725b
Diffstat (limited to 'src/osmo-bts-trx/loops.h')
-rw-r--r--src/osmo-bts-trx/loops.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/osmo-bts-trx/loops.h b/src/osmo-bts-trx/loops.h
index 0db01d76..78699031 100644
--- a/src/osmo-bts-trx/loops.h
+++ b/src/osmo-bts-trx/loops.h
@@ -8,8 +8,8 @@
*/
/* how much power levels do we raise/lower as maximum (1 level = 2 dB) */
-#define MS_RAISE_MAX 4
-#define MS_LOWER_MAX 2
+#define MS_RAISE_MAX_DB 4
+#define MS_LOWER_MAX_DB 8
/*
* loops api