diff options
| author | Holger Hans Peter Freyther <holger@moiji-mobile.com> | 2014-08-21 23:51:13 +0200 |
|---|---|---|
| committer | Holger Hans Peter Freyther <holger@moiji-mobile.com> | 2014-08-21 23:55:27 +0200 |
| commit | 1f8053e366c9d0f4ab7160595a3cb1ead915e0d6 (patch) | |
| tree | e10f2099acc0f5204feff094df0fe75b4c9c3061 /src/osmo-bts-sysmo/misc/sysmobts_misc.h | |
| parent | e02d7796c3cb4eaeca679286bc6db12b9b2c070b (diff) | |
sysmobts: Enable the PA on start and disable it as first action
The PA will be unconditionally turned. This makes it possible
that in case of a crash, the PA will be turned on and then we
will do the temperature measurement and turn it off again. There
are no known crashes with the sysmobts-mgr right now so the risk
seems to be okay. In case we can't switch off the PA we have no
way to escalate it right now. We have not seen a dead uc either
so the risk is okay as well.
We can't switch the PA back on once we reach the normal level
as the BTS might transmit with full power and we would need more
current than the power supply/rails can carry. So leave the
system off right now.
What is missing is to use the OML router to actually inform
the BSC that something bad has happened at the BTS.
Diffstat (limited to 'src/osmo-bts-sysmo/misc/sysmobts_misc.h')
| -rw-r--r-- | src/osmo-bts-sysmo/misc/sysmobts_misc.h | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/src/osmo-bts-sysmo/misc/sysmobts_misc.h b/src/osmo-bts-sysmo/misc/sysmobts_misc.h index 28b6e628..8a6337e2 100644 --- a/src/osmo-bts-sysmo/misc/sysmobts_misc.h +++ b/src/osmo-bts-sysmo/misc/sysmobts_misc.h @@ -56,8 +56,9 @@ struct sbts2050_power_status { }; int sbts2050_uc_check_temp(int *temp_pa, int *temp_board); -void sbts2050_uc_set_power(int pmaster, int pslave, int ppa); +int sbts2050_uc_set_power(int pmaster, int pslave, int ppa); int sbts2050_uc_get_status(struct sbts2050_power_status *status); +int sbts2050_uc_set_pa_power(int on_off); void sbts2050_uc_initialize(); #endif |