From: Rob Herring <robh@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Kalle Valo <kvalo@codeaurora.org>,
"David S. Miller" <davem@davemloft.net>,
Mark Rutland <mark.rutland@arm.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
ath10k@lists.infradead.org, stable@vger.kernel.org
Subject: Re: [PATCH] ath10k: Fix HOST capability QMI incompatibility
Date: Fri, 16 Aug 2019 16:11:41 -0500 [thread overview]
Message-ID: <20190816211141.GA4468@bogus> (raw)
In-Reply-To: <20190725063108.15790-1-bjorn.andersson@linaro.org>
On Wed, Jul 24, 2019 at 11:31:08PM -0700, Bjorn Andersson wrote:
> The introduction of 768ec4c012ac ("ath10k: update HOST capability QMI
> message") served the purpose of supporting the new and extended HOST
> capability QMI message.
>
> But while the new message adds a slew of optional members it changes the
> data type of the "daemon_support" member, which means that older
> versions of the firmware will fail to decode the incoming request
> message.
>
> There is no way to detect this breakage from Linux and there's no way to
> recover from sending the wrong message (i.e. we can't just try one
> format and then fallback to the other), so a quirk is introduced in
> DeviceTree to indicate to the driver that the firmware requires the 8bit
> version of this message.
>
> Cc: stable@vger.kernel.org
> Fixes: 768ec4c012ac ("ath10k: update HOST capability qmi message")
> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> ---
> .../bindings/net/wireless/qcom,ath10k.txt | 6 +++++
Acked-by: Rob Herring <robh@kernel.org>
> drivers/net/wireless/ath/ath10k/qmi.c | 13 ++++++++---
> .../net/wireless/ath/ath10k/qmi_wlfw_v01.c | 22 +++++++++++++++++++
> .../net/wireless/ath/ath10k/qmi_wlfw_v01.h | 1 +
> drivers/net/wireless/ath/ath10k/snoc.c | 11 ++++++++++
> drivers/net/wireless/ath/ath10k/snoc.h | 1 +
> 6 files changed, 51 insertions(+), 3 deletions(-)
next prev parent reply other threads:[~2019-08-16 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 6:31 [PATCH] ath10k: Fix HOST capability QMI incompatibility Bjorn Andersson
2019-08-16 21:11 ` Rob Herring [this message]
2019-09-17 14:03 ` Kalle Valo
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=20190816211141.GA4468@bogus \
--to=robh@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=bjorn.andersson@linaro.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.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).