From: Kerigan Creighton <kerigancreighton@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: loic.poulain@oss.qualcomm.com, wcn36xx@lists.infradead.org,
andersson@kernel.org, mathieu.poirier@linaro.org,
linux-remoteproc@vger.kernel.org, linux-arm-msm@vger.kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Kerigan Creighton <kerigancreighton@gmail.com>
Subject: [PATCH v3 0/3] Add support for Qualcomm WCN3610
Date: Thu, 5 Mar 2026 18:43:41 -0600 [thread overview]
Message-ID: <20260306004344.10968-1-kerigancreighton@gmail.com> (raw)
The WCN3610 is a 2.4GHz-only WLAN/BT combo chip used in some
cheaper Android and Windows phones such as the Lumia 550, and
IoT devices like the Anki Vector robot. It shares a lot in
common with the WCN3620.
This series adds support for the WCN3610 across the necessary
subsystems:
* Document the new compatible string (patch 1).
* Add compatible string in qcom_wcnss_iris (patch 2).
* Add rf_id and CFGs for the WCN3610 in wcn36xx, disable
powersave for this specific chip, ensure it is 2.4GHz-only
(patch 3).
Tested on an Anki Vector 1.0 and 2.0 robot. Support for other
WCN36xx chips has not been affected.
Changes in v2:
- Move the Documentation patch to the beginning of the patch set.
- Move remoteproc compatible string addition to the middle of
the patch set.
- Add Reviewed-by Dmitry (thanks!) to remoteproc compatible patch.
- Move wcn36xx driver changes to the end of the patch set.
Changes in v3:
- Describe the hardware rather than the driver in the
dt-bindings patch [Krzysztof].
- Describe why we need a new compatible in the remoteproc
patch [Krzysztof].
- Describe where the CFG values came from in the wcn36xx
driver patch [Konrad].
Kerigan Creighton (3):
dt-bindings: remoteproc: qcom,wcnss-pil: Add wcn3610 compatible
remoteproc: qcom_wcnss_iris: Add support for WCN3610
wifi: wcn36xx: Add support for WCN3610
.../bindings/remoteproc/qcom,wcnss-pil.yaml | 1 +
drivers/net/wireless/ath/wcn36xx/main.c | 4 +-
drivers/net/wireless/ath/wcn36xx/smd.c | 61 ++++++++++++++++++-
drivers/net/wireless/ath/wcn36xx/wcn36xx.h | 1 +
drivers/remoteproc/qcom_wcnss_iris.c | 1 +
5 files changed, 66 insertions(+), 2 deletions(-)
--
2.53.0
next reply other threads:[~2026-03-06 0:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 0:43 Kerigan Creighton [this message]
2026-03-06 0:43 ` [PATCH v3 1/3] dt-bindings: remoteproc: qcom,wcnss-pil: Add wcn3610 compatible Kerigan Creighton
2026-03-06 7:26 ` Krzysztof Kozlowski
2026-03-06 0:43 ` [PATCH v3 2/3] remoteproc: qcom_wcnss_iris: Add support for WCN3610 Kerigan Creighton
2026-03-06 7:25 ` Krzysztof Kozlowski
2026-03-06 0:43 ` [PATCH v3 3/3] wifi: wcn36xx: " Kerigan Creighton
2026-03-06 8:41 ` Loic Poulain
2026-03-06 18:05 ` Kerigan Creighton
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=20260306004344.10968-1-kerigancreighton@gmail.com \
--to=kerigancreighton@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=mathieu.poirier@linaro.org \
--cc=robh@kernel.org \
--cc=wcn36xx@lists.infradead.org \
/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