Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Marc Gonzalez <mgonzalez@freebox.fr>,
	Kalle Valo <kvalo@kernel.org>,
	Jeff Johnson <quic_jjohnson@quicinc.com>,
	ath10k <ath10k@lists.infradead.org>
Cc: wireless <linux-wireless@vger.kernel.org>,
	DT <devicetree@vger.kernel.org>,
	MSM <linux-arm-msm@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Pierre-Hugues Husson <phhusson@freebox.fr>,
	Arnaud Vrac <avrac@freebox.fr>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Jami Kettunen <jamipkettunen@gmail.com>,
	Jeffrey Hugo <quic_jhugo@quicinc.com>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Alexey Minnekhanov <alexeymin@postmarketos.org>
Subject: Re: [PATCH v3 0/3] Work around missing MSA_READY indicator for msm8998 devices
Date: Tue, 30 Apr 2024 00:24:40 +0100	[thread overview]
Message-ID: <463bcd2f-c741-4120-b7ae-2bb55d5211e3@linaro.org> (raw)
In-Reply-To: <ebbda69c-63c1-4003-bf97-c3adf3ccb9e3@freebox.fr>

On 29/04/2024 15:01, Marc Gonzalez wrote:
> Work around missing MSA_READY indicator in ath10k driver
> (apply work-around for all msm8998 devices)
> 
> CHANGELOG v3
> - Add a paragraph in binding commit to explain why we use
>    a DT property instead of a firmware feature bit.
> - Warn if the "no_msa_ready_indicator" property is true,
>    but we actually receive the indicator.
> 
> Marc Gonzalez (3):
>    dt-bindings: net: wireless: ath10k: add qcom,no-msa-ready-indicator prop
>    wifi: ath10k: do not always wait for MSA_READY indicator
>    arm64: dts: qcom: msm8998: set qcom,no-msa-ready-indicator for wifi
> 
>   Documentation/devicetree/bindings/net/wireless/qcom,ath10k.yaml |  5 +++++
>   arch/arm64/boot/dts/qcom/msm8998.dtsi                           |  1 +
>   drivers/net/wireless/ath/ath10k/qmi.c                           | 11 +++++++++++
>   drivers/net/wireless/ath/ath10k/qmi.h                           |  1 +
>   4 files changed, 18 insertions(+)
> 

I wonder if you could infer the workaround based on firmware version, 
instead of kernel passed flag ?

---
bod

  parent reply	other threads:[~2024-04-29 23:24 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29 14:01 [PATCH v3 0/3] Work around missing MSA_READY indicator for msm8998 devices Marc Gonzalez
2024-04-29 14:04 ` [PATCH v3 1/3] dt-bindings: net: wireless: ath10k: add qcom,no-msa-ready-indicator prop Marc Gonzalez
2024-04-30  2:22   ` Bjorn Andersson
2024-04-30  4:06     ` Kalle Valo
2024-04-30 11:10       ` Marc Gonzalez
2024-05-06 12:16         ` Kalle Valo
2024-05-07 17:03         ` Kalle Valo
2024-05-13  8:47           ` Marc Gonzalez
2024-04-30 14:39   ` Jeff Johnson
2024-05-07 15:05   ` Rob Herring (Arm)
2024-05-13 14:16   ` Kalle Valo
2024-05-28  9:54     ` Marc Gonzalez
2024-05-28 10:11       ` Kalle Valo
2024-05-28 12:36         ` Marc Gonzalez
2024-05-28 13:34           ` Kalle Valo
2024-04-29 14:06 ` [PATCH v3 2/3] wifi: ath10k: do not always wait for MSA_READY indicator Marc Gonzalez
2024-04-30  2:24   ` Bjorn Andersson
2024-04-30 11:15     ` Marc Gonzalez
2024-04-30 14:39   ` Jeff Johnson
2024-04-29 14:07 ` [PATCH v3 3/3] arm64: dts: qcom: msm8998: set qcom,no-msa-ready-indicator for wifi Marc Gonzalez
2024-04-30 14:40   ` Jeff Johnson
2024-05-06 10:39   ` Marc Gonzalez
2024-05-07 11:06     ` Konrad Dybcio
2024-04-29 23:24 ` Bryan O'Donoghue [this message]
2024-04-30  2:18   ` [PATCH v3 0/3] Work around missing MSA_READY indicator for msm8998 devices Bjorn Andersson
2024-05-29  2:01 ` (subset) " Bjorn Andersson

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=463bcd2f-c741-4120-b7ae-2bb55d5211e3@linaro.org \
    --to=bryan.odonoghue@linaro.org \
    --cc=alexeymin@postmarketos.org \
    --cc=andersson@kernel.org \
    --cc=ath10k@lists.infradead.org \
    --cc=avrac@freebox.fr \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=jamipkettunen@gmail.com \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kvalo@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mgonzalez@freebox.fr \
    --cc=phhusson@freebox.fr \
    --cc=quic_jhugo@quicinc.com \
    --cc=quic_jjohnson@quicinc.com \
    --cc=robh+dt@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