modemmanager: Add a reason to ConnectionStateChanged events.

introspection/mm-modem.xml

Index: introspection/mm-modem.xml
diff --git a/introspection/mm-modem.xml b/introspection/mm-modem.xml
index 484619e98bf8466f11e1dc42fcd497fe3cd19987..e6440a5105045d859e1ead52558bf413c98d15a9 100644
--- a/introspection/mm-modem.xml
+++ b/introspection/mm-modem.xml
@@ -101,6 +101,11 @@
           True if the modem is connected; false otherwise.
         </tp:docstring>
       </arg>
+      <arg name="reason" type="u" tp:type="MM_MODEM_CONNECTION_STATE_CHANGED_REASON">
+        <tp:docstring>
+          Reason for this state change.
+        </tp:docstring>
+      </arg>
     </signal>
 
     <property name="Device" type="s" access="read">
@@ -198,5 +203,24 @@
       </tp:enumvalue>
     </tp:enum>
 
+    <tp:enum name="MM_MODEM_CONNECTION_STATE_CHANGE_REASON" type="u">
+      <tp:enumvalue suffix="UNKNOWN" value="0">
+        <tp:docstring>
+          Reason unknown or not reportable.
+        </tp:docstring>
+      </tp:enumvalue>
+      <tp:enumvalue suffix="REQUESTED" value="1">
+        <tp:docstring>
+          Connection state change was requested by an interface user.
+        </tp:docstring>
+      </tp:enumvalue>
+      <tp:enumvalue suffix="SUSPEND" value="2">
+        <tp:docstring>
+          Connection state change was caused by a system suspend.
+        </tp:docstring>
+      </tp:enumvalue>
+    </tp:enum>
+
+
   </interface>
 </node>