From: Jeff Hugo <jeff.hugo@oss.qualcomm.com>
To: jimmie.lin@gmail.com, Manivannan Sadhasivam <mani@kernel.org>
Cc: mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, daleyo@gmail.com,
Johan Hovold <johan@kernel.org>
Subject: Re: [PATCH RFC v2] bus: mhi: host: pci_generic: Add MBIM-mode config for generic SDX65
Date: Fri, 13 Nov 2026 11:53:51 -0700 [thread overview]
Message-ID: <84fd339d-c8b2-435d-8e3e-648fb4f889cb@oss.qualcomm.com> (raw)
In-Reply-To: <20261110-mhi-sdx65-mbim-rfc-v2-1-f1d71a5ac9ab@gmail.com>
On 11/10/2026 6:06 PM, Haipeng Lin via B4 Relay wrote:
> From: Haipeng Lin <jimmie.lin@gmail.com>
>
> The Surface Pro 11 5G carries an SDX65 that enumerates with Qualcomm's
> generic IDs (17cb:0308, subsystem 17cb:0308) but runs the MBIM-mode
> firmware it ships with for Windows.
>
> Control is MBIM only (the QMI channel never answers), and data on
> channels 100/101 is framed as MBIM NTBs: the modem reports a WDA data
> format of raw IP with MBIM aggregation, up to 32 KiB downlink.
>
> The generic qcom-sdx65m entry names channels 100/101 "IP_HW0", which
> binds mhi_net. mhi_net expects raw IP, so no data session can work.
> The MBIM-mode modules in this driver name them "IP_HW0_MBIM" instead
> which binds mhi_wwan_mbim.
>
> Boards with a Qualcomm-ID modem in MBIM mode have so far been told
> apart by subsystem ID, like the SC8280XP CRD's SDX55 (17cb:010c).
> This modem carries the generic subsystem ID, so select an MBIM
> configuration by machine compatible instead.
I'd like it if we could query the hardware to determine if it is in this
mode as maybe one of these systems has a SDX65 dongle attached where
this workaround does not apply. However, I am failing to identify such
a mechanism so what you have proposed seem to be the best solution so far.
Unless someone identifies a better idea, this seems reasonable given the
situation.
-Jeff
prev parent reply other threads:[~2026-11-13 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 1:06 Haipeng Lin via B4 Relay
2026-11-13 18:53 ` Jeff Hugo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84fd339d-c8b2-435d-8e3e-648fb4f889cb@oss.qualcomm.com \
--to=jeff.hugo@oss.qualcomm.com \
--cc=daleyo@gmail.com \
--cc=jimmie.lin@gmail.com \
--cc=johan@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mhi@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®