devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Heidelberg <david@ixit.cz>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Jeff Johnson <jeff.johnson@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>,
	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,
	Amit Pundir <amit.pundir@linaro.org>
Subject: Re: [PATCH v2 0/3] ath10k: Introduce a devicetree quirk to skip host cap QMI requests
Date: Tue, 25 Nov 2025 10:29:23 +0100	[thread overview]
Message-ID: <6a3448cf-dd18-4b3d-a8fa-fe282ee779de@ixit.cz> (raw)
In-Reply-To: <ttka4uevai7tzf4c3r7rgozzpd3hsdhjzf5uyysfzj24ex2o2v@r64z6pvxb6sv>

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


  reply	other threads:[~2025-11-25  9:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-10 14:26 [PATCH v2 0/3] ath10k: Introduce a devicetree quirk to skip host cap QMI requests David Heidelberg via B4 Relay
2025-11-10 14:26 ` [PATCH v2 1/3] dt-bindings: wireless: ath10k: Introduce " David Heidelberg via B4 Relay
2025-11-10 20:35   ` Dmitry Baryshkov
2025-11-10 14:26 ` [PATCH v2 2/3] ath10k: Introduce a devicetree " David Heidelberg via B4 Relay
2025-11-10 14:26 ` [PATCH v2 3/3] arm64: dts: qcom: sdm845-xiaomi-beryllium: Enable ath10k host-cap skip quirk David Heidelberg via B4 Relay
2025-11-10 20:04 ` [PATCH v2 0/3] ath10k: Introduce a devicetree quirk to skip host cap QMI requests Jeff Johnson
2025-11-10 20:41   ` Dmitry Baryshkov
2025-11-25  9:29     ` David Heidelberg [this message]
2025-11-25 14:42       ` Dmitry Baryshkov
2025-11-25  7:03 ` Paul Sajna

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=6a3448cf-dd18-4b3d-a8fa-fe282ee779de@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=jeff.johnson@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 \
    /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;
as well as URLs for NNTP newsgroup(s).