From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 0/2] ath10k: warm reset fixes 2014-05-14
Date: Wed, 14 May 2014 17:22:05 +0300 [thread overview]
Message-ID: <87bnv0fnjm.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1400050658-2763-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Wed, 14 May 2014 08:57:36 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> Warm reset was not able to recover from a device
> crash so ath10k was falling back to cold reset
> which would occasionally hang the system or
> generate a data bus error with some device chips.
>
> Warm reset now works a lot more reliably (at least
> on my T430). It's able to recover from a "hard"
> simulate fw crash and some firmware asserts I've
> forced meaning it should recover in most cases
> without falling back to the cold reset.
>
> There's still one case of a crash warm reset is
> incapable to recover from: IOMMU faults (when
> supported and enabled and device tries to access
> non-DMA mapped host memory) trigger device crash
> and leave CE totally unresponsive before and after
> the warm reset.
>
>
> Michal Kazior (2):
> ath10k: improve warm reset reliability
> ath10k: retry warm reset a few times
The patches don't apply anymore and the conflict was not trivial enough
for me to fix it. Can you rebase, please?
--
Kalle Valo
next prev parent reply other threads:[~2014-05-14 14:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 6:57 [PATCH 0/2] ath10k: warm reset fixes 2014-05-14 Michal Kazior
2014-05-14 6:57 ` [PATCH 1/2] ath10k: improve warm reset reliability Michal Kazior
2014-05-15 10:48 ` Kalle Valo
2014-05-15 12:42 ` Michal Kazior
2014-05-15 12:57 ` Kalle Valo
2014-05-14 6:57 ` [PATCH 2/2] ath10k: retry warm reset a few times Michal Kazior
2014-05-14 14:22 ` Kalle Valo [this message]
2014-05-14 14:25 ` [PATCH 0/2] ath10k: warm reset fixes 2014-05-14 Kalle Valo
2014-05-16 13:49 ` 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=87bnv0fnjm.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.com \
/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).