From: Kalle Valo <kvalo@codeaurora.org>
To: Zhi Chen <zhichen@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH RFC, v2] Revert "ath10k: fix DMA related firmware crashes on multiple devices"
Date: Fri, 22 Nov 2019 09:45:28 +0000 [thread overview]
Message-ID: <0101016e92808aff-6e101d7c-069d-4db9-8149-9b12e3393920-000000@us-west-2.amazonses.com> (raw)
In-Reply-To: <1573808573-12159-1-git-send-email-zhichen@codeaurora.org> (Zhi Chen's message of "Fri, 15 Nov 2019 17:02:53 +0800")
Zhi Chen <zhichen@codeaurora.org> writes:
> This reverts commit 76d164f582150fd0259ec0fcbc485470bcd8033e.
> PCIe hung issue was observed on multiple platforms. The issue was reproduced
> when DUT was configured as AP and associated with 50+ STAs.
>
> With PCIe protocol analyzer, we can see DMA Read crossing 4KB boundary when
> issue happened. It broke PCIe spec and caused PCIe stuck.
>
> Tested: IPQ8064 + QCA9984 with firmware 10.4-3.10-00047
> QCS404 + QCA9984 with firmware 10.4-3.9.0.2--00044
> Synaptics AS370 + QCA9888 with firmware 10.4-3.9.0.2--00040
>
> Signed-off-by: Zhi Chen <zhichen@codeaurora.org>
> ---
All comments under --- line is not added to the git repository.
> v2: revert 10.4 only because old chips have different AXI RD/WR CFG
So you should also mention this in the commit log so it gets properly
archived.
And in the next version please remove RFC, as it seems we are reaching a
consensus that is the right approach. Or are there any comments?
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2019-11-22 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 9:02 [PATCH RFC,v2] Revert "ath10k: fix DMA related firmware crashes on multiple devices" Zhi Chen
2019-11-15 9:02 ` [PATCH RFC, v2] " Zhi Chen
2019-11-22 9:45 ` Kalle Valo
2019-11-22 9:45 ` Kalle Valo [this message]
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=0101016e92808aff-6e101d7c-069d-4db9-8149-9b12e3393920-000000@us-west-2.amazonses.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zhichen@codeaurora.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.