From: "Juha-Matti Tilli" <juha-matti.tilli@iki.fi>
To: ath11k@lists.infradead.org, ath12k@lists.infradead.org,
mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Jeff Johnson" <jjohnson@kernel.org>
Cc: "Jeff Hugo" <jeff.hugo@oss.qualcomm.com>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Eric Dumazet" <edumazet@google.com>,
"Kuniyuki Iwashima" <kuniyu@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Willem de Bruijn" <willemb@google.com>,
"David S . Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Simon Horman" <horms@kernel.org>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, "Mihai Moldovan" <ionic@ionic.de>,
"Denis Kenzior" <denkenz@gmail.com>
Subject: Re: [PATCH v4 00/12] ath1{1,2}k: support multiple PCI devices in one system
Date: Fri, 18 Sep 2026 09:26:24 +0300 [thread overview]
Message-ID: <98cc01fd-0df0-46ee-b27f-2556a577a5a5@app.fastmail.com> (raw)
In-Reply-To: <20260915074135.2567411-1-juha-matti.tilli@iki.fi>
On Tue, Sep 15, 2026, at 10:41, Juha-Matti Tilli wrote:
> Hello,
>
> As you may well know, multiple identical ath11k and ath12k devices are
> not supported in a single Linux host because they use conflicting QRTR
> node IDs. Fortunately, Denis Kenzior created a patchset to support
> multiple QRTR endpoints with identical node IDs, and Mihai Moldovan
> refined it, after which I took over the patchset and refined it more.
>
> Mihai Moldovan also created a patchset for actually adding the support
> for this QRTR multi-endpoint feature to ath11k and ath12k drivers.
> Unfortunately, the code of Mihai was not merge-quality, since it leaked
> memory if you ran rmmod and modprobe inside a loop. Mihai mentioned this
> drawback, without providing an API for deleting endpoints or usage of
> such API in code that's responsible for freeing resources. Also Mihai's
> patchset had a race condition.
Hello,
Some positive news. There will be no next version, as Qualcomm is going
to provide a superior patchset that I tested. It's easier to backport,
cleaner design, fewer lines changed, has 1 author as opposed to 3, and
most importantly, it worked just fine on my 2x card setup.
Thus, I'm going to abandon this patchset.
BR, Juha-Matti
prev parent reply other threads:[~2026-09-18 6:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 7:41 Juha-Matti Tilli
2026-09-15 7:41 ` [PATCH v4 01/12] net: qrtr: support getting new endpoint ids externally Juha-Matti Tilli
2026-09-15 7:41 ` [PATCH v4 02/12] bus: mhi: allow mhi to know about its qrtr endpoint id and free it Juha-Matti Tilli
2026-09-15 7:41 ` [PATCH v4 03/12] net: qrtr: mhi: register new qrtr endpoint id for mhi Juha-Matti Tilli
2026-09-15 7:41 ` [PATCH v4 04/12] soc: qcom: qmi_helpers: add QRTR endpoint ID to qmi_handle Juha-Matti Tilli
2026-09-15 7:41 ` [PATCH v4 05/12] soc: qcom: qmi_helpers: optionally bind to QRTR endpoint ID in qmi_sock_create Juha-Matti Tilli
2026-09-15 7:41 ` [PATCH v4 06/12] wifi: ath11k: add QRTR endpoint ID hif feature Juha-Matti Tilli
2026-09-15 7:41 ` [PATCH v4 07/12] wifi: ath11k: stub QRTR endpoint ID fetching Juha-Matti Tilli
2026-09-15 7:41 ` [PATCH v4 08/12] wifi: ath11k: implement QRTR endpoint ID fetching for PCI Juha-Matti Tilli
2026-09-15 7:41 ` [PATCH v4 09/12] wifi: ath11k: bind to QRTR endpoint ID in ath11k_qmi_init_service Juha-Matti Tilli
2026-09-15 7:41 ` [PATCH v4 10/12] wifi: ath12k: add QRTR endpoint ID hif feature Juha-Matti Tilli
2026-09-15 7:41 ` [PATCH v4 11/12] wifi: ath12k: implement QRTR endpoint ID fetching for PCI Juha-Matti Tilli
2026-09-15 7:41 ` [PATCH v4 12/12] wifi: ath12k: bind to QRTR endpoint ID in ath12k_qmi_init_service Juha-Matti Tilli
2026-09-18 6:26 ` Juha-Matti Tilli [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=98cc01fd-0df0-46ee-b27f-2556a577a5a5@app.fastmail.com \
--to=juha-matti.tilli@iki.fi \
--cc=andersson@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=denkenz@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=ionic@ionic.de \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=konradybcio@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mhi@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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®