From: "Juha-Matti Tilli" <juha-matti.tilli@iki.fi>
To: "Manivannan Sadhasivam" <manivannan.sadhasivam@oss.qualcomm.com>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Jeff Johnson" <jjohnson@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
ath11k@lists.infradead.org, ath12k@lists.infradead.org,
"Bjorn Andersson" <andersson@kernel.org>,
"Chris Lew" <christopher.lew@oss.qualcomm.com>,
"Deepak Kumar Singh" <deepak.singh@oss.qualcomm.com>,
"Raj Kumar Bhagat" <raj.bhagat@oss.qualcomm.com>,
"Jeff Hugo" <jeff.hugo@oss.qualcomm.com>,
"Mihai Moldovan" <ionic@ionic.de>,
david@3adesign.co.uk, nakonechnij.sergsj@gmail.com
Subject: Re: [PATCH 4/4] wifi: ath12k: Connect to the QMI server belonging to the device owned by this driver
Date: Fri, 18 Sep 2026 19:51:33 +0300 [thread overview]
Message-ID: <cb6766f8-54b9-435f-a69a-e712727dabdb@app.fastmail.com> (raw)
In-Reply-To: <20260918-qrtr-multi-ep-v1-4-8a06caa368d3@oss.qualcomm.com>
On Fri, Sep 18, 2026, at 19:28, Manivannan Sadhasivam via B4 Relay wrote:
> From: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
>
> When two identical ath12k PCIe devices are connected to the same host, both
> advertise the WLFW service with the same service and instance id. The QMI
> lookup reports both servers to each device, so a device may connect to the
> firmware running on the other device.
>
> But now, QRTR provides each MHI endpoint a unique node id which is
> different from the node id announced by the device. So use the same id to
> pick the correct server. Add a get_qrtr_node_id() HIF callback that returns
> the node id derived from the MHI controller index and zero for transports
> that do not assign one. In the new_server callback, skip any service whose
> node id does not match. A node id of zero disables the check, so transports
> that do not assign one keep their current behavior.
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
CC'ing Mihai. He is known to have a platform with two ath12k cards,
but he said he's been busy recently, so his testing input is uncertain.
Also David and Serhii have found the bug at Bugzilla and may
be able to help with testing. (CC'ing them too)
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=218480
Here's the patchset in an easier-to-access format:
https://github.com/Mani-Sadhasivam/linux/commits/qrtr-multi-ep/
Also, I have suggested that at $DAYJOB we'd switch to a newer LTS kernel
with better ath12k support. This may take some time, but there is a
possibility I'll be able to finally get ath12k cards working. This might
allow me to test this with ath12k cards, porting the patches to 6.12 or
6.18 kernel. But that will take time (the kernel switch; backporting is
easy for such simple patches).
BR, Juha-Matti
next prev parent reply other threads:[~2026-09-18 16:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 16:28 [PATCH 0/4] net: qrtr: Add support for using identical MHI endpoint devices Manivannan Sadhasivam via B4 Relay
2026-09-18 16:28 ` [PATCH 1/4] net: qrtr: Allow the host QRTR to assign a unique node id Manivannan Sadhasivam via B4 Relay
2026-09-18 16:28 ` [PATCH 2/4] net: qrtr: Assign unique node id for MHI endpoints Manivannan Sadhasivam via B4 Relay
2026-09-18 16:28 ` [PATCH 3/4] wifi: ath11k: Connect to the QMI server belonging to the device owned by this driver Manivannan Sadhasivam via B4 Relay
2026-09-18 16:39 ` Juha-Matti Tilli
2026-09-18 16:28 ` [PATCH 4/4] wifi: ath12k: " Manivannan Sadhasivam via B4 Relay
2026-09-18 16:51 ` Juha-Matti Tilli [this message]
2026-09-19 15:45 ` Mihai Moldovan
2026-09-18 18:13 ` [PATCH 0/4] net: qrtr: Add support for using identical MHI endpoint devices Jeff Johnson
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=cb6766f8-54b9-435f-a69a-e712727dabdb@app.fastmail.com \
--to=juha-matti.tilli@iki.fi \
--cc=andersson@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=christopher.lew@oss.qualcomm.com \
--cc=davem@davemloft.net \
--cc=david@3adesign.co.uk \
--cc=deepak.singh@oss.qualcomm.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=ionic@ionic.de \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mani@kernel.org \
--cc=manivannan.sadhasivam@oss.qualcomm.com \
--cc=nakonechnij.sergsj@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=raj.bhagat@oss.qualcomm.com \
/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®