All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ipw3945-devel@lists.sourceforge.net"
	<ipw3945-devel@lists.sourceforge.net>,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH wireless-2.6] iwlwifi: do not perferm force reset while doing scan
Date: Wed, 22 Sep 2010 07:33:50 -0700	[thread overview]
Message-ID: <1285166030.12056.19.camel@wwguy-huron> (raw)
In-Reply-To: <20100922105722.3be42969@dhcp-lab-109.englab.brq.redhat.com>

Hi Gruszka,

On Wed, 2010-09-22 at 01:57 -0700, Stanislaw Gruszka wrote:
> Hi Wey
> 
> On Fri, 17 Sep 2010 14:24:17 -0700
> Wey-Yi Guy <wey-yi.w.guy@intel.com> wrote:
> > When uCode error condition detected, driver try to perform either
> > rf reset or firmware reload in order bring device back to
> > working condition.
> > 
> > If rf reset is required and scan is in process, there is no need
> > to issue rf reset since scan already reset the rf.
> 
> Yes, and that is already handled by iwl_scan_initiate().
> 
> > If firmware reload is required and scan is in process, skip the
> > reload request. There is a possibility firmware reload during
> > scan cause problem.
> 
> If we skip restart request now, next will be scheduled lately (correct?,

That is correct, if we still encounter the problem.

> I think there are firmware reset requests that are not repeatable). But we
> still will have scan pending since firmware is in bad shape and will not
> finish scan. So until scan_check delayed work (7s) will not finish scan,
> will not be able to reset firmware. I do not think that is what we want.
> I think patch is good for .36, but after my current scan patches, it is
> not be needed and actually it should be reverted (see below).
> 
Agree, with your recent patch, it improve a lot on how scan abort work.
I still don't like the warning, but like you say, it might be ok since
we reloading firmware.

I will ask John to revert the patch

Thanks
Wey




  reply	other threads:[~2010-09-22 14:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-17 21:24 [PATCH wireless-2.6] iwlwifi: do not perferm force reset while doing scan Wey-Yi Guy
2010-09-22  8:57 ` Stanislaw Gruszka
2010-09-22 14:33   ` Guy, Wey-Yi [this message]
2010-09-22 14:39   ` Johannes Berg
2010-09-22 14:51     ` Stanislaw Gruszka
2010-09-22 15:10       ` Johannes Berg
2010-09-22 15:23         ` Stanislaw Gruszka
2010-09-22 15:27           ` Johannes Berg
2010-09-22 15:29           ` Guy, Wey-Yi

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=1285166030.12056.19.camel@wwguy-huron \
    --to=wey-yi.w.guy@intel.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=sgruszka@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.