linux-kernel - Re: [PATCH v3 07/11] arm64: dts: qcom: sdm845-lg-{common, judyln}: Add wifi node

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4c80c922-5955-4490-bb69-fc0e91368bdf@ixit.cz>
Date: Wed, 26 Nov 2025 13:14:29 +0100
From: David Heidelberg <david@...t.cz>
To: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>,
 Paul Sajna <sajattack@...tmarketos.org>
Cc: Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
 Bjorn Andersson <andersson@...nel.org>,
 Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, linux-arm-msm@...r.kernel.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 phone-devel@...r.kernel.org, Amir Dahan <system64fumo@...tonmail.com>,
 Christopher Brown <crispybrown@...il.com>
Subject: Re: [PATCH v3 07/11] arm64: dts: qcom: sdm845-lg-{common, judyln}:
 Add wifi node

On 26/11/2025 01:38, Dmitry Baryshkov wrote:

[...]
>>> with qcom,snoc-host-cap-8bit-quirk I get
>>> ```
>>> ath10k_snoc 18800000.wifi: msa info req rejected: 90
>>> ```
>>>
>>> without it I get
>>> ```
>>> ath10k_snoc 18800000.wifi: host capability request rejected: 1
>>>
>>> ```
>>>
>>> Please help me understand how I should proceed.
>>>
>>
>> I guess I'll just voice my support in https://patchwork.kernel.org/project/ath10k/patch/1601058581-19461-1-git-send-email-amit.pundir@linaro.org/ for now.
> 
> Can "... we just ignore the return value of
> ath10k_qmi_host_cap_send_sync() and move along"?
> 

From: https://lore.kernel.org/all/20201029134017.GA807@yoga/
SNIP ---
 > Why can't you just always ignore this error? If you can't deal with this
 > entirely in the driver, then it should be part of the WiFi firmware so
 > it's always in sync.
 >

Unfortunately the firmware versions I've hit this problem on has gone
belly up when receiving this request, that's why I asked Amit to add a
flag to skip it.

That said, in the devices I've hit this I've managed to get newer
firmware working, which doesn't have either problem.
SNIP ---

That's the pain behind it.

David