Re: [PATCH 0/4] net: qrtr: Add support for using identical MHI endpoint devices

[Manivannan Sadhasivam]

On Fri, Sep 18, 2026 at 11:13:42AM -0700, Jeff Johnson wrote:
> On 9/18/2026 9:28 AM, Manivannan Sadhasivam via B4 Relay wrote:
> > Hi,
> > 
> > This series reworks the QRTR driver to add support for using identical MHI
> > endpoint devices at the same time. Currently, QRTR driver has a limitation on
> > using more than one identical MHI endpoint devices like QCS6490 or any Qcom
> > Endpoint device making use of QRTR at the same time. Because of the fact that
> > these devices will have the identical QRTR node id, they cannot be used at the
> > same time, on the same host machine.
> > 
> > This limitation is a blocker for running upstream kernel on devices like Qcom
> > based routers as they often have multiple identical WLAN Endpoint devices
> > connected to the Router SoC.
> > 
> > This series supersedes the following 2 series from Juha:
> > https://lore.kernel.org/all/20260915054207.2513877-1-juha-matti.tilli@xxxxxx
> > https://lore.kernel.org/all/20260915074135.2567411-1-juha-matti.tilli@xxxxxx
> > 
> > Compared to the series from Juha, this series simplifies the multi-endpoint
> > support by computing a unique node id for each MHI endpoint and uses it for the
> > internal QRTR book keeping. This ensures that even if the MHI endpoint devices
> > have same node ids, the host QRTR will always use a unique node id for each one
> > of them.
> > 
> > More details can be found in the individual patches.
> > 
> > Testing
> > =======
> > 
> > Juha tested this series on multi ath11k setup by backporting this series to
> > 6.6.156 kernel. I'd appreciate a formal tested-by tag from Juha and other folks
> > CCed to this series.
> > 
> > Merge Strategy
> > ==============
> > 
> > Since both QRTR and ath drivers are falling under the networking tree, the whole
> > series can be merged through netdev tree.
> > 
> > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@xxxxxxxxxxxxxxxx>
> > ---
> > Manivannan Sadhasivam (4):
> >       net: qrtr: Allow the host QRTR to assign a unique node id
> >       net: qrtr: Assign unique node id for MHI endpoints
> >       wifi: ath11k: Connect to the QMI server belonging to the device owned by this driver
> >       wifi: ath12k: Connect to the QMI server belonging to the device owned by this driver
> > 
> >  MAINTAINERS                           |  1 +
> >  drivers/net/wireless/ath/ath11k/hif.h |  9 ++++++
> >  drivers/net/wireless/ath/ath11k/pci.c |  9 ++++++
> >  drivers/net/wireless/ath/ath11k/qmi.c | 10 ++++++
> >  drivers/net/wireless/ath/ath12k/hif.h |  9 ++++++
> >  drivers/net/wireless/ath/ath12k/pci.c |  9 ++++++
> >  drivers/net/wireless/ath/ath12k/qmi.c | 11 +++++++
> >  include/net/qrtr.h                    | 21 ++++++++++++
> >  net/qrtr/af_qrtr.c                    | 61 +++++++++++++++++++++++++++++++----
> >  net/qrtr/mhi.c                        |  4 ++-
> >  10 files changed, 136 insertions(+), 8 deletions(-)
> > ---
> > base-commit: cee9395acd8043be0644b25c34bfa86623f2b935
> 
> I see this is based upon v7.3-rc1 (current release tree).
> This series doesn't cleanly apply on the net-next tree.
> 

Ah, that's bad.

> Are you planning on netdev taking this through current or next?
> 

-next only. I will respin.

> And an alternate merge strategy would be for netdev to take the first two
> patches and then after wireless fast-forwards and ath fast-forwards, I could
> take the last two though the ath tree.
> 

Unfortunately, ath patches depend on API introduced by the 2nd patch. So they
can't be applied independently.

I will respin this series on top of ath-next so that the series can be applied
through netdev next.

- Mani

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