From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from smtp.codeaurora.org ([198.145.29.96]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1iU4ZS-0001C2-Nh for ath11k@lists.infradead.org; Mon, 11 Nov 2019 07:57:11 +0000 MIME-Version: 1.0 Date: Mon, 11 Nov 2019 13:27:09 +0530 From: Sathishkumar Muruganandam Subject: Re: [EXT] Re: [PATCH v2 0/2] add Wide Band Scan support In-Reply-To: <867302d58d3183ce7e2c7afa846027a787579b87.camel@sipsolutions.net> References: <1572869374-9635-1-git-send-email-murugana@codeaurora.org> <53d45563803b3f96be0d53731408cc3af028c510.camel@sipsolutions.net> <00d301d593c2$bd37d8f0$37a78ad0$@codeaurora.org> <867302d58d3183ce7e2c7afa846027a787579b87.camel@sipsolutions.net> Message-ID: <6ea305b2ac09c340181623a23cf4180b@codeaurora.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "ath11k" Errors-To: ath11k-bounces+kvalo=adurom.com@lists.infradead.org To: Johannes Berg Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org On 2019-11-05 15:52, Johannes Berg wrote: > On Tue, 2019-11-05 at 15:51 +0530, Sathishkumar Muruganandam wrote: >> > 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. > > Yes ... but ... that doesn't address my question. > > How is this related to scanning? It sounds to me like you're just > (ab)using scan as a somewhat convenient "do some channel hopping" API > ... > Whether this can be used under "iw offchannel" with NL80211_CMD_REMAIN_ON_CHANNEL? Please provide your comments. -- Thanks, Sathishkumar _______________________________________________ ath11k mailing list ath11k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath11k From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0BF00C43331 for ; Mon, 11 Nov 2019 07:57:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D204A2075C for ; Mon, 11 Nov 2019 07:57:11 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="key not found in DNS" (0-bit key) header.d=codeaurora.org header.i=@codeaurora.org header.b="HYFWrgGm"; dkim=fail reason="key not found in DNS" (0-bit key) header.d=codeaurora.org header.i=@codeaurora.org header.b="HYFWrgGm" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726819AbfKKH5K (ORCPT ); Mon, 11 Nov 2019 02:57:10 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:35014 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726808AbfKKH5K (ORCPT ); Mon, 11 Nov 2019 02:57:10 -0500 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id D06B4608CC; Mon, 11 Nov 2019 07:57:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1573459029; bh=S7KBTQ03krYSdg5c3dcqLbjEuC0Jp7OQePSlRrVO7p4=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=HYFWrgGmClU1T9ySkNYxE0bE3Rx/rZSd86HBP3xCFJ1Lra4vd0rYwdc+eWda3c+aL jY+Qh9i0WKSqgnHPHsOoSd5gBWvQspmLrSEK5GNBtLOHUpMrjpfTplEBlWyTUAjUjK ZE3L07JrWh1iU7VFZDiEMQAkRdX2Xr7Ex88dX70o= Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.codeaurora.org (Postfix) with ESMTP id 634D66087D; Mon, 11 Nov 2019 07:57:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1573459029; bh=S7KBTQ03krYSdg5c3dcqLbjEuC0Jp7OQePSlRrVO7p4=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=HYFWrgGmClU1T9ySkNYxE0bE3Rx/rZSd86HBP3xCFJ1Lra4vd0rYwdc+eWda3c+aL jY+Qh9i0WKSqgnHPHsOoSd5gBWvQspmLrSEK5GNBtLOHUpMrjpfTplEBlWyTUAjUjK ZE3L07JrWh1iU7VFZDiEMQAkRdX2Xr7Ex88dX70o= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 11 Nov 2019 13:27:09 +0530 From: Sathishkumar Muruganandam To: Johannes Berg Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org Subject: Re: [EXT] Re: [PATCH v2 0/2] add Wide Band Scan support In-Reply-To: <867302d58d3183ce7e2c7afa846027a787579b87.camel@sipsolutions.net> References: <1572869374-9635-1-git-send-email-murugana@codeaurora.org> <53d45563803b3f96be0d53731408cc3af028c510.camel@sipsolutions.net> <00d301d593c2$bd37d8f0$37a78ad0$@codeaurora.org> <867302d58d3183ce7e2c7afa846027a787579b87.camel@sipsolutions.net> Message-ID: <6ea305b2ac09c340181623a23cf4180b@codeaurora.org> X-Sender: murugana@codeaurora.org User-Agent: Roundcube Webmail/1.2.5 Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On 2019-11-05 15:52, Johannes Berg wrote: > On Tue, 2019-11-05 at 15:51 +0530, Sathishkumar Muruganandam wrote: >> > 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. > > Yes ... but ... that doesn't address my question. > > How is this related to scanning? It sounds to me like you're just > (ab)using scan as a somewhat convenient "do some channel hopping" API > ... > Whether this can be used under "iw offchannel" with NL80211_CMD_REMAIN_ON_CHANNEL? Please provide your comments. -- Thanks, Sathishkumar