From: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: Zefir Kurtisi <zefir.kurtisi@neratec.com>,
Zefir Kurtisi <zefir.kurtisi@gmail.com>,
linville@tuxdriver.com, ath9k-devel@lists.ath9k.org,
linux-wireless@vger.kernel.org, achadd@qca.qualcomm.com,
chunkeey@googlemail.com
Subject: Re: [PATCH 2/4] ath9k: set PHYRADAR in RX filter when on DFS channel
Date: Mon, 23 Apr 2012 11:28:04 -0700 [thread overview]
Message-ID: <20120423182804.GE9438@tux> (raw)
In-Reply-To: <4F95902E.7040806@openwrt.org>
On Mon, Apr 23, 2012 at 07:23:58PM +0200, Felix Fietkau wrote:
> On 2012-04-23 11:12 AM, Zefir Kurtisi wrote:
> > On 22.04.2012 22:00, Felix Fietkau wrote:
> >> On 2012-04-22 9:50 PM, Zefir Kurtisi wrote:
> >>> From: Zefir Kurtisi<zefir.kurtisi@neratec.com>
> >>>
> >>>
> >>> Signed-off-by: Zefir Kurtisi<zefir.kurtisi@neratec.com>
> >>> ---
> >>> drivers/net/wireless/ath/ath9k/recv.c | 6 ++++++
> >>> 1 files changed, 6 insertions(+), 0 deletions(-)
> >>>
> >>> diff --git a/drivers/net/wireless/ath/ath9k/recv.c b/drivers/net/wireless/ath/ath9k/recv.c
> >>> index f4ae3ba..ef45c0c 100644
> >>> --- a/drivers/net/wireless/ath/ath9k/recv.c
> >>> +++ b/drivers/net/wireless/ath/ath9k/recv.c
> >>> @@ -17,6 +17,7 @@
> >>> #include<linux/dma-mapping.h>
> >>> #include "ath9k.h"
> >>> #include "ar9003_mac.h"
> >>> +#include "dfs.h"
> >>>
> >>> #define SKB_CB_ATHBUF(__skb) (*((struct ath_buf **)__skb->cb))
> >>>
> >>> @@ -467,6 +468,11 @@ u32 ath_calcrxfilter(struct ath_softc *sc)
> >>> rfilt |= ATH9K_RX_FILTER_MCAST_BCAST_ALL;
> >>> }
> >>>
> >>> + if (sc->sc_ah->curchan->chan->flags& IEEE80211_CHAN_RADAR)
> >>> + rfilt |= ATH9K_RX_FILTER_PHYRADAR;
> >>> + else
> >>> + rfilt&= ~ATH9K_RX_FILTER_PHYRADAR;
> >> This should only be done in AP mode, maybe mac80211 should have a
> >> separate flag to tell the driver to enable this. Same comment also
> >> applies to patch 4/4.
> >>
> >> - Felix
> >>
> > Are you aware of any issues enabling DFS in client modes? My thinking
> > was that it won't hurt to detect radars in any mode and let the DFS
> > management component decide what to do with that events.
> Power consumption (for laptops), performance issues (due to DMA
> descriptor use and interrupts triggered by pulse detection).
>
> If the DFS management component decides what to do with the events, why
> not let it decide whether it actually wants events as well ;)
This could come from mac80211's filter flag call on to the driver, that is,
mac80211 can figure out when we need something like ATH9K_RX_FILTER_PHYRADAR
and tell us, instead of having the driver figure this out.
Luis
next prev parent reply other threads:[~2012-04-23 18:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 19:50 [PATCH 0/4] ath9k: integrate DFS detection Zefir Kurtisi
2012-04-22 19:50 ` [PATCH 1/4] ath9k: set detector DFS domain in reg notifyer Zefir Kurtisi
2012-04-22 19:50 ` [PATCH 2/4] ath9k: set PHYRADAR in RX filter when on DFS channel Zefir Kurtisi
2012-04-22 20:00 ` Felix Fietkau
2012-04-23 9:12 ` Zefir Kurtisi
2012-04-23 17:23 ` Felix Fietkau
2012-04-23 17:27 ` Chadd, Adrian
2012-04-23 18:28 ` Luis R. Rodriguez [this message]
2012-04-23 17:29 ` Christian Lamparter
2012-04-22 19:50 ` [PATCH 3/4] ath9k: forward pulse events to DFS pulse detector Zefir Kurtisi
2012-04-22 19:50 ` [PATCH 4/4] ath9k: set radar config if switching to DFS channel Zefir Kurtisi
2012-04-27 20:50 ` Adrian Chadd
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=20120423182804.GE9438@tux \
--to=rodrigue@qca.qualcomm.com \
--cc=achadd@qca.qualcomm.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=nbd@openwrt.org \
--cc=zefir.kurtisi@gmail.com \
--cc=zefir.kurtisi@neratec.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).