From: Kalle Valo <kvalo@codeaurora.org>
To: Christian Lamparter <chunkeey@gmail.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH] ath10k: restore QCA9880-AR1A (v1) detection
Date: Tue, 17 Sep 2019 06:44:12 +0000 (UTC) [thread overview]
Message-ID: <20190917064412.B376E61576@smtp.codeaurora.org> (raw)
In-Reply-To: <20190906215423.23589-1-chunkeey@gmail.com>
Christian Lamparter <chunkeey@gmail.com> wrote:
> 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
> Fixes: 1a7fecb766c8 ("ath10k: reset chip before reading chip_id in probe")
> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
I'll drop this as there's no plan to support QCA988X hw1.0.
--
https://patchwork.kernel.org/patch/11136089/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2019-09-17 6:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 21:54 [PATCH] ath10k: restore QCA9880-AR1A (v1) detection Christian Lamparter
2019-09-06 21:54 ` Christian Lamparter
2019-09-07 21:43 ` Sasha Levin
2019-09-07 21:43 ` Sasha Levin
2019-09-07 23:18 ` stable backports for "ath10k: restore QCA9880-AR1A (v1) detection" Christian Lamparter
2019-09-07 23:18 ` Christian Lamparter
2019-09-10 1:27 ` [PATCH] ath10k: restore QCA9880-AR1A (v1) detection Tom Psyborg
2019-09-10 1:27 ` Tom Psyborg
2019-09-10 7:21 ` Kalle Valo
2019-09-10 7:21 ` Kalle Valo
2019-09-10 12:59 ` Tom Psyborg
2019-09-10 12:59 ` Tom Psyborg
2019-09-10 13:51 ` Sebastian Gottschall
2019-09-10 14:11 ` Ben Greear
2019-09-10 14:20 ` Sebastian Gottschall
2019-09-08 6:32 ` Tom Psyborg
2019-09-08 6:32 ` Tom Psyborg
2019-09-17 6:44 ` Kalle Valo
2019-09-18 21:30 ` Tom Psyborg
2019-09-18 21:30 ` Tom Psyborg
2019-09-17 6:44 ` Kalle Valo [this message]
[not found] ` <20190917064412.C2E0D61572@smtp.codeaurora.org>
2019-09-20 17:19 ` Christian Lamparter
2019-09-20 17:19 ` Christian Lamparter
2019-10-01 13:03 ` Kalle Valo
2019-10-01 13:03 ` Kalle Valo
2019-10-01 14:17 ` Tom Psyborg
2019-10-01 14:17 ` Tom Psyborg
2019-10-02 17:19 ` Kalle Valo
2019-10-02 17:19 ` 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=20190917064412.B376E61576@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=chunkeey@gmail.com \
--cc=linux-wireless@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.