From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>, david@ixit.cz
Cc: Johannes Berg <johannes@sipsolutions.net>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jeff Johnson <jjohnson@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Paul Sajna <sajattack@postmarketos.org>,
Amit Pundir <amit.pundir@linaro.org>,
linux-wireless@vger.kernel.org, devicetree@vger.kernel.org,
ath10k@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, phone-devel@vger.kernel.org
Subject: Re: [PATCH v4 2/3] ath10k: Add device-tree quirk to skip host cap QMI requests
Date: Mon, 30 Mar 2026 11:56:16 -0700 [thread overview]
Message-ID: <fd33e4fe-8450-4076-b0cb-f09a7bb9cb11@oss.qualcomm.com> (raw)
In-Reply-To: <c5tdbllqrxxsviv7m2i3xzweyjhetv6wbpgioddaitig3tm6or@a22uaizux6nq>
On 3/29/2026 9:26 AM, Dmitry Baryshkov wrote:
> On Wed, Mar 25, 2026 at 06:57:16PM +0100, David Heidelberg via B4 Relay wrote:
>> From: Amit Pundir <amit.pundir@linaro.org>
>>
>> Some firmware versions do not support the host capability QMI request.
>> Since this request occurs before firmware-N.bin and board-M.bin are
>> loaded, the quirk cannot be expressed in the firmware itself.
>
>
> Acked-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
>
> Jeff, to my knowledge this is the best approach that we have to solve
> the issue on those devices.
I'm ok with this approach.
I need DT Review or ACK on the 1/3 patch in order to bring the first 2 patches
through my ath tree.
/jeff
next prev parent reply other threads:[~2026-03-30 18:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 17:57 [PATCH v4 0/3] ath10k: Introduce a devicetree quirk to skip host cap QMI requests David Heidelberg via B4 Relay
2026-03-25 17:57 ` [PATCH v4 1/3] dt-bindings: wireless: ath10k: Add " David Heidelberg via B4 Relay
2026-04-06 15:51 ` Jeff Johnson
2026-04-07 5:44 ` Krzysztof Kozlowski
2026-03-25 17:57 ` [PATCH v4 2/3] ath10k: Add device-tree " David Heidelberg via B4 Relay
2026-03-26 19:39 ` Paul Sajna
2026-03-29 16:26 ` Dmitry Baryshkov
2026-03-30 18:56 ` Jeff Johnson [this message]
2026-03-30 19:38 ` Dmitry Baryshkov
2026-03-31 16:06 ` Vasanthakumar Thiagarajan
2026-04-07 3:36 ` Baochen Qiang
2026-03-25 17:57 ` [PATCH v4 3/3] arm64: dts: qcom: sdm845-xiaomi-beryllium: Enable ath10k host-cap skip quirk David Heidelberg via B4 Relay
2026-03-29 16:27 ` Dmitry Baryshkov
2026-04-08 17:15 ` [PATCH v4 0/3] ath10k: Introduce a devicetree quirk to skip host cap QMI requests Jeff Johnson
2026-04-08 17:27 ` Jeff Johnson
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=fd33e4fe-8450-4076-b0cb-f09a7bb9cb11@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=amit.pundir@linaro.org \
--cc=andersson@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sajattack@postmarketos.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