Received: by 2002:a05:6a10:8395:0:0:0:0 with SMTP id n21csp307502pxh; Tue, 9 Nov 2021 11:02:23 -0800 (PST) X-Google-Smtp-Source: ABdhPJyg9zvMhqMmc+1ebSVHrhHL+TyMWA1mUsVkG2fTFwRkRaeFK8alShPC3uW7QcKj5DmMSx3G X-Received: by 2002:a17:906:5d05:: with SMTP id g5mr12872030ejt.406.1636484543586; Tue, 09 Nov 2021 11:02:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1636484543; cv=none; d=google.com; s=arc-20160816; b=JodDFjhaqLL5BQoX21npgGeD5L8sZumUif2NaLLg/4tk6x4rXmP1Et+400KC00XS0u 7dyCE4MLdYouY3Nn1YM7JkgVA6DJXZKpEvA9bWKTaVscxlyvvu1vSaQrw+dL9hteYFzv CE6RyWsrkvTmGL7shiDAMccY/vuIjbmWPQD1wfbsP+6p9cvEnMnlgSnfqSavRhQl3Hhh pPY+K03CHLZLQTXKorCWQ+yBNvkmBqa5PfTSYKOdTQWw8VkrVQkaO78DEC9BT63vPXgJ EGM7skcauNlSp6aUIUPCSrxvbmL2PPhJGBc4rB1wRqpS5CD7CNytwstqysrqUOKVX4OF 34aA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:message-id:references:in-reply-to :subject:cc:to:from:date:content-transfer-encoding:mime-version :sender:dkim-signature; bh=JqO118YMY9m3B/RF52ZBcw2MCflSgzOhZYVVhgi3NZQ=; b=WSGVliBx+YlXMZHXnuTbc0N8mCpTnd7R7ggM00YNpXi5Xtwv5kfJaehKo/cFhA2YiM Nf9Dv0iqE9twsHGiY2GvjDbV5FjCsUv9udYX9hsKoOW5qFS5E5OqykJTR9oVEr1Incrl lhrZugkenPrjxJmGMdjRQjitr5Hv1bpfyV9vP0gWcKg70GOX2n21lj8+Ee4/WWOgkBks q0nQOJ77ZdS8jwtCATIxif9bsA+wzAMyEiCSiL4nPJf5+ROunybZSfjNsureO1/ThpJo i71UKZ5+YRhJI0XMOVyofj+T+eqJW5UzoSeH7NXcJlrlmMKCEXYvguRbAzG64sMNTG3N LGzQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@mg.codeaurora.org header.s=smtp header.b=qkUqNFIG; 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 u6si30676952edt.370.2021.11.09.11.02.06; Tue, 09 Nov 2021 11:02:23 -0800 (PST) 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; dkim=pass header.i=@mg.codeaurora.org header.s=smtp header.b=qkUqNFIG; 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 S243772AbhKIKAM (ORCPT + 68 others); Tue, 9 Nov 2021 05:00:12 -0500 Received: from so254-9.mailgun.net ([198.61.254.9]:47392 "EHLO so254-9.mailgun.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241704AbhKIKAL (ORCPT ); Tue, 9 Nov 2021 05:00:11 -0500 DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=mg.codeaurora.org; q=dns/txt; s=smtp; t=1636451846; h=Message-ID: References: In-Reply-To: Subject: Cc: To: From: Date: Content-Transfer-Encoding: Content-Type: MIME-Version: Sender; bh=JqO118YMY9m3B/RF52ZBcw2MCflSgzOhZYVVhgi3NZQ=; b=qkUqNFIGjgF6xak5Plf7ItoRDmJf/379oTF2ntW5iryLnmnmQ9CBCluAMd1STztU6yIiaCe0 mTvem23sD1vxQ88F9lGXTtwclsQlrsqBNuEIiN8h4AjXpzg/x9SOaIe6b9AOkoMZ1Z3KKYmw C61doqUd9JlNNQXGIdKrSduOrOY= X-Mailgun-Sending-Ip: 198.61.254.9 X-Mailgun-Sid: WyI3YTAwOSIsICJsaW51eC13aXJlbGVzc0B2Z2VyLmtlcm5lbC5vcmciLCAiYmU5ZTRhIl0= Received: from smtp.codeaurora.org (ec2-35-166-182-171.us-west-2.compute.amazonaws.com [35.166.182.171]) by smtp-out-n06.prod.us-west-2.postgun.com with SMTP id 618a45f7facd20d795fb3210 (version=TLS1.2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256); Tue, 09 Nov 2021 09:57:11 GMT Sender: wgong=codeaurora.org@mg.codeaurora.org Received: by smtp.codeaurora.org (Postfix, from userid 1001) id CB2C1C4361A; Tue, 9 Nov 2021 09:57:11 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-caf-mail-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=2.0 tests=ALL_TRUSTED,BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: wgong) by smtp.codeaurora.org (Postfix) with ESMTPSA id 09C81C4338F; Tue, 9 Nov 2021 09:57:10 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 09 Nov 2021 17:57:10 +0800 From: Wen Gong To: Johannes Berg Cc: Venkateswara Naralasetty , Venkateswara Naralasetty , ath11k@lists.infradead.org, linux-wireless@vger.kernel.org, wgong=codeaurora.org@codeaurora.org Subject: Re: [PATCH v5] cfg80211: save power spectral density(psd) of regulatory rule In-Reply-To: <67936afa5545b9a5d6eb5ad6931026d7@codeaurora.org> References: <20210928085211.26186-1-wgong@codeaurora.org> <2afb1bf6f06cb53f43fe0d354afa4e7c@codeaurora.org> <2ed76cff292dcca18326de0407a93821@codeaurora.org> <1222384c2bc7d80bf572b65ab17660477bb27300.camel@sipsolutions.net> <562080d7fc3b7568811c47a8e8e79156@codeaurora.org> <0b05f6e555bcb89c49f56279c077ce63@codeaurora.org> <18363bc18538ea9b7e8fe28f4c5595c54f3b93d3.camel@sipsolutions.net> <67936afa5545b9a5d6eb5ad6931026d7@codeaurora.org> Message-ID: <6053b0963612057267f00b89e14b9e15@codeaurora.org> X-Sender: wgong@codeaurora.org User-Agent: Roundcube Webmail/1.3.9 Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Hi Johannes, do you have comments about my description for PSD? On 2021-10-26 19:26, Wen Gong wrote: > On 2021-10-26 04:09, Johannes Berg wrote: >> On Mon, 2021-10-11 at 15:48 +0800, Wen Gong wrote: >>> >>> > IMO, Only power rules and PSD info might vary for AP and STATION. Rest >>> > of the rules will remains same right? >>> > >>> The freq_range may also be different for AP and STATION. >>> and reg_rules number also may also be different for AP and STATION. >>> >>> for example: >>> SUBORDINATE CLIENT of STANDARD POWER reg rules number 2 >>> reg rule 1: (5945 - 6425 @ 160) (0, 30) (FLAGS 0) (psd flag 1 EIRP 17 >>> dB/MHz) >>> reg rule 2: (6525 - 6885 @ 160) (0, 30) (FLAGS 0) (psd flag 1 EIRP 17 >>> dB/MHz) >>> >>> INDOOR AP reg rules number 1 >>> reg rule 1: (5945 - 7125 @ 160) (0, 24) (FLAGS 0) (psd flag 0 EIRP 0 >>> dB/MHz) >> >> That seems right, but isn't that an orthogonal question? >> >> Here, on this patch, we're discussing what data we should have in the >> channel information, and it would seem that if it's different for >> AP/client, then we do need both information stored, so that we can >> cope >> with concurrency between AP and client? >> >> If we additionally need to have different data for the regulatory >> rules >> for AP and client, that might mean we need to go back and actually >> change the code there *as well*, and then fill in the right fields in >> this patch? >> >> Unless somehow we're convinced that for this feature we don't need to >> worry about concurrently using AP and client modes? >> >> johannes > > Currently these patches of mac80211/cfg80211/ieee80211 for LPI/SP/VLP > is > the base patches, to enable the feature of LPI/SP/VLP, it still need > other > patches of lower drivers such as ath11k to enable it. It will not have > LPI/SP/VLP without patches of ath11k, it means all these patches will > not take effect. > > When lower driver such as ath11k set max_interfaces of > ieee80211_iface_combination > to 1, then it can not start more than 1 interface on the same > ieee80211_hw/wiphy. > When STATION interface is up, then AP interface can not start up. AP > interface > can start up after STATION interfacedown. Also when AP interface is up, > STATION interface can not start up. STATION interface can start up > after > AP interface down. > > I have sent out my ath11k > patches(https://lore.kernel.org/linux-wireless/20211026111913.7346-1-quic_wgong@quicinc.com/), > it will allow only one interface > up simultaneously for the chip which enable LPI/SP/VLP feature in this > patch: "ath11k: allow only one interface up simultaneously for WCN6855" > https://lore.kernel.org/linux-wireless/20211026111913.7346-5-quic_wgong@quicinc.com/ > It means it will not have both AP/STA together and these patches of > mac80211/ > cfg80211/ieee80211 not need changes and it will not have bugs. > > If there are some chip want to both enable LPI/SP/VLP feature and > enable AP/STA simultaneously in same ieee80211_hw/wiphy in future, > then he/she need to refine reg rules and channels of mac80211/cfg80211/ > ieee80211, but at that moment, this patch "cfg80211: save power > spectral density(psd) of regulatory rule" still not need change. > Because this patch is change in each reg rule/each channel in a > low layer, the refine reg rules and channels is a high layer, they > have no intersection.