From: Simon Horman <horms@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
Cc: 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>,
Jeff Johnson <jjohnson@kernel.org>,
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>,
Juha-Matti Tilli <juha-matti.tilli@iki.fi>,
Jeff Hugo <jeff.hugo@oss.qualcomm.com>
Subject: Re: [PATCH v4 4/4] wifi: ath12k: Connect to the QMI server belonging to the device owned by this driver
Date: Mon, 26 Oct 2026 17:26:15 +0000 [thread overview]
Message-ID: <20261026172615.GK257209@horms.kernel.org> (raw)
In-Reply-To: <20261022-qrtr-multi-ep-v4-4-c6fdb75fcd3e@oss.qualcomm.com>
On Thu, Oct 22, 2026 at 07:43:10PM +0200, Manivannan Sadhasivam wrote:
> 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, reject 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>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2026-10-26 17:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 17:43 [PATCH v4 0/4] net: qrtr: Add support for using identical MHI endpoint devices Manivannan Sadhasivam
2026-10-22 17:43 ` Manivannan Sadhasivam via B4 Relay
2026-10-22 17:43 ` [PATCH v4 1/4] net: qrtr: Allow the host QRTR to assign a unique node id Manivannan Sadhasivam
2026-10-22 17:43 ` Manivannan Sadhasivam via B4 Relay
2026-10-26 17:24 ` Simon Horman
2026-10-22 17:43 ` [PATCH v4 2/4] net: qrtr: Assign unique node id for MHI endpoints Manivannan Sadhasivam
2026-10-22 17:43 ` Manivannan Sadhasivam via B4 Relay
2026-10-26 17:25 ` Simon Horman
2026-10-22 17:43 ` [PATCH v4 3/4] wifi: ath11k: Connect to the QMI server belonging to the device owned by this driver Manivannan Sadhasivam
2026-10-22 17:43 ` Manivannan Sadhasivam via B4 Relay
2026-10-26 17:25 ` Simon Horman
2026-10-26 21:34 ` Jeff Johnson
2026-10-22 17:43 ` [PATCH v4 4/4] wifi: ath12k: " Manivannan Sadhasivam
2026-10-22 17:43 ` Manivannan Sadhasivam via B4 Relay
2026-10-23 5:51 ` Juha-Matti Tilli
2026-10-26 6:22 ` [PATCH v4 4/4] wifi: ath12k: Connect to the QMI server belonging to the MHI endpoint that received the packet Daizhuang Bai
2026-10-26 17:26 ` Simon Horman [this message]
2026-10-26 21:34 ` [PATCH v4 4/4] wifi: ath12k: Connect to the QMI server belonging to the device owned by this driver Jeff Johnson
2026-10-27 0:15 ` [PATCH v4 0/4] net: qrtr: Add support for using identical MHI endpoint devices Jakub Kicinski
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=20261026172615.GK257209@horms.kernel.org \
--to=horms@kernel.org \
--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=deepak.singh@oss.qualcomm.com \
--cc=edumazet@google.com \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=juha-matti.tilli@iki.fi \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.