aboutsummaryrefslogtreecommitdiffstats
path: root/include/osmocom/bsc/bts.h
diff options
context:
space:
mode:
authorHarald Welte <laforge@osmocom.org>2020-12-20 23:53:24 +0100
committerlaforge <laforge@osmocom.org>2021-01-02 22:47:18 +0000
commitc77cea43ee237326114da5cbadd3780d70f17172 (patch)
tree286c3f051892008785ad7788b54a31b08c7a4b3d /include/osmocom/bsc/bts.h
parentcde3d1f29cd65211f58c683e4506944a5a807ce6 (diff)
abis_om2000: keep OM2K FSMs around, don't terminate
The existing code uses short-lived FSMs which are allocated straight before START, and which are free'd after DONE state is reached. While that works, it makes state introspection a bit hard, as one cannot show the FSM states, etc. Let's change to a different model where the per-OM2k-MO FSMs are always around (in state INIT after object creation). While at it, also introduce a RESET event that can reset each FSM instance back to INIT state, i.e. in case of OML link failure. Change-Id: Ia37cffff5c451e1d79a52ccae41ab5718b4661d4
Diffstat (limited to 'include/osmocom/bsc/bts.h')
-rw-r--r--include/osmocom/bsc/bts.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/osmocom/bsc/bts.h b/include/osmocom/bsc/bts.h
index aef0e0384..c79e7f7f4 100644
--- a/include/osmocom/bsc/bts.h
+++ b/include/osmocom/bsc/bts.h
@@ -316,6 +316,7 @@ struct gsm_bts {
struct gsm_envabtse envabtse[4];
} bs11;
struct {
+ struct osmo_fsm_inst *bts_fi;
struct {
struct om2k_mo om2k_mo;
struct gsm_abis_mo mo;