ath10k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: ath10k@lists.infradead.org
Cc: mathias.kretschmer@fokus.fraunhofer.de, kgiori@qca.qualcomm.com,
	linux-wireless@vger.kernel.org, sven@narfation.org,
	Simon Wunderlich <sw@simonwunderlich.de>
Subject: [RFC 0/2] ath10k spectral scan support
Date: Tue, 15 Jul 2014 18:32:44 +0200	[thread overview]
Message-ID: <1405441966-32681-1-git-send-email-sw@simonwunderlich.de> (raw)

This is the first patchset iteration for review to implement the ath10k
spectral scan feature. The patchset is still experimental, but we were
able to detect our analogue 5.8 GHz TV repeater in the sample data. :)

As for ath9k, a proof of concept data plotter has been implemented, and
is currently available for ath10k in its own branch of FFT_eval [1].

There are a few open questions, and any help or pointers would be
appreciated:

 * so far, we could only enable endless mode (samples are sent
   endlessly). To prevent relayfs buffers overflowing because they are
   not read from userspace, it would be great to set a "count" to limit
   the number of samples sent after a trigger. That was possible in
   ath9k as well. However, if we set the "scan_count" parameter in the
   WMI command to something else than 0 (default), we don't get any
   samples at all. Is there any other configuration which needs to be
   done to get a limited number of samples?
 * So far, we always get 64 bins of fft data in the samples, even if we
   are in HT40 or VHT80 mode. That doesn't seem right, as there should
   be more bins for wider channels (e.g. 128 or 256 bins). Is there any
   parameter to change in the configuration to get the output from
   multiple channels / higher bandwidth?

Kudos to Kalle and Michal for their help to get this started. :)

Cheers,
     Simon

[1] https://github.com/simonwunderlich/FFT_eval/tree/ath10k_wip

Sven Eckelmann (2):
  ath: Move spectral debugfs structs to shared header
  ath10k: add spectral scan feature

 drivers/net/wireless/ath/ath10k/Kconfig    |   1 +
 drivers/net/wireless/ath/ath10k/Makefile   |   3 +-
 drivers/net/wireless/ath/ath10k/core.h     |   6 +
 drivers/net/wireless/ath/ath10k/debug.c    |   3 +
 drivers/net/wireless/ath/ath10k/spectral.c | 368 +++++++++++++++++++++++++++++
 drivers/net/wireless/ath/ath10k/spectral.h |  66 ++++++
 drivers/net/wireless/ath/ath10k/wmi.c      |  98 +++++++-
 drivers/net/wireless/ath/ath10k/wmi.h      |  80 +++++++
 drivers/net/wireless/ath/ath9k/spectral.h  |  71 +-----
 drivers/net/wireless/ath/spectral_common.h | 108 +++++++++
 10 files changed, 733 insertions(+), 71 deletions(-)
 create mode 100644 drivers/net/wireless/ath/ath10k/spectral.c
 create mode 100644 drivers/net/wireless/ath/ath10k/spectral.h
 create mode 100644 drivers/net/wireless/ath/spectral_common.h

-- 
1.9.1


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

             reply	other threads:[~2014-07-15 16:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15 16:32 Simon Wunderlich [this message]
2014-07-15 16:32 ` [RFC 1/2] ath: Move spectral debugfs structs to shared header Simon Wunderlich
2014-07-15 16:32 ` [RFC 2/2] ath10k: add spectral scan feature Simon Wunderlich
2014-07-16  9:30   ` Michal Kazior
2014-07-16 14:35     ` Sven Eckelmann
2014-07-17  5:34       ` Michal Kazior
2014-07-16  6:24 ` [RFC 0/2] ath10k spectral scan support Michal Kazior
2014-07-16  8:25   ` Sven Eckelmann
2014-07-16  8:38     ` Simon Wunderlich
2014-07-16  8:56       ` Michal Kazior
2014-07-18 10:26 ` Janusz Dziedzic

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=1405441966-32681-1-git-send-email-sw@simonwunderlich.de \
    --to=sw@simonwunderlich.de \
    --cc=ath10k@lists.infradead.org \
    --cc=kgiori@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mathias.kretschmer@fokus.fraunhofer.de \
    --cc=sven@narfation.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).