RFC: Workaround for newest QMI devices that require arguments in "WDA Get Data Format"

[Reinhard Speyerer]

On Tue, Jan 28, 2020 at 11:36:04AM +0100, Aleksander Morgado wrote:
> Hey!
> 
> On Tue, Jan 28, 2020 at 11:04 AM Aleksander Morgado
> <aleksander at aleksander.es> wrote:
> >
> > Hey!
> >
> > >
> > > perhaps these devices now need an "Endpoint Info" TLV for "WDA Get Data Format"
> > > too similar to what is used with "WDA Set Data Format" and QMAP MUXing?
> > >
> >
> > I got the same suggestion off-list from another person, I'll try to
> > prepare a patch to test.
> >
> 
> I've prepared the following MR that upgrades the --wda-get-data-format
> qmicli command to allow optional key=value pair arguments, so now we
> can also do:
> $ qmicli -d /dev/cdc-wdm1 -p
> --wda-get-data-format="ep-type=hsusb,ep-iface-number=0"
> 
> Could anyone give this a try with one of the new 5G modules?
> 
> https://gitlab.freedesktop.org/mobile-broadband/libqmi/merge_requests/91
>

Hi Aleksander,

can't use the RG500Q with qmicli at the moment but (assuming that I interpreted
the changes correctly) does not work for me with another QMI client.

Quoting from the above link: "This is a WILD guess, just reusing the same TLV
id (0x17) as the SET command."

$ sqmuxdqwa -p 4200 -w 4 /dev/cdc-wdm0&
[12] 16590
+OK sqmuxdqwa 1.60 (Kleinkunst) connected to /dev/cdc-wdm0, QMI service(s) 0:1.5,1:1.175,2:1.69,3:1.25,4:1.16,5:1.10,7:1.13,8:1.6,9:2.1,10:2.24,11:1.77,12:1.4,15:1.0,16:2.115,17:1.0,18:1.82,20:1.0,23:1.0,24:1.0,26:1.23,29:1.6,33:1.36,34:1.0,36:1.0,41:1.0,42:1.60,48:1.11,49:1.0,68:1.3,73:1.7,74:1.0,75:1.3,76:1.0,77:1.2,78:1.2, listen port 4200, protocol QMUXD
$ gobicmapicli -g ~/lib/gobicmapi/GobiConnectionMgmt/GobiConnectionMgmt.so SOCKET:TCP:127.0.0.1:4200,0 1 2 3 5 7 9 11 26
+OK gobicmapicli 2.25 connected to SOCKET:TCP:127.0.0.1:4200,0, QMI service(s) 1,2,3,5,7,9,11,26
WDAGetDataFormat 3000
-ERR WDAGetDataFormat error 1017 02040001001100
WDAGetDataFormat 3000 1708000200000004000000
-ERR WDAGetDataFormat error 1017 02040001001100
WDAGetDataFormat 3000 0108000200000004000000
-ERR WDAGetDataFormat error 1058 02040001003a00
WDAGetDataFormat 3000 1008000200000004000000
+OK WDAGetDataFormat 02040000000000100100001104000200000012040000000000130400000000001404000000000015040000000000160400000000001a0400000000001b010000
quit
+OK gobicmapicli disconnected from SOCKET:TCP:127.0.0.1:4200,0

All of this might be much less guesswork if the CodeAurora folks would update
https://portland.source.codeaurora.org/quic/qsdk/oss/lklm/gobinet/tree/GobiConnectionMgmt
with the changes relevant to the functionality covered by TS 27.005/TS 27.007
and release a 2020 version of the Gobi API if only for reference purposes...

Regards,
Reinhard