uqmi/dev.c, branch master

reorganize source code in common and uqmi specific parts

2024-03-09T20:15:22Z

In preparation to add support for uqmid. Move uqmi specific parts into directory uqmi/. Move common parts used by both uqmid and uqmi into common/ directory. Signed-off-by: Alexander Couzens

move qmi_get_error_str to into utils.c

2024-03-09T20:15:21Z

In prepration to allow uqmid to use it as well. Signed-off-by: Alexander Couzens

dev.c: add missing import strings.h

2024-03-09T20:15:21Z

Fix compiler warning undeclared function. Signed-off-by: Alexander Couzens

dev.c: add comment to qmi_request_wait()

2024-03-09T20:15:21Z

Signed-off-by: Alexander Couzens

uqmi: cancel all requests on SYNC indication reception

2024-01-16T22:18:41Z

A SYNC indication might be sent by the modem on boot as a first response, in order to indicate that all Client IDs have been deallocated. Upon reception of this indication, cancel all current requests, as they will never be answered. Signed-off-by: Jean Thomas

uqmi: improve response detection

2024-01-16T22:18:41Z

Create a helper which checks the flags depending on the service indicated in the received message, as the response flag is not the same for the CTL service and the other services. This avoids considering a CTL indication as a valid response. Also use a mask in order to check the flags, as they are a bitmap. Signed-off-by: Jean Thomas

uqmi: add explicit check for message type when expecting a response

2019-06-27T10:06:56Z

When the utility sends a request it expects a response type message, but does not explicitly check for it. When a device stays idle for some time, it switches into a sleep mode, and notifies the utility with an identification type message. In some configurations the device only sends this identification message when triggered by the utility, in this case by the request message. What the utility gets is two messages at the same time - an identification and a response. When it tries to decode former it obviously fails, because it is not what it expected. Signed-off-by: Tautvydas Belgeras

mbim: fix memory corruption issues

2016-11-22T14:24:18Z

Use a common buffer that has enough headroom for the MBIM header. Signed-off-by: Felix Fietkau

add UIM verify pin commands

2016-11-04T13:25:05Z

Signed-off-by: Felix Fietkau

uqmi: add support for MBIM devices with QMI service

2016-08-23T11:38:27Z

Many Qualcomm based devices offer a QMI service when running in MBIM mode. This is useful for a number of requests which have no MBIM counterpart. This implementation is very basic, simply wrapping the QMI requests in an MBIM command. It is up to the user to make sure that the MBIM command sequence is valid, using a mix of umbim and uqmi requests. umbim must be used to send "OPEN" before uqmi can issue any MBIM requests. Example: 1. use umbim to open the session, using the '-n' option: $ umbim -d /dev/cdc-wdm0 -n caps devicetype: 0003 - remote cellularclass: 0001 voiceclass: 0001 - no-voice simclass: 0002 dataclass: 003C smscaps: 0003 controlcaps: 0001 maxsessions: 0008 deviceid: 0145820007xxxxx firmwareinfo: SWI9X30C_02.08.02.00 hardwareinfo: EM7455 2. use uqmi to send an MBIM request, using the '-m' option: $ uqmi -m -d /dev/cdc-wdm0 --get-serving-system { "registration": "registered", "plmn_mcc": 242, "plmn_mnc": 1, "plmn_description": "TELENOR", "roaming": false } 3. use umbim to close the open session, using the '-t X' option: $ umbim -d /dev/cdc-wdm0 -t 2 caps devicetype: 0003 - remote cellularclass: 0001 voiceclass: 0001 - no-voice simclass: 0002 dataclass: 003C smscaps: 0003 controlcaps: 0001 maxsessions: 0008 deviceid: 0145820007xxxxx firmwareinfo: SWI9X30C_02.08.02.00 hardwareinfo: EM7455 Signed-off-by: Bjørn Mork Signed-off-by: Felix Fietkau [cleanup, portability fixes]