diff options
| author | Steve Meek <stevemeek82@gmail.com> | 2026-10-11 08:40:49 +0100 |
|---|---|---|
| committer | Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com> | 2026-10-11 21:52:07 +0530 |
| commit | f6985f512f82757f4aad13bad87039c9190b1466 (patch) | |
| tree | 4cd249da506300331c8f0b86c5bc6c7f3361b6f4 /tools/perf/scripts/python/stackcollapse.py | |
| parent | 710bf7329abf86e37db529f19c8f394099238892 (diff) | |
| download | linux-next-f6985f512f82757f4aad13bad87039c9190b1466.tar.gz linux-next-f6985f512f82757f4aad13bad87039c9190b1466.zip | |
bus: mhi: host: pci_generic: Add Quectel RM500Q-AE support
The Quectel RM500Q-AE (SDX55) enumerates with the Qualcomm SDX55 ID
17cb:0306 and subsystem ID 17cb:5002, so it binds to the generic
qcom-sdx55m entry. That configuration expects QMI on channels 14/15,
which this module's firmware does not answer: the modem probes, but
every QMI request over the control channel times out and no data
session can be set up. Users of this module have had to fall back to
Quectel's out-of-tree driver.
Like the other Quectel modules, the RM500Q-AE provides MBIM control on
channels 12/13 and data on IP_HW0_MBIM. Add an entry for its subsystem
ID, which no other entry in the table uses, that reuses the Quectel
em1xx channel configuration. The EDL image name is the one the generic
SDX55 entry already uses.
Tested on a Xunison Exigo D50 5G (IPQ5018) with modem firmware
RM500QAEAAR13A03M4G: the modem probes as quectel-rm500q and exposes
wwan0mbim0, wwan0at0 and an MBIM network device. A data session set up
with mbimcli and with OpenWrt's umbim reached 160-180 Mbps, the
limit of the cell.
Assisted-by: LLM
Signed-off-by: Steve Meek <stevemeek82@gmail.com>
Link: https://patch.msgid.link/20261011-mhi-next-v1-1-13a738637ff0@gmail.com
Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions
