Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp3606800pxk; Tue, 29 Sep 2020 01:05:59 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxHn8uSLsNC0rMhEsZQFATwf0nRW7Jla2S8DoQbJuqpcw7L2GipDvpd9+nCBcqWbYIVirc7 X-Received: by 2002:aa7:c444:: with SMTP id n4mr1953850edr.200.1601366759459; Tue, 29 Sep 2020 01:05:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1601366759; cv=none; d=google.com; s=arc-20160816; b=BP6cenoNtFxfxlH6Af1mhvpWZR7YH6ST/L1XBL9W/Jnjoe8PEyO09+nqgqu0wsnHhA 0152H94ICyWiXksj0dA4MW8v0xY/SmybUMOda7c8x9uw3Lvp8h66WT8TzTsLaATWhshz MQ+BNrP2jY84099/t8B9Ux2JKPjVU8yYMFRnyB1Ol9ZixfJplSM6dw761dEwSXk4xPRY chV/4LH0U6+pDEATQCVzO1A/KdjARp/eWfR01NGrty/GU7FVFaOJuP+iRvVNZAkU+wvd vWzpSq4RaSzp9zQBJhVDsgg5vRigyu4bbnAKNEQ3ThAlwI0Ui6dRkMnHfhQkLav5LKvp Xd5w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=GEUqh9Lh9CkOqVJ2WWleWlxRmkMXXC9sQJiqiIKuoSY=; b=OIpVXofecC1+pjW4GQfpL+Tzjg8f5hJzYMYaxaLvCIZVFIWJ/d/xXQDEjgXOYhD3wA HZLqyO9r5eYg+eqjV3gI+HIY7WtnQWagGsx9g7hURysSVxxziM2wZ1zv2WkfGxnK1Chj NnZYmUaMDcHP2iP4MPPt4YR3k2p4i4mBgwswsGaZC754Nkca54FlzIl/RsO6FDvCVATx kyPMXavjRHPrNWD8lONUomFmrn8MwfmOkEXdeOSIewVz4gfT5kWcuhjAuMYIp8gTXE/F RPgek8aOQLgAVPOqzHyhQW4DssTFfdBLxfsdAkZ0yYetglByUNv0ByHvK0BSUPXZApgf olhA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id kt7si2228366ejb.282.2020.09.29.01.05.29; Tue, 29 Sep 2020 01:05:59 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727495AbgI2IEk (ORCPT + 99 others); Tue, 29 Sep 2020 04:04:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33208 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726064AbgI2IEk (ORCPT ); Tue, 29 Sep 2020 04:04:40 -0400 Received: from sipsolutions.net (s3.sipsolutions.net [IPv6:2a01:4f8:191:4433::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ED5C1C061755 for ; Tue, 29 Sep 2020 01:04:39 -0700 (PDT) Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.94) (envelope-from ) id 1kNAcg-00CyHn-0N; Tue, 29 Sep 2020 10:04:30 +0200 Message-ID: Subject: Re: [PATCHv2 1/2] nl80211: vendor-cmd: qca: add command for ap power save From: Johannes Berg To: Kalle Valo Cc: Venkateswara Naralasetty , ath11k@lists.infradead.org, linux-wireless@vger.kernel.org Date: Tue, 29 Sep 2020 10:04:14 +0200 In-Reply-To: <871rilf2th.fsf@codeaurora.org> References: <1598257589-19091-1-git-send-email-vnaralas@codeaurora.org> <4b4a0d79a243c1c3b8044730da0493c96ba294bf.camel@sipsolutions.net> <871rilf2th.fsf@codeaurora.org> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-1.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Tue, 2020-09-29 at 10:40 +0300, Kalle Valo wrote: > Johannes Berg writes: > > > On Mon, 2020-08-24 at 13:56 +0530, Venkateswara Naralasetty wrote: > > > AP power save feature is to save power in AP mode, where AP goes > > > to power save mode when no stations associate to it and comes out > > > of power save when any station associate to AP. > > > > Why do you think this requires a vendor command? I mean, that seems like > > fairly reasonable - even by default - behaviour? > > I have not studied the details, but doesn't AP power save break normal > functionality? For example, I would guess probe requests from clients > would be lost. So there's a major drawback when enabling this, right? Not the way it's described above? johannes