linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zefir Kurtisi <zefir.kurtisi@gmail.com>
To: linville@tuxdriver.com
Cc: ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org,
	rodrigue@qca.qualcomm.com, achadd@qca.qualcomm.com,
	chunkeey@googlemail.com,
	Zefir Kurtisi <zefir.kurtisi@neratec.com>
Subject: [PATCH 0/4] ath9k: integrate DFS detection
Date: Sun, 22 Apr 2012 21:50:19 +0200	[thread overview]
Message-ID: <1335124223-15439-1-git-send-email-zefir.kurtisi@gmail.com> (raw)

From: Zefir Kurtisi <zefir.kurtisi@neratec.com>

These are the remaining knobs required to turn to get DFS
detection working in ath9k.

---

Testing mini-HowTo

Building:
On top of the patches, building a DFS capable driver requires
* setting CONFIG_ATH9K_DFS_CERTIFIED=y
* change hw.c:ath9k_hw_dfs_tested() to return true for the
  chip-set you are testing
  (tested so far: AR9280, AR9390 and AR9580)

Setting CONFIG_ATH_DEBUG=y will allow you to log detailed pulse
event information by setting the DFS_DEBUG bit (0x20000) in
ath9k/debug, while radar detection events are logged generally.

Also, set CONFIG_ATH9K_DFS_DEBUGFS=y to enable pulse and
pattern detection statistics along with pool utilization stats
in phyX/ath9k/dfs_stats. Ensure to have recent
'[PATCH] ath9k: extend DFS detector stats in dfs_debugfs'
applied for the full set of DFS statistics.

Testing:
You need wireless tools built with
* crda: add support to send DFS master region
* wireless-regdb: Add master DFS region support
* wireless-regdb: set ETSI as DFS region for EU
(all upstream since 2012-01)

1) setup ath9k monitor
   sudo iw phy phy0 interface add moni0 type monitor
   sudo iw dev moni0 set freq 5500 HT20
   sudo ifconfig moni0 up
2) set ETSI countrycode, e.g.
   sudo iw reg set CH
3) fire some ETSI radars at device and check log and dfs_stats


Note: due to the lack of DFS master support, only monitor mode
      can be tested. Furthermore, at this stage the detector
      supports ETSI defined radar patterns only. With other
      DFS domains you still are able to test pulse detections,
      but any pulse event will be accounted as radar event
      in the stats/logs.

Zefir Kurtisi (4):
  ath9k: set detector DFS domain in reg notifyer
  ath9k: set PHYRADAR in RX filter when on DFS channel
  ath9k: forward pulse events to DFS pulse detector
  ath9k: set radar config if switching to DFS channel

 drivers/net/wireless/ath/ath9k/init.c |    4 ++++
 drivers/net/wireless/ath/ath9k/main.c |   10 ++++++++++
 drivers/net/wireless/ath/ath9k/recv.c |    9 +++++++++
 3 files changed, 23 insertions(+), 0 deletions(-)

-- 
1.7.4.1


             reply	other threads:[~2012-04-22 19:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-22 19:50 Zefir Kurtisi [this message]
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
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=1335124223-15439-1-git-send-email-zefir.kurtisi@gmail.com \
    --to=zefir.kurtisi@gmail.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=rodrigue@qca.qualcomm.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).