diff options
| author | Neels Hofmeyr <neels@hofmeyr.de> | 2021-08-02 01:41:49 +0200 |
|---|---|---|
| committer | Neels Hofmeyr <neels@hofmeyr.de> | 2021-08-09 17:47:44 +0200 |
| commit | b4ca0a42fe913cf2de5c56a29f7dbbb964d95c43 (patch) | |
| tree | ff8d5aed929f6335af989c5e24c9160432c5388d /tests/power_ctrl.vty | |
| parent | 4bf2297b2f29231e3b4cf61f48ac23ec20753d4c (diff) | |
fix gscon clear 2/n: proper state transition to ST_CLEARING
The way the ST_CLEARING is entered before this patch has various
symptoms of how I / we used osmo_fsm when we were still FSM amateurs in
Osmocom. Patch that up:
- Move all state transitioning into gscon_bssmap_clear().
- In gscon_bssmap_clear(), ask for a state transition to ST_CLEARING
first. If the state transition is allowed, do the Clear Request
messaging in ST_CLEARING's onenter function.
- Fix the timeout behavior: by using conn_fsm_state_chg(), use the
proper X4 timer value from VTY configuration instead of hardcoded
magic numbers in various places.
Change-Id: I234b2a754d0c98031056981823cdbc187e977741
Diffstat (limited to 'tests/power_ctrl.vty')
0 files changed, 0 insertions, 0 deletions