summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorAleksander Morgado <aleksander@aleksander.es>2022-02-09 15:39:44 +0100
committerAleksander Morgado <aleksander@aleksander.es>2022-03-07 09:51:43 +0000
commit343f27a5e7b0226e10aec025c502703d0be9d1ac (patch)
tree01d128828e4ebb7416614d1a2e190c870429f82a /include
parentdeaf0646c4a3da4a1dc3a1bfd4157cc0ee74921f (diff)
downloadModemManager-343f27a5e7b0226e10aec025c502703d0be9d1ac.tar.gz
api: allow tagging AT ports as GPS control
There are devices with multiple AT ports where only one of them is supposed to be used for GNSS control (and data).
Diffstat (limited to 'include')
-rw-r--r--include/ModemManager-tags.h13
1 files changed, 13 insertions, 0 deletions
diff --git a/include/ModemManager-tags.h b/include/ModemManager-tags.h
index ec7814262..ad813b155 100644
--- a/include/ModemManager-tags.h
+++ b/include/ModemManager-tags.h
@@ -130,6 +130,19 @@
#define ID_MM_PORT_TYPE_AT_SECONDARY "ID_MM_PORT_TYPE_AT_SECONDARY"
/**
+ * ID_MM_PORT_TYPE_AT_GPS_CONTROL:
+ *
+ * This is a port-specific tag applied to TTYs that we know in advance
+ * are AT ports to be used for GPS control. Depending on the device,
+ * this may or may not mean the same port is also used fo GPS data.
+ *
+ * This tag will also proevent QCDM probing on the port.
+ *
+ * Since: 1.20
+ */
+#define ID_MM_PORT_TYPE_AT_GPS_CONTROL "ID_MM_PORT_TYPE_AT_GPS_CONTROL"
+
+/**
* ID_MM_PORT_TYPE_AT_PPP:
*
* This is a port-specific tag applied to TTYs that we know in advance