mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Haipeng Lin <jimmie.lin@gmail.com>
To: Jeff Hugo <jeff.hugo@oss.qualcomm.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: Mon, 16 Nov 2026 22:08:34 -0500	[thread overview]
Message-ID: <93f7aabc-4a92-4d3c-a6af-a84b461c0e0c@gmail.com> (raw)
In-Reply-To: <84fd339d-c8b2-435d-8e3e-648fb4f889cb@oss.qualcomm.com>

On 11/13/26 1:53 PM, Jeff Hugo wrote:
> On 11/10/2026 6:06 PM, Haipeng Lin via B4 Relay wrote:
>> From: Haipeng Lin <jimmie.lin@gmail.com>
[...]>> 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

Hi Jeff,

Thank you for your reply. I tried to look for a hardware hint since we
have to select the channel layout before opening a channel (so that
can't be the way to select MBIM, I think). The oem_pk_hash on this SP11
SDX65 is non-zero (12 words) so it could potentially tell this module
apart from a dongle, but using it would mean reading BHI before the
controller is registered plus adding a table of hashes in the driver.

I can try the hash route if preferred. The machine match is simpler
although it wouldn't cover the situation e.g., a SDX65 dongle is attach-
ed via PCIe tunneling/USB4 you mentioned...

Best,
Haipeng


      reply	other threads:[~2026-11-17  3:08 UTC|newest]

Thread overview: 3+ 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
2026-11-17  3:08   ` Haipeng Lin [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=93f7aabc-4a92-4d3c-a6af-a84b461c0e0c@gmail.com \
    --to=jimmie.lin@gmail.com \
    --cc=daleyo@gmail.com \
    --cc=jeff.hugo@oss.qualcomm.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®