ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: mpubbise@codeaurora.org
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: ath10k: correct target assert problem due to CE5 stuck
Date: Thu, 19 Apr 2018 15:59:10 +0000 (UTC)	[thread overview]
Message-ID: <20180419155910.B3C4F60117@smtp.codeaurora.org> (raw)
In-Reply-To: <1523535410-29333-1-git-send-email-mpubbise@codeaurora.org>

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


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

      reply	other threads:[~2018-04-19 15:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12 12:16 [PATCH] ath10k: correct target assert problem due to CE5 stuck mpubbise
2018-04-19 15:59 ` 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=20180419155910.B3C4F60117@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mpubbise@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