* [PATCH] ath10k: correct target assert problem due to CE5 stuck
@ 2018-04-12 12:16 mpubbise
2018-04-19 15:59 ` Kalle Valo
0 siblings, 1 reply; 2+ messages in thread
From: mpubbise @ 2018-04-12 12:16 UTC (permalink / raw)
To: ath10k; +Cc: linux-wireless, Manikanta Pubbisetty
From: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Correct a minor bug in the commit 0628467f97b5 ("ath10k: fix
copy engine 5 destination ring stuck") which introduced a change to fix
firmware assert that happens when ring indices of copy engine 5 are stuck
for a specific duration, problem with this fix is that it did not use
ring arithmatic. As a result,firmware asserts did not go away entirely
athough the frequency of occurrence has reduced. Using ring arithmatic
to fix the issue.
Tested on QCA9984(fw version-10.4-3.4-00082).
Fixes: 0628467f97b5 ("ath10k: fix copy engine 5 destination ring stuck)
Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
---
drivers/net/wireless/ath/ath10k/ce.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ath/ath10k/ce.c b/drivers/net/wireless/ath/ath10k/ce.c
index b9def7b..6efa69e 100644
--- a/drivers/net/wireless/ath/ath10k/ce.c
+++ b/drivers/net/wireless/ath/ath10k/ce.c
@@ -615,7 +615,7 @@ void ath10k_ce_rx_update_write_idx(struct ath10k_ce_pipe *pipe, u32 nentries)
/* Prevent CE ring stuck issue that will occur when ring is full.
* Make sure that write index is 1 less than read index.
*/
- if ((cur_write_idx + nentries) == dest_ring->sw_index)
+ if (((cur_write_idx + nentries) & nentries_mask) == dest_ring->sw_index)
nentries -= 1;
write_index = CE_RING_IDX_ADD(nentries_mask, write_index, nentries);
--
2.7.4
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: ath10k: correct target assert problem due to CE5 stuck
2018-04-12 12:16 [PATCH] ath10k: correct target assert problem due to CE5 stuck mpubbise
@ 2018-04-19 15:59 ` Kalle Valo
0 siblings, 0 replies; 2+ messages in thread
From: Kalle Valo @ 2018-04-19 15:59 UTC (permalink / raw)
To: mpubbise; +Cc: ath10k, linux-wireless, Manikanta Pubbisetty
mpubbise@codeaurora.org wrote:
> Correct a minor bug in the commit 0628467f97b5 ("ath10k: fix
> copy engine 5 destination ring stuck") which introduced a change to fix
> firmware assert that happens when ring indices of copy engine 5 are stuck
> for a specific duration, problem with this fix is that it did not use
> ring arithmatic. As a result,firmware asserts did not go away entirely
> athough the frequency of occurrence has reduced. Using ring arithmatic
> to fix the issue.
>
> Tested on QCA9984(fw version-10.4-3.4-00082).
>
> Fixes: 0628467f97b5 ("ath10k: fix copy engine 5 destination ring stuck)
> Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
1e8f77502341 ath10k: correct target assert problem due to CE5 stuck
--
https://patchwork.kernel.org/patch/10338443/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-04-19 15:59 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-04-12 12:16 [PATCH] ath10k: correct target assert problem due to CE5 stuck mpubbise
2018-04-19 15:59 ` Kalle Valo
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).