Re: [PATCH 3/4] wifi: ath11k: Connect to the QMI server belonging to the device owned by this driver

[Manivannan Sadhasivam]

On Fri, Sep 18, 2026 at 07:39:09PM +0300, Juha-Matti Tilli wrote:
> On Fri, Sep 18, 2026, at 19:28, Manivannan Sadhasivam via B4 Relay wrote:
> > From: Manivannan Sadhasivam <manivannan.sadhasivam@xxxxxxxxxxxxxxxx>
> > 
> > When two identical ath11k 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@xxxxxxxxxxxxxxxx>
> 
> Tested-by: Juha-Matti Tilli <juha-matti.tilli@xxxxxx>
> Tested-on: 2x WCN6855 hw2.1 PCI WLAN.HSP.1.1-04685-QCAHSPSWPL_V1_V2_SILICONZ_IOE-1
> 
> (assuming the patch is the same and hasn't been updated since 17.9:
> https://github.com/Mani-Sadhasivam/linux/commits/qrtr-multi-ep/ )
> 

I just sent v2. Could you please test this version? I had made some changes
while rebasing to net-next/main, so making sure I didn't regress, thanks!

- Mani

-- 
மணிவண்ணன் சதாசிவம்