[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0101016ea2792bf8-85cec4e9-f426-43ba-89a1-242f2308e25e-000000@us-west-2.amazonses.com>
Date: Mon, 25 Nov 2019 12:11:20 +0000
From: Kalle Valo <kvalo@...eaurora.org>
To: Jeffrey Hugo <jeffrey.l.hugo@...il.com>
Cc: davem@...emloft.net, ath10k@...ts.infradead.org,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
Jeffrey Hugo <jeffrey.l.hugo@...il.com>
Subject: Re: [PATCH v2] ath10k: Handle "invalid" BDFs for msm8998 devices
Jeffrey Hugo <jeffrey.l.hugo@...il.com> wrote:
> When the BDF download QMI message has the end field set to 1, it signals
> the end of the transfer, and triggers the firmware to do a CRC check. The
> BDFs for msm8998 devices fail this check, yet the firmware is happy to
> still use the BDF. It appears that this error is not caught by the
> downstream drive by concidence, therefore there are production devices
> in the field where this issue needs to be handled otherwise we cannot
> support wifi on them. So, attempt to detect this scenario as best we can
> and treat it as non-fatal.
>
> Signed-off-by: Jeffrey Hugo <jeffrey.l.hugo@...il.com>
> Reviewed-by: Bjorn Andersson <bjorn.andersson@...aro.org>
> Signed-off-by: Kalle Valo <kvalo@...eaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
319c2b71041f ath10k: Handle "invalid" BDFs for msm8998 devices
--
https://patchwork.kernel.org/patch/11242143/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Powered by blists - more mailing lists