linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Sujith Manoharan <c_manoha@qti.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com,
	rodrigue@qca.qualcomm.com
Subject: Re: [PATCH 3.7 2/3] ath9k: improve suspend/resume reliability
Date: Thu, 04 Oct 2012 11:33:56 +0200	[thread overview]
Message-ID: <506D5804.4090806@openwrt.org> (raw)
In-Reply-To: <20588.62828.845432.706022@gargle.gargle.HOWL>

On 2012-10-04 4:33 AM, Sujith Manoharan wrote:
> Felix Fietkau wrote:
>> Ensure that drv_start() always returns true, as a failing hw start usually
>> eventually leads to crashes when there's still a station entry present.
>> Call a power-on reset after a resume and after a hw reset failure to bring
>> the hardware back to life again.
> 
> In what situations did HW reset (via start() or resume()) fail ?
I don't know what situations caused it, but this happened on a few
ChromeOS devices in the wild, and my patch fixed it.

- Felix

  reply	other threads:[~2012-10-04  9:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03 19:07 [PATCH 3.7 1/3] ath9k: fix ASPM initialization on resume Felix Fietkau
2012-10-03 19:07 ` [PATCH 3.7 2/3] ath9k: improve suspend/resume reliability Felix Fietkau
2012-10-03 19:07   ` [PATCH 3.7 3/3] ath9k: use ieee80211_free_txskb Felix Fietkau
2012-10-04  2:33   ` [PATCH 3.7 2/3] ath9k: improve suspend/resume reliability Sujith Manoharan
2012-10-04  9:33     ` Felix Fietkau [this message]
2012-10-06 10:46       ` Manoharan, Sujith
2012-10-06 10:59         ` Felix Fietkau

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=506D5804.4090806@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=c_manoha@qti.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rodrigue@qca.qualcomm.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).