ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Sathishkumar Muruganandam" <murugana@codeaurora.org>
To: 'Johannes Berg' <johannes@sipsolutions.net>
Cc: murugana@codeaurora.org, linux-wireless@vger.kernel.org,
	ath11k@lists.infradead.org
Subject: RE: [EXT] Re: [PATCH v2 0/2] add Wide Band Scan support
Date: Tue, 5 Nov 2019 15:51:04 +0530	[thread overview]
Message-ID: <00d301d593c2$bd37d8f0$37a78ad0$@codeaurora.org> (raw)
In-Reply-To: <53d45563803b3f96be0d53731408cc3af028c510.camel@sipsolutions.net>

> Neither of these are scan use cases (at least not that are covered by
> nl80211 scan APIs), so that doesn't make sense.
> 

Actually we had extended the existing 'iw scan' command to do Wide Band Scan using nl80211 scan APIs.

dev <devname> scan freq <freq> [HT40+|HT40-|80MHz] [ap-force]

dev <devname> scan trigger freq <freq> [HT40+|HT40-|80MHz] [ap-force]

Raised patch for above change, [PATCH] iw: Add phymode parameters to scan command for Wide Band Scan support.

--
Sathishkumar


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

  reply	other threads:[~2019-11-05 10:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 12:09 [PATCH v2 0/2] add Wide Band Scan support Sathishkumar Muruganandam
2019-11-04 12:09 ` [PATCH v2 1/2] nl80211: " Sathishkumar Muruganandam
2019-11-04 12:09 ` [PATCH v2 2/2] ath11k: " Sathishkumar Muruganandam
2019-11-04 12:11 ` [PATCH v2 0/2] " Johannes Berg
2019-11-05 10:21   ` Sathishkumar Muruganandam [this message]
2019-11-05 10:22     ` [EXT] " Johannes Berg
2019-11-11  7:57       ` Sathishkumar Muruganandam
2019-11-14  6:38         ` Johannes Berg
2019-11-14 12:33           ` Sathishkumar Muruganandam
2019-11-22 12:45             ` Johannes Berg

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='00d301d593c2$bd37d8f0$37a78ad0$@codeaurora.org' \
    --to=murugana@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.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