aboutsummaryrefslogtreecommitdiffstats
path: root/include/osmo-bts
diff options
context:
space:
mode:
authorVadim Yanitskiy <vyanitskiy@sysmocom.de>2022-04-14 01:19:43 +0300
committerVadim Yanitskiy <vyanitskiy@sysmocom.de>2022-08-18 16:11:03 +0700
commit016c8b616df0447ba151f7b24294fe16cf18fe79 (patch)
tree233545b37ffc01b15e57b06dd741801704ee1ea1 /include/osmo-bts
parent2baf54dd468d4b2366c809051231b935f305ad2b (diff)
osmo-bts-trx: amr_loop: trigger the loop unconditionally2022q2
The logic responsible for enabling and disabling the loop appears to be broken: during my experiments trx_loop_amr_set() was never called with loop=1. It's not clear what's the motivation behind this breaker, so I propose to rip it out for now. This patch finally makes the loop work (confirmed with a TEMS phone). Related: SYS#5917, OS#4984 Change-Id: I09b649973d4269c4082a4fafa493c37825f95a9c (cherry picked from commit 541b7525aee81fbeed23be9cddf909ebcca6ed6d)
Diffstat (limited to 'include/osmo-bts')
-rw-r--r--include/osmo-bts/scheduler.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/include/osmo-bts/scheduler.h b/include/osmo-bts/scheduler.h
index ec31eab9..c96b70b4 100644
--- a/include/osmo-bts/scheduler.h
+++ b/include/osmo-bts/scheduler.h
@@ -119,7 +119,6 @@ struct l1sched_chan_state {
uint8_t dl_ft; /* current downlink FT index */
uint8_t ul_cmr; /* current uplink CMR index */
uint8_t dl_cmr; /* current downlink CMR index */
- uint8_t amr_loop; /* if AMR loop is enabled */
uint8_t amr_last_dtx; /* last received dtx frame type */
/* TCH/H */