Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Message-ID: <53d45563803b3f96be0d53731408cc3af028c510.camel@sipsolutions.net>
Subject: Re: [PATCH v2 0/2] add Wide Band Scan support
From:   Johannes Berg <johannes@sipsolutions.net>
To:     Sathishkumar Muruganandam <murugana@codeaurora.org>
Cc:     linux-wireless@vger.kernel.org, ath11k@lists.infradead.org
Date:   Mon, 04 Nov 2019 13:11:49 +0100
In-Reply-To: <1572869374-9635-1-git-send-email-murugana@codeaurora.org>
References: <1572869374-9635-1-git-send-email-murugana@codeaurora.org>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.30.5 (3.30.5-1.fc29) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

On Mon, 2019-11-04 at 17:39 +0530, Sathishkumar Muruganandam wrote:
> Wide Band Scan allows to perform off-channel scan on requested channel/
> frequency along with corresponding phy mode/bandwidth (40Mhz, 80Mhz).
> 
> Below are use cases of Wide Band Scan,
> 
> 1. In case of phy running both AP and monitor vifs, wide band scan on
>    a different channel along with phymode (40Mhz, 80Mhz) captures
>    those off-channel data frames to monitor vif.
> 
> 2. Doing wide band scan instead of normal 20Mhz scan before spectral
>    dump, allows to fetch FFT reports for the complete requested
>    bandwidth (40Mhz, 80Mhz).

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

johannes