ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: Sven Eckelmann <sven@narfation.org>
Cc: Mathias Kretschmer <mathias.kretschmer@fokus.fraunhofer.de>,
	"Giori, Kathy" <kgiori@qca.qualcomm.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Michal Kazior <michal.kazior@tieto.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [RFC 0/2] ath10k spectral scan support
Date: Wed, 16 Jul 2014 10:38:09 +0200	[thread overview]
Message-ID: <201407161038.10130.sw@simonwunderlich.de> (raw)
In-Reply-To: <4111404.UJkIUxkzQm@bentobox>


> On Wednesday 16 July 2014 08:24:58 Michal Kazior wrote:
> > >  * 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?
> > 
> > Hmm.. I suspect this may be because you use scan command. Scanning
> > uses channel list which is programmed with legacy modes a and g
> > (implying 20Mhz). Perhaps that's the limiting factor now. Using other
> > (wider) modes breaks scan from what I remember but it might be worth
> > checking out if it impacts fft bin sizes.
> 
> I did the HT80 and HT40 stuff on a single channel in the spectral
> "background" mode. They reports from the firmware (10.1) still only had 64
> bins. The HT80 stuff wasn't tested with the "main" firmware because it
> refused to switch to HT80 mode as AP/Sta.

Just to clarify this a little more, we tried AP (running hostapd) as well a 
STA in 40 and 80 MHz modes. We always got 64 bins returned.

Cheers,
    Simon

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

  reply	other threads:[~2014-07-16  8:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15 16:32 [RFC 0/2] ath10k spectral scan support Simon Wunderlich
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 [this message]
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=201407161038.10130.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=michal.kazior@tieto.com \
    --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