public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/1] mac80211: tell driver when dtim change detected
Date: Thu, 21 Jan 2010 08:34:13 -0800	[thread overview]
Message-ID: <1264091653.7735.6.camel@wwguy-ubuntu> (raw)
In-Reply-To: <1264091564.11396.58.camel@johannes.local>

Hi Johannes,

Agree, only iwlwifi use the dtim information now, but not sure it will
be always true. Yes, we should recalculate the internal power save when
it happen, I will make the changes and re-submit

On Thu, 2010-01-21 at 08:32 -0800, Johannes Berg wrote:
> On Thu, 2010-01-21 at 07:51 -0800, wey-yi.w.guy@intel.com wrote:
> > From: Wey-Yi Guy <wey-yi.w.guy@intel.com>
> > 
> > In current implementation, mac80211 send dtim_period update to driver during
> > association, but if no NetworkManager or similar application perform scan
> > operation, plus tim_ie is not part of probe response; mac80211 will not get
> > beacon with dtim information later, then  mac80211 will not pass the 
> > information to driver for update.
> 
> Good catch.
> 
> > Call ieee80211_hw_config() with IEEE80211_CONF_CHANGE_PS flag set to
> > allow driver make correct dtim adjustment if dtim_period change detected.
> 
> I don't think this is the right place or the right thing to do though,
> this seems like an implementation detail from iwlwifi -- it only (and
> maybe only it) uses the DTIM interval for power saving.
> 
> However, the internal power saving stuff from mac80211 should also be
> recalculated if this happens, and then we can probably call it a PS
> change?
> 
> johannes


      reply	other threads:[~2010-01-21 16:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-21 15:51 [PATCH 1/1] mac80211: tell driver when dtim change detected wey-yi.w.guy
2010-01-21 16:32 ` Johannes Berg
2010-01-21 16:34   ` Guy, Wey-Yi [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=1264091653.7735.6.camel@wwguy-ubuntu \
    --to=wey-yi.w.guy@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.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