From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Kerigan Creighton <kerigancreighton@gmail.com>,
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
Subject: Re: [PATCH v2 3/3] wifi: wcn36xx: add support for WCN3610
Date: Thu, 5 Mar 2026 09:41:03 +0100 [thread overview]
Message-ID: <dea45e4e-aebc-46e4-a245-3603da1779f3@oss.qualcomm.com> (raw)
In-Reply-To: <20260305003253.1022386-4-kerigancreighton@gmail.com>
On 3/5/26 1:32 AM, Kerigan Creighton wrote:
> The WCN3610 has a lot in common with the WCN3620, so much
> of that code was reused.
>
> Tested on an Anki Vector 1.0 and 2.0 robot. Support for other
> WCN36xx chips has not been affected.
>
> The WCN3610 requires specific BTC configuration values for
> stable Wi-Fi. Without these values, there's some packet loss.
> An extra CFG table was made so other chips are not affected.
>
> STA_POWERSAVE causes firmware bugs (long hangs) with the
> WCN3610, thus it has been disabled just for this chip.
Is that something you've observed, or does the downstream kernel
mention these issues?
Konrad
next prev parent reply other threads:[~2026-03-05 8:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 0:32 [PATCH v2 0/3] Add support for Qualcomm WCN3610 Kerigan Creighton
2026-03-05 0:32 ` [PATCH v2 1/3] dt-bindings: remoteproc: qcom,wcnss-pil: add WCN3610 compatible Kerigan Creighton
2026-03-05 8:05 ` Krzysztof Kozlowski
2026-03-05 0:32 ` [PATCH v2 2/3] remoteproc: qcom_wcnss_iris: add support for WCN3610 Kerigan Creighton
2026-03-05 8:06 ` Krzysztof Kozlowski
2026-03-13 19:27 ` Dmitry Baryshkov
2026-03-05 0:32 ` [PATCH v2 3/3] wifi: wcn36xx: " Kerigan Creighton
2026-03-05 8:41 ` Konrad Dybcio [this message]
[not found] ` <CAN6+ztxfcNR8xR1qwgHQcHHM=zoQbMd-8oggb785ssPZ7f=y4w@mail.gmail.com>
2026-03-05 19:16 ` Loic Poulain
2026-03-05 19:33 ` 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=dea45e4e-aebc-46e4-a245-3603da1779f3@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kerigancreighton@gmail.com \
--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