[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6a3448cf-dd18-4b3d-a8fa-fe282ee779de@ixit.cz>
Date: Tue, 25 Nov 2025 10:29:23 +0100
From: David Heidelberg <david@...t.cz>
To: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>,
Jeff Johnson <jeff.johnson@....qualcomm.com>
Cc: Johannes Berg <johannes@...solutions.net>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Jeff Johnson <jjohnson@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>, linux-wireless@...r.kernel.org,
devicetree@...r.kernel.org, ath10k@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
phone-devel@...r.kernel.org, Amit Pundir <amit.pundir@...aro.org>
Subject: Re: [PATCH v2 0/3] ath10k: Introduce a devicetree quirk to skip host
cap QMI requests
On 10/11/2025 21:41, Dmitry Baryshkov wrote:
[...]
> I think this should go to the firmware-N file. SNOC platforms now allow
> per-platform firmware description files, so it's possible to describe
> quirks for the particular firmware file.
Since the approach to put it into the firmware failed due to early
initialization, see
https://lore.kernel.org/linux-wireless/20251111-xiaomi-beryllium-firmware-v1-0-836b9c51ad86@ixit.cz/
I wondering if I should get back on this series?
Also, meanwhile Paul found another device [1] in need of this quirk.
David
[1]
https://lore.kernel.org/all/20250928-judyln-dts-v3-0-b14cf9e9a928@postmarketos.org/T/#m90e8087d4388e588b71a0eff01b88f1721f73b73
>
>>
>> So I'm personally OK with this suggested approach.
>>
>> /jeff
>
--
David Heidelberg
Powered by blists - more mailing lists