public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: David Heidelberg <david@ixit.cz>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
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 v3 2/3] ath10k: Introduce a device-tree quirk to skip host cap QMI requests
Date: Wed, 25 Mar 2026 18:39:32 +0100	[thread overview]
Message-ID: <323d5570-ae3d-4083-bbc8-8ce2ef53a34c@ixit.cz> (raw)
In-Reply-To: <d6pv62kc5zyqite7krm65vbtlqnsc3v53rlrtilchyk5c7uad2@iu4yaw2ksr65>

On 25/03/2026 18:15, Dmitry Baryshkov wrote:
> On Wed, Mar 25, 2026 at 05:41:13PM +0100, David Heidelberg via B4 Relay wrote:
>> From: Amit Pundir <amit.pundir@linaro.org>
>>
>> There are firmware versions which do not support host capability QMI
>> request. We suspect either the host cap is not implemented or there may
>> be firmware specific issues, but apparently there seem to be a generation
>> of firmware that has this particular behavior.
> 
> It needs to be explicit that this happens _before_ firmware-N.bin and
> board-M.bin loading. As such, you can't add a quirk to the firmware.bin
> (a standard way to handle firmware issues).

Ok, let me send with updated desc :)

> 
>> For example, firmware build on Xiaomi Poco F1 (sdm845) phone:
>> "QC_IMAGE_VERSION_STRING=WLAN.HL.2.0.c3-00257-QCAHLSWMTPLZ-1"
>>
>> If we do not skip the host cap QMI request on Poco F1, then we get a
>> QMI_ERR_MALFORMED_MSG_V01 error message before loading the firmware in the
>> ath10k_qmi_host_cap_send_sync(). This error message is not fatal to the
>> firmware nor to the ath10k driver and we can still bring up the WiFi
>> services successfully if we just ignore it.
>>
>> Hence introducing this device-tree quirk to skip host capability
>> QMI request for the devices with firmware versions which do not support
>> this feature.
>>
>> Suggested-by: Bjorn Andersson <andersson@kernel.org>
>> Signed-off-by: Amit Pundir <amit.pundir@linaro.org>
> 
> You are sending the patch, but it misses your SoB.

Oh, sorry bout that.

checkpatch.pl could spot this kind of an issue :P

David>
>> ---
>>   drivers/net/wireless/ath/ath10k/qmi.c  | 13 ++++++++++---
>>   drivers/net/wireless/ath/ath10k/snoc.c |  3 +++
>>   drivers/net/wireless/ath/ath10k/snoc.h |  1 +
>>   3 files changed, 14 insertions(+), 3 deletions(-)
> 

-- 
David Heidelberg


  reply	other threads:[~2026-03-25 17:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 16:41 [PATCH v3 0/3] ath10k: Introduce a devicetree quirk to skip host cap QMI requests David Heidelberg via B4 Relay
2026-03-25 16:41 ` [PATCH v3 1/3] dt-bindings: wireless: ath10k: Introduce " David Heidelberg via B4 Relay
2026-03-25 16:41 ` [PATCH v3 2/3] ath10k: Introduce a device-tree " David Heidelberg via B4 Relay
2026-03-25 17:15   ` Dmitry Baryshkov
2026-03-25 17:39     ` David Heidelberg [this message]
2026-03-25 16:41 ` [PATCH v3 3/3] arm64: dts: qcom: sdm845-xiaomi-beryllium: Enable ath10k host-cap skip quirk David Heidelberg via B4 Relay

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=323d5570-ae3d-4083-bbc8-8ce2ef53a34c@ixit.cz \
    --to=david@ixit.cz \
    --cc=amit.pundir@linaro.org \
    --cc=andersson@kernel.org \
    --cc=ath10k@lists.infradead.org \
    --cc=conor+dt@kernel.org \
    --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