api,simple: new 'multiplex' setting in bearer properties
Both the Simple.Connect() and Modem.CreateBearer() are updated to allow a new 'multiplex' setting in the properties provided by the user in both of these methods. The new setting expects a MMBearerMultiplexSupport enum indicating what kind of multiplex needs the user has: * none: if multiplex must not be used. * requested: if multiplex should be used if available. * required: if multiplex must be used. The underlying implementations will take care of accepting or rejecting the setting depending on the system and modem capabilities.
This commit is contained in:
@@ -1526,4 +1526,22 @@ typedef enum { /*< underscore_name=mm_modem_firmware_update_method >*/
|
||||
MM_MODEM_FIRMWARE_UPDATE_METHOD_QMI_PDC = 1 << 1,
|
||||
} MMModemFirmwareUpdateMethod;
|
||||
|
||||
/**
|
||||
* MMBearerMultiplexSupport:
|
||||
* @MM_BEARER_MULTIPLEX_SUPPORT_UNKNOWN: Unknown.
|
||||
* @MM_BEARER_MULTIPLEX_SUPPORT_NONE: No multiplex support should be used.
|
||||
* @MM_BEARER_MULTIPLEX_SUPPORT_REQUESTED: If available, multiplex support should be used.
|
||||
* @MM_BEARER_MULTIPLEX_SUPPORT_REQUIRED: Multiplex support must be used or otherwise the connection attempt will fail.
|
||||
*
|
||||
* Multiplex support requested by the user.
|
||||
*
|
||||
* Since: 1.18
|
||||
*/
|
||||
typedef enum { /*< underscore_name=mm_bearer_multiplex_support >*/
|
||||
MM_BEARER_MULTIPLEX_SUPPORT_UNKNOWN = 0,
|
||||
MM_BEARER_MULTIPLEX_SUPPORT_NONE = 1,
|
||||
MM_BEARER_MULTIPLEX_SUPPORT_REQUESTED = 2,
|
||||
MM_BEARER_MULTIPLEX_SUPPORT_REQUIRED = 3,
|
||||
} MMBearerMultiplexSupport;
|
||||
|
||||
#endif /* _MODEMMANAGER_ENUMS_H_ */
|
||||
|
Reference in New Issue
Block a user