Hi, I’m trying to use the EM919x connected to a i.MX6DualLite through the PCIe gen2 bus, but for the moment without success, could you help me ? I’m following two approaches: Use the Sierra driver R21 with on the kernel 5.4 Use the upstream MHI driver on the kernel 5.13 QMI and MBIM are exposed…

We got that firmware version from our distributor, it has been released end of August.

[image] thomas.perrot: +static const struct mhi_pci_dev_info mhi_sierra_em919x_info = { + .name = "sierra-em919x", + .config = &modem_sierra_em919x_config, + .bar_num = MHI_PCI_DEFAULT_BAR_NUM, + .dma_data_width = 32, + .sideband_wake = true, +}; Shouldn’t sideba…

[image] thomas.perrot: But these random issues seem linked to I.MX6DL MSI vector limitation because when we restrain the number of MSI vectors on the X86-64 setup, we observe same issues. How many are you able to allocate? In my setup I’m using one single shared MSI vector; it tries to alloca…

Hello @aleksander0m , Our i.MX6 setup also are using one single shared MSI vector. On x86-64, with the MBPL Sierra driver 8 share MSI vector are used, and if we limit to 1 we observe same kinds of issues as on i.MX6DL, but to a lesser extent probably because x86-64 provides a PCIe gen3 bus and not…

[image] thomas.perrot: Your i.MX6 setup also are using one single shared MSI vector. This is a RaspberryPi CM4 (Broadcom BCM2711), not the good old i.MX6 :wink:

There’s something fishy here; I’ve now tested with the PCI_DEVICE_SUB() line before the generic one for the 0x0306, and also after it (as you have it); and in both cases, it’s not picking the EM919x speciifc config, it’s always reporting MHI PCI device found: qcom-sdx55m. Until now I’ve also been t…

[image] aleksander0m: Until now I’ve also been testing with a hack to make sure the correct one was being picked (changing the default one to 0x03ff and making the EM919x the only one for 0x0306). But if I go back to PCI_DEVICE_SUB(), it never gets picked any more. Hello @aleksander0m , Yes,…

[image] thomas.perrot: Yes, from my side, I also use a hack for the moment, because my EM919x didn’t provide right svid and sdev. To fix this issue it is necessary to use PCI_DEVICE_SUB instead PCI_DEVICE to define the first entry. You mean we also need to use PCI_DEVICE_SUB() for the non-Sie…

[image] aleksander0m: Does the new PCI_DEVICE_SUB() line really take precedence over the previous PCI_DEVICE() entry for the same 0x0306 device id? (Just wondering) No, it doesn’t. The list is parsed sequentially and a PCI_DEVICE() entry will match any subdevice. See https://git.kernel.org…

[image] dl5162: No, it doesn’t. The list is parsed sequentially and a PCI_DEVICE() entry will match any subdevice. That’s what I assumed when I first read the patch, yes. And I tested yesterday having the more specific PCI_SUB_DEVICE before the generic PCI_DEVICE entry, and for some reason i…

Sierra Wireless AirPrime EM919x PCIe support

IoT Modules

dl5162 October 20, 2021, 1:06pm 21

Yes, that’s unexpected. I assume you had a clean dynamic device id list? And no typos? Stupid question, I know. But that’s just the kind of error I would do…

Topic		Replies	Views
Setting up EM9291 Module IoT Modules faq , driver	35	403	May 1, 2026
PCIe Drivers for EM9191 MC/EM Series	15	4914	February 12, 2022
Sierra EM9291 module not enumerating as a usb device on imx93 debug , driver	7	73	January 30, 2026
EM9190 usbcomp settings IoT Modules	7	3263	March 10, 2021
EM9190 not being detected in Linux Ubuntu 20.04.5 EM9191 EM7690 5G dev kit MC/EM Series feature-request , debug , iot-cards , faq , driver	31	3605	November 21, 2022

Sierra Wireless AirPrime EM919x PCIe support

Related topics