aboutsummaryrefslogtreecommitdiffstats
path: root/src/osmo-bts-sysmo/hw_misc.h
diff options
context:
space:
mode:
authorHarald Welte <laforge@gnumonks.org>2012-05-31 23:15:38 +0200
committerHarald Welte <laforge@gnumonks.org>2012-06-01 00:06:58 +0200
commit799ea59c2feeb9fe7ea9e9c202376e973ffca711 (patch)
tree967a162fd8b11b2f078ef65fb27b1e696f0561b7 /src/osmo-bts-sysmo/hw_misc.h
parent700c645478249319dcf7e7e138c13dbbb9c04ba9 (diff)
sysmobts: set the RF ACTIVE LED when we bring RF up
Once we get RF-ACTIVATE.conf from L1, we now enable the corresponding LED. We also switch it off on RF-DEACTIVATE.conf. We do _not_ switch it off when osmo-bts crashes or terminates before RF-DEACTIVATE.conf. The latter is intentional, as RF may very well still be active at that point. The re-spawning script will re-set the DSP and therby turn off the RF and then disable the LED. A better solution might be to do all this in the kernel driver for the DSP.
Diffstat (limited to 'src/osmo-bts-sysmo/hw_misc.h')
-rw-r--r--src/osmo-bts-sysmo/hw_misc.h12
1 files changed, 12 insertions, 0 deletions
diff --git a/src/osmo-bts-sysmo/hw_misc.h b/src/osmo-bts-sysmo/hw_misc.h
new file mode 100644
index 00000000..c4838dbf
--- /dev/null
+++ b/src/osmo-bts-sysmo/hw_misc.h
@@ -0,0 +1,12 @@
+#ifndef _SYSMOBTS_HW_MISC_H
+#define _SYSMOBTS_HW_MISC_H
+
+enum sysmobts_led {
+ LED_NONE,
+ LED_RF_ACTIVE,
+ LED_ONLINE,
+};
+
+int sysmobts_led_set(enum sysmobts_led nr, int on);
+
+#endif