linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Felix Fietkau <nbd@openwrt.org>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
	linux-wireless@vger.kernel.org, linville@tuxdriver.com,
	greearb@candelatech.com
Subject: Re: [PATCH 2.6.39] mac80211: always clear PS filtering for non-AP interfaces
Date: Fri, 06 May 2011 15:43:22 +0200	[thread overview]
Message-ID: <1304689402.3595.12.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4DC3F93B.10308@openwrt.org>

On Fri, 2011-05-06 at 15:35 +0200, Felix Fietkau wrote:

> >>  >>   +		info->flags |= IEEE80211_TX_CTL_CLEAR_PS_FILT;

> Rely on what being set in AP mode only? The patch ensures that the flag 
> for *clearing* PS filtering gets set for all non-AP modes. This flag 
> already gets set whenever tx->sta is unset, so I think it also makes 
> sense to extend that for other cases where the hardware is not supposed 
> to enable any PS filtering on its own.

I didn't remember/know about the case where sta is unset, but still,
what if the driver checks for the flag and does something that's only
valid in AP mode? I'm thinking firmware API here, not HW like ath9k.

> > Your patch makes those drivers responsible for checking the mode, but
> > that makes less sense than having drivers that need to do some magic in
> > all modes, no?
> How does my patch make drivers responsible for checking the mode?

Well, say I implement the clearing by sending something command to the
device, like p54. If that's only valid in AP mode in the firmware, now
this driver has to check that it's AP mode, where before it didn't have
to. That's not counting the sta==NULL case I guess.

OTOH, we only have two drivers using the flag anyway. Go figure it out
between those two :)

johannes


  reply	other threads:[~2011-05-06 13:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06  0:41 [PATCH 2.6.39] mac80211: always clear PS filtering for non-AP interfaces Felix Fietkau
2011-05-06  8:39 ` Johannes Berg
2011-05-06 13:08 ` Christian Lamparter
2011-05-06 13:20   ` Felix Fietkau
2011-05-06 13:26     ` Johannes Berg
2011-05-06 13:35       ` Felix Fietkau
2011-05-06 13:43         ` Johannes Berg [this message]
2011-05-06 13:47           ` Felix Fietkau
2011-05-06 15:53             ` Christian Lamparter

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=1304689402.3595.12.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=chunkeey@googlemail.com \
    --cc=greearb@candelatech.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=nbd@openwrt.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;
as well as URLs for NNTP newsgroup(s).