diff options
author | Eric Shienbrood <ers@chromium.org> | 2011-08-11 13:58:59 -0400 |
---|---|---|
committer | Dan Williams <dcbw@redhat.com> | 2011-11-16 23:41:49 -0600 |
commit | eede5bb621152eb1774495d9cd403b1e653c076c (patch) | |
tree | d8fc5bfcb140e444aba52f8d64d1738d441ccca6 /introspection/org.freedesktop.ModemManager.Modem.Gsm.xml | |
parent | e7b6b2dc1c709ae877e3cd472d4134b918bb5fb7 (diff) |
gsm: add new property to track which facility locks are enabled
The property EnabledFacilityLocks on the .Modem.Gsm.Card interface
is a bit mask that indicates which of the various personalization
codes from 3GPP TS 22.022, plus the SIM PIN lock and SIM PIN2 lock,
are enabled. The set of facility locks supported by the modem is
determined at the time the modem is initialized, and the state of
each supported lock (enabled or disabled) is determined. When the
state of a lock changes, a property-change signal is sent out. Note
that ModemManager only supports enabling and disabling SIM-PIN, via
the EnablePin method on Modem.Gsm.Card.
Diffstat (limited to 'introspection/org.freedesktop.ModemManager.Modem.Gsm.xml')
-rw-r--r-- | introspection/org.freedesktop.ModemManager.Modem.Gsm.xml | 37 |
1 files changed, 36 insertions, 1 deletions
diff --git a/introspection/org.freedesktop.ModemManager.Modem.Gsm.xml b/introspection/org.freedesktop.ModemManager.Modem.Gsm.xml index 1abf9155..354ce4a3 100644 --- a/introspection/org.freedesktop.ModemManager.Modem.Gsm.xml +++ b/introspection/org.freedesktop.ModemManager.Modem.Gsm.xml @@ -4,7 +4,7 @@ <interface name="org.freedesktop.ModemManager.Modem.Gsm"> <tp:flags name="MM_MODEM_GSM_MODE" value-prefix="MM_MODEM_GSM_MODE" type="u"> <tp:docstring> - A bitfield describing the specifc access modes and technologies + A bitfield describing the specific access modes and technologies supported by a device and the access technology in-use when connected to a mobile network. </tp:docstring> @@ -168,6 +168,41 @@ </tp:enumvalue> </tp:enum> + <tp:flags name="MM_MODEM_GSM_FACILITY" value-prefix="MM_MODEM_GSM_FACILITY" type="u"> + <tp:docstring> + A bitfield describing which facilities have a lock enabled, i.e., + requires a pin or unlock code. The facilities include the + personalizations (device locks) described in 3GPP spec TS 22.022, + and the PIN and PIN2 locks, which are SIM locks. + </tp:docstring> + <tp:flag suffix="NONE" value="0x0"> + <tp:docstring>No facility</tp:docstring> + </tp:flag> + <tp:flag suffix="SIM" value="0x1"> + <tp:docstring>SIM lock</tp:docstring> + </tp:flag> + <tp:flag suffix="FIXED_DIALING" value="0x2"> + <tp:docstring>Fixed dialing (PIN2) SIM lock</tp:docstring> + </tp:flag> + <tp:flag suffix="PH_SIM" value="0x4"> + <tp:docstring>Device is locked to a specific SIM</tp:docstring> + </tp:flag> + <tp:flag suffix="PH_FSIM" value="0x8"> + <tp:docstring>Device is locked to first SIM inserted</tp:docstring> + </tp:flag> + <tp:flag suffix="NET_PERS" value="0x10"> + <tp:docstring>Network personalization</tp:docstring> + </tp:flag> + <tp:flag suffix="NET_SUB_PERS" value="0x20"> + <tp:docstring>Network subset personalization</tp:docstring> + </tp:flag> + <tp:flag suffix="PROVIDER_PERS" value="0x40"> + <tp:docstring>Service provider personalization</tp:docstring> + </tp:flag> + <tp:flag suffix="CORP_PERS" value="0x80"> + <tp:docstring>Corporate personalization</tp:docstring> + </tp:flag> + </tp:flags> </interface> </node> |