<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="#467886" vlink="#96607D" style="word-wrap:break-word"> <div class="WordSection1"> Thanks for the response!<o:p></o:p> <o:p> </o:p> Not having much insight of the PCIe driver, but it looks like it exposed different port for qmi. <o:p></o:p> It’s /dev/ mhi_0308_01.01.00_pipe_14 instead of /dev/wwan0qmi0. <o:p></o:p> I think the driver is mhi_netdev. <o:p></o:p> This is the output of lspci of the device: 0001:01:00.0 Unassigned class [ff00]: Qualcomm Technologies, Inc Device 0308<o:p></o:p> Subsystem: Device 18d7:0301<o:p></o:p> Flags: bus master, fast devsel, latency 0, IRQ 57<o:p></o:p> Memory at e0100000 (64-bit, non-prefetchable) [size=4K]<o:p></o:p> Memory at e0101000 (64-bit, non-prefetchable) [size=4K]<o:p></o:p> Capabilities: [40] Power Management version 3<o:p></o:p> Capabilities: [50] MSI: Enable+ Count=4/32 Maskable+ 64bit+<o:p></o:p> Capabilities: [70] Express Endpoint, MSI 00<o:p></o:p> Capabilities: [100] Advanced Error Reporting<o:p></o:p> Capabilities: [148] Secondary PCI Express<o:p></o:p> Capabilities: [168] Physical Layer 16.0 GT/s <?><o:p></o:p> Capabilities: [18c] Lane Margining at the Receiver <?><o:p></o:p> Capabilities: [19c] Transaction Processing Hints<o:p></o:p> Capabilities: [228] Latency Tolerance Reporting<o:p></o:p> Capabilities: [230] L1 PM Substates<o:p></o:p> Capabilities: [240] Data Link Feature <?><o:p></o:p> Kernel driver in use: mhictrl<o:p></o:p> Kernel modules: mhi_pci_generic, mhictrl<o:p></o:p> <o:p> </o:p> My experience of using libqmi with the current qmi port of EM9293, is that most of the qmicli command works properly, except during `qmi-network start` command, it failed with:<o:p></o:p> <o:p> </o:p> Getting expected data format with 'qmicli --device-open-qmi -d /dev/mhi_0308_01.01.00_pipe_14 --get-expected-data-format'...<o:p></o:p> [01 May 2024, 00:59:10] -Warning ** [/dev/mhi_0308_01.01.00_pipe_14] couldn't detect transport type of port: unexpected port subsm<o:p></o:p> [01 May 2024, 00:59:10] -Warning ** [/dev/mhi_0308_01.01.00_pipe_14] requested QMI mode but unexpected transport type found<o:p></o:p> error: cannot get expected data format: Setting expected data format management is unsupported by the driver<o:p></o:p> Expected link layer protocol not retrieved: kernel unsupported<o:p></o:p> <o:p> </o:p> Subsequently, the command to start the network, wds-start-network, failed.<o:p></o:p> <o:p> </o:p> Any thoughts?<o:p></o:p> <o:p> </o:p> Best regards,<o:p></o:p> Leo<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <div id="mail-editor-reference-message-container"> <div> <div> Juniper Business Use Only <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"> From: Aleksander Morgado <aleksandermj@chromium.org> Date: Tuesday, October 1, 2024 at 2:26 PM To: Leo Liu <lliu@juniper.net> Cc: libqmi-devel@lists.freedesktop.org <libqmi-devel@lists.freedesktop.org> Subject: Re: Pci-e device support<o:p></o:p> </div> <div> [External Email. Be cautious of content] Hey, > > I have another question. What is the status of libqmi supporting pci-e device? The reason I ask is that we have a EM9293 Sierra modem with pcie connection type. > > > > Using libqmi-1.32.2 on el9, it doesn’t seem to work properly. From the source codes of (1.30.8), it seems a lot of the codes are expecting USB type of driver/device. > > > > Is this true? > There is nothing in libqmi that prevents it from being used with PCI devices, as long as the device is correctly managed by the kernel drivers. E.g. For the EM9293 in PCIe mode, I would assume the corresponding support needs to exist in the mhi kernel driver, and if that's the case, then we would expect to see a /dev/wwan0qmi0 port exposed. This port can be used with libqmi/qmicli without issues. How is it not working properly in your case? -- Aleksander<o:p></o:p> </div> </div> </div> </div> </div> </body> </html>