All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Christian Lamparter <chunkeey@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH for-4.19-stable] ath10k: restore QCA9880-AR1A (v1) detection
Date: Sun, 1 Dec 2019 12:02:45 -0500	[thread overview]
Message-ID: <20191201170245.GU5861@sasha-vm> (raw)
In-Reply-To: <5688116.JcRxOpqE2I@debian64>

On Fri, Nov 29, 2019 at 09:52:14PM +0100, Christian Lamparter wrote:
>commit f8914a14623a79b73f72b2b1ee4cd9b2cb91b735 upstream
>---
>From f8914a14623a79b73f72b2b1ee4cd9b2cb91b735 Mon Sep 17 00:00:00 2001
>From: Christian Lamparter <chunkeey@gmail.com>
>Date: Mon, 25 Mar 2019 13:50:19 +0100
>Subject: [PATCH for-4.19-stable] ath10k: restore QCA9880-AR1A (v1) detection
>To: linux-wireless@vger.kernel.org,
>    ath10k@lists.infradead.org
>Cc: Kalle Valo <kvalo@codeaurora.org>
>
>This patch restores the old behavior that read
>the chip_id on the QCA988x before resetting the
>chip. This needs to be done in this order since
>the unsupported QCA988x AR1A chips fall off the
>bus when resetted. Otherwise the next MMIO Op
>after the reset causes a BUS ERROR and panic.
>
>Cc: stable@vger.kernel.org # 4.19
>Fixes: 1a7fecb766c8 ("ath10k: reset chip before reading chip_id in probe")
>Signed-off-by: Christian Lamparter <chunkeey@gmail.com>

Queued up for all branches, thanks!

-- 
Thanks,
Sasha

  reply	other threads:[~2019-12-01 17:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29 20:52 [PATCH for-4.19-stable] ath10k: restore QCA9880-AR1A (v1) detection Christian Lamparter
2019-12-01 17:02 ` Sasha Levin [this message]
2019-12-02  9:14   ` Greg KH
2019-12-02  9:15     ` Greg KH
2019-12-02  9:17       ` Greg KH
2019-12-02  9:18         ` Greg KH

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=20191201170245.GU5861@sasha-vm \
    --to=sashal@kernel.org \
    --cc=chunkeey@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.