From: Krzysztof Kozlowski <krzk@kernel.org>
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,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v3 2/3] remoteproc: qcom_wcnss_iris: Add support for WCN3610
Date: Fri, 6 Mar 2026 08:25:50 +0100 [thread overview]
Message-ID: <4f94c20c-d06f-48e5-95fb-5380c84a1b99@kernel.org> (raw)
In-Reply-To: <20260306004344.10968-3-kerigancreighton@gmail.com>
On 06/03/2026 01:43, Kerigan Creighton wrote:
> WCN3610 has the same regulator requirements as
> WCN3620, so in qcom_wcnss_iris, we can use wcn3620_data.
>
> A separate compatible is needed for WCN3610 because the
> wcn36xx driver uses it for chip-specific configuration.
> Specifically, it sets BTC (Bluetooth Coexistence) CFGs,
> disables ENABLE_DYNAMIC_RA_START_RATE, and disables
> STA_POWERSAVE for this specific chip for stable
> functionality.
This goes to the binding description where you describe the hardware,
how I asked.
Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-06 7:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 0:43 [PATCH v3 0/3] Add support for Qualcomm WCN3610 Kerigan Creighton
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 [this message]
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=4f94c20c-d06f-48e5-95fb-5380c84a1b99@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--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