linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 2/2] iwlwifi: one less commit_rxon while scan
Date: Fri, 15 Oct 2010 09:00:19 -0700	[thread overview]
Message-ID: <1287158419.13051.26.camel@wwguy-ubuntu> (raw)
In-Reply-To: <20101015145129.GA4046@redhat.com>

Hi Stanislaw,

On Fri, 2010-10-15 at 07:51 -0700, Stanislaw Gruszka wrote:
> Hello
> 
> On Thu, Oct 14, 2010 at 08:54:39AM -0700, Guy, Wey-Yi wrote:
> > > Any comments about iwl_update_chain_flags, iwl_bg_bt_full_concurrency ?
> > > I would like to know how to deal with them, should we deffer commit_rxon
> > > to scan complete, or cancel the scan. Or maybe this is no problem
> > > at all, because in example committing rxon vs scan was problem of
> > > older firmware?
> > > 
> > 
> > iwl_update_chain_flags() is used when PSP mode change,
> > iwl_bg_bt_full_concurrency() is used only for BT coex and in BT full
> > concurrency mode. For both case, I do not see any reason we can not
> > defer to scan complete.
> 
> I think deferring could be a bit hard for iwl_update_chain_flags, since
> according to the comments we need perform commit_rxon in order regarding
> other commands sending to the device.
> 
> Looking more closely at this:
> 
> * iwl_update_chain_flags is called from:
> 
> 1) iwl_chain_noise_calibration
> 2) iwlagn_bt_traffic_change_work 
> 3) iwl_power_update_mode
> 
> Ad 1) iwl_chain_noise_calibration:
> 
> Called only from iwl_bg_run_time_calib_work, we check STATUS_SCANNING
> there.

This should only call once when we first associate, and we check
STATUS_SCANNING, justlike you mention, should be ok

> 
> Ad 2) iwlagn_bt_traffic_change_work 
> 
> Queued as work from iwl_rx_scan_complete_notif, since scan_completed
> work is queued first we, should not have pending scan, as long as new
> scan request do not income in the maintime. Adding STATUS_SCANNING 
> check and return is probably what we need to prevent that corner case.
> 
Agree

> Ad 3) iwl_power_update_mode
> 
> Called from many places. In some of them we for sure not perform scanning,
> because we do the check or scan cancel before, or this is alive start.
> Fixing remaining calls and add WARNING in iwl_power_update_mode in is
> what I plan to do.
> 
> * iwl_bg_bt_full_concurrency is queued from rs_bt_update_lq. 
> 
> I think we can check if scanning is pending and schedule that work for
> late time, or set additional bit that we need to change full_concurrency,
> and based on that bit do bg_bt_full_concurrency from scan_completed.
> 

overall, I agree with your plan, for both iwl_bg_bt_full_concurrency and
iwlagn_bt_traffic_change_work can be delay to scan complete.

Thanks
Wey



  reply	other threads:[~2010-10-15 16:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-13 13:39 [PATCH 1/2] iwlwifi: fix set_tx_power vs scan Stanislaw Gruszka
2010-10-13 13:39 ` [PATCH 2/2] iwlwifi: one less commit_rxon while scan Stanislaw Gruszka
2010-10-14  8:42   ` Stanislaw Gruszka
2010-10-14 15:54     ` Guy, Wey-Yi
2010-10-15 14:51       ` Stanislaw Gruszka
2010-10-15 16:00         ` Guy, Wey-Yi [this message]
2010-10-13 15:18 ` [PATCH 1/2] iwlwifi: fix set_tx_power vs scan Guy, Wey-Yi
2010-10-14  8:32   ` Stanislaw Gruszka
2010-10-21 13:13     ` Stanislaw Gruszka
2010-10-21 14:26       ` Guy, Wey-Yi
2010-10-22 12:56       ` Stanislaw Gruszka
2010-10-22 14:39         ` Guy, Wey-Yi
2010-10-22 15:04           ` Stanislaw Gruszka
2010-10-22 16:51         ` Dan Williams

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=1287158419.13051.26.camel@wwguy-ubuntu \
    --to=wey-yi.w.guy@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --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 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).