From: Kalle Valo <kvalo@codeaurora.org>
To: Zhi Chen <zhichen@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
Zhi Chen <zhichen@codeaurora.org>
Subject: Re: [PATCH, v4] Revert "ath10k: fix DMA related firmware crashes on multiple devices"
Date: Sun, 26 Jan 2020 10:34:52 +0000 (UTC) [thread overview]
Message-ID: <20200126103452.DF7CAC433A2@smtp.codeaurora.org> (raw)
In-Reply-To: <1578976521-6104-1-git-send-email-zhichen@codeaurora.org>
Zhi Chen <zhichen@codeaurora.org> wrote:
> 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.
>
> For QCA9984/QCA9888, the DMA_BURST_SIZE register controls the AXI burst size
> of the RD/WR access to the HOST MEM.
> 0 - No split , RAW read/write transfer size from MAC is put out on bus
> as burst length
> 1 - Split at 256 byte boundary
> 2,3 - Reserved
>
> With PCIe protocol analyzer, we can see DMA Read crossing 4KB boundary when
> issue happened. It broke PCIe spec and caused PCIe stuck. So revert
> the default value from 0 to 1.
>
> 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>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
a1769bb68a85 Revert "ath10k: fix DMA related firmware crashes on multiple devices"
--
https://patchwork.kernel.org/patch/11331293/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-01-26 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 4:35 [PATCH,v4] Revert "ath10k: fix DMA related firmware crashes on multiple devices" Zhi Chen
2020-01-26 10:34 ` Kalle Valo [this message]
2020-09-08 17:48 ` Ben Greear
2020-09-09 2:04 ` Zhi Chen
2020-09-09 4:02 ` Ben Greear
2020-09-15 20:00 ` Ben Greear
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=20200126103452.DF7CAC433A2@smtp.codeaurora.org \
--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 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).