aboutsummaryrefslogtreecommitdiffstats
path: root/src/osmo-bts-sysmo/hw_misc.h
diff options
context:
space:
mode:
authorPau Espin Pedrol <pespin@sysmocom.de>2019-10-08 18:30:43 +0200
committerpespin <pespin@sysmocom.de>2019-10-16 11:13:21 +0000
commit8ff35d3c9117b2abdbcca03d9400dde21157417b (patch)
tree35b5dd5b55aca461f9ef241e5b29379656ebd42c /src/osmo-bts-sysmo/hw_misc.h
parent5fee4d1ff5fac53bc21ed19abf2f84456486fa44 (diff)
bts-trx: Time out if no clock ind recvd after RSP POWERONHEADmaster
Before this patch, if due to whatever reason the TRX started fine (RSP POWERON 0) and sockets were created but no CLOCK IND was ever received by the BTS, it wouldn't notice since the timerfd timeouts (bts_shutdown("no clock")) are only checked after the first CLOCK IND is sent by the TRX. As a result, the BTS would be kept on forever saying everything is fine but it would be sending no DL burst at all to the TRX (tested with a modfied osmo-trx dropping clock indication). With this patch, new APIs are added to indicate the scheduler_trx code the timeframes where clock ind are expected (between RSP POWERON 0 and RSP POWEROFF 0); if TRX sends clock indications out of that timeframe, BTs lower layers will drop them (controlled by "powered" bool). Hence, the scheduler_trx can now place a timeout (reusing same timerfd because its new use is exclusive in time with its other previous use) when it is told that CLOCK IND should start appearing, and if none arrives in considerable time, then the BTS can be shut down to notify the rest of the network. Related: OS#4215 Change-Id: Iba5dbe867aff10e70ec73dbf1f7aeeecb15c0a4d
Diffstat (limited to 'src/osmo-bts-sysmo/hw_misc.h')
0 files changed, 0 insertions, 0 deletions