| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
The issue referenced was already fixed in GLib 2.43.0.
|
|
|
|
The QmiService enum is a 32bit value, we need to ensure we don't get
unexpected values when trying to create a new message.
|
|
|
|
|
|
|
|
Just style changes, no functional updates.
|
|
Just style changes, no functional updates.
|
|
Using the marker to decide whether the allocation info TLV contains
the 16-bit value is not right, the decision should be exclusively done
based on the message id.
|
|
|
|
|
|
|
|
Handle QMUX and QRTR messages in QMI Message:
- Use QmiService enum instead of guint8
- Handle service ID extraction from QMI message based on marker
- Allow messages with QMUX and QRTR marker
|
|
Handle QMUX and QRTR messages in QMI Message:
- Allow QMI messages with both QMUX and QRTR markers
|
|
|
|
|
|
Handle QMUX and QRTR messages in QMI Message:
- Use QmiService enum instead of guint where possible
- Bump service ID size from guint8 to guint16 when constructing TLVs
- Extract service IDs from QMI messages depending on marker
|
|
Handle QMUX and QRTR messages in QMI Message:
- Add internal calls for CTL service which is handled by QRTR endpoint
- Adjust QMI Device to send internal CTL service messages when services
are out of reach of QMUX compatible endpoints.
|
|
Handle QMUX and QRTR messages in QMI Message:
- Allow QMI messages with both QMUX and QRTR markers
|
|
Handle QMUX and QRTR messages in QMI Message:
- Set a different marker for services > G_MAXUINT8
- Handle different markers in helper methods
- Print QMI Messages differently depending on marker
- Document QMI_MESSAGE_QRTR_MARKER and qmi_message_get_marker
|
|
The SSC service is the Qualcomm Snapdragon Sensor Core (SSC) which is a
remoteproc exposing the sensor devices in the latest Qualcomm SoCs.
The SSC manages the power to the sensors, sample rates, etc. which
can be used over QMI. In contrast to other QMI services, the SSC uses
QMI only as a transport mechamism. The actual messages are Protobuf
messages encoded in the QMI messages and indications.
Therefore, only 1 QMI message is used and 2 QMI indications.
The SSC may emit QMI indications with a small data size or much bigger,
they are indentical besides the data size and ID.
|
|
|
|
|
|
IMS is the IMS Settings service which exposes the settings of various
IMS services such as IMS SMS, IMS Voice, IMS Video Telephony, IMS UE to
TAS, and IMS Video Share. Implement the setting indicators for those
services so we know which services are enabled and which not.
|
|
IMSA is the IMS Application service which exposes the status of various
IMS services such as IMS SMS, IMS Voice, IMS Video Telephony, IMS UE to
TAS, and IMS Video Share. Implement the status indicators for those
services.
|
|
IMSP service is already known by libqmi but without any implementation.
Add the Get Enabler State method to retrieve the IMS registation status.
IMS is split up in multiple services: IMS, IMSA, IMSP, IMSVT, and
IMSRTP. Other IMS services will be added in other patches.
|
|
|
|
Add an action to watch for unsolicited notifications.
To enable the AT communication in the QMI client and get the unsolicited
notifications, it is required to send any initial AT command.
The implementation uses 'ATE0' so that the echo is disabled in the
monitoring client: this could also be useful if the same client cid
is used also for AT commands sending through --atr-send-only to avoid
polluting the monitoring output.
|
|
$ sudo qmicli -d /dev/cdc-wdm0 --atr-send-only="AT+CFUN=1"
Successfully sent AT command
|
|
Add Telit AT Relay Service which can be used for sending AT commands.
The service has a single request for sending the AT command: the reply
arrives asynchronously as an indication.
|
|
|
|
|
|
This allows us to skip needing to include the non-existent
build_string_from_mask() or get_string() counterparts in the
documentation index.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The personalization feature enum in "UIM Card Status" QMI message is
treated differently in QMI modems, and is not same as the existing
'QmiUimCardApplicationPersonalizationFeature' enum. A new enum
'QmiUimCardApplicationPersonalizationFeatureStatus' for the "UIM Card
Status" QMI message is introduced.
The enum change in the QMI message leads to the need of compat symbols
to support API/ABI compatibility. Given that the format and size of
the struct involved in the enum change is the same, i.e. only the
representation of the integer as a different enum changed, we don't
treat the change as a whole TLV rename. Instead, we only change the
struct type that is stored in the GArray/GPtrArray.
We also provide a compat symbol for the UNKNOWN enum name, which the
old enum no longer has.
Originally written by Akash Aggarwal <quic_akasagga@quicinc.com> in
5f366be3000e8c00f7ce73d64606095d3ba4c22e, but later reverted to handle
all the needed compat symbols.
|
|
|
|
|
|
The release buildtype will disable certain warnings that we do see in
debug builds. Ensure we have a test build with all features enabled in
debug mode.
|
|
This reverts commit 5f366be3000e8c00f7ce73d64606095d3ba4c22e.
This change introduced a TLV field type change, and we therefore need
proper compat methods to avoid breaking API/ABI.
|
|
If the common TLV field defines its own 'since' tag, prefer it over
the 'since' tag specified by the message. This supports the rare case
where a TLV format is updated while keeping the original message name
untouched.
Fixes https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/issues/104
|
|
Personalization feature enum in "UIM Card Status" QMI message is treated differently in QMI modem,
and is not same as existing 'QmiUimCardApplicationPersonalizationFeature' enum.
Add new enum 'QmiUimCardApplicationPersonalizationFeatureStatus' for "UIM Card Status" QMI message.
|
|
|
|
|
|
Just to make the compiler happy:
../libqmi-9999/src/qmicli/qmicli-voice.c:71:12: warning: missing field 'short_name' initializer [-Wmissing-field-initializers]
{ NULL }
^
|
