Received: by 2002:a05:6a11:4021:0:0:0:0 with SMTP id ky33csp795287pxb; Wed, 29 Sep 2021 09:48:27 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwSMww5XsDm//2L6W67/SYzGIrvcN/waZ5KC6pVrfni32RVhhX/zrKCmDBEMNzJ/53s0tqu X-Received: by 2002:a17:90a:307:: with SMTP id 7mr985186pje.176.1632934107287; Wed, 29 Sep 2021 09:48:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1632934107; cv=none; d=google.com; s=arc-20160816; b=NVguV9c4i2qbUvOYu+gxSnn3HWlNVM3Ci7yckrYDsfJpILnjI5Xa25zkIdiGqCw0yT 0ldb38h2YVxzKzuB1mBAbqonXbTCxmjjthzqjaMTyP/XQCcp5KT3ot3vcuAGk+MWEUpH ACDv4cGaUp4c1xNHpB1+fqgx0iP/ieKqkYW2LsCFbzuGcCJUBqcAoOGTypZXlJzxO+ln QksWpOTqhOqs/wUzpDvMQlMR6LSAppyGn0KsaMhdzJDiXgXI+siLcikwgRaScmseLTwr QT1SSQ17hJ7aEAt7nDNbPq7f1V+VJgHL3wfJcj5vHDRIceGZ4mW+8OgxIyHmbQcukgar z5xg== 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=hENbf6DLHZQ9EDwLZm4d/dfWRbeRGqIPP0WtfVX8Mp0=; b=bBs/DilNevr3wZsOkgDseU4QWaYXkI+saA0IfquuSieOj3s8x9xBnEIuj8QH4VvGPx 8gsBXLUQ7F3LFXuGiuwQMGmMtOUBdXcKYokexVETCEzZsSOc2Qin0YsPt4cN7g6d+Cck HQa79uG186ENcnx3KwBrIR3EILl54lJKHfVOJ38Rlgx7tlNNyeIGql5wBh3vsN3NAUKo OCzWSSmXl7nCWtzG/phQxnOqzJwGeJpoNrvP4nXJuWxgVxQolB0ClM2ENXSJBVrKNd8p IG+g5is8+JkNw+QKNPfvRA6JRH914CNgBBzs4hOcPXc0inlS91vvOZOM0fC0zhczWau/ u0Cw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@mg.codeaurora.org header.s=smtp header.b=Bd9L6Pjk; 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 u2si520861plk.33.2021.09.29.09.48.12; Wed, 29 Sep 2021 09:48:27 -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; dkim=pass header.i=@mg.codeaurora.org header.s=smtp header.b=Bd9L6Pjk; 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 S1346238AbhI2Qs3 (ORCPT + 78 others); Wed, 29 Sep 2021 12:48:29 -0400 Received: from so254-9.mailgun.net ([198.61.254.9]:59204 "EHLO so254-9.mailgun.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1345986AbhI2QsQ (ORCPT ); Wed, 29 Sep 2021 12:48:16 -0400 DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=mg.codeaurora.org; q=dns/txt; s=smtp; t=1632933995; h=Message-ID: References: In-Reply-To: Subject: Cc: To: From: Date: Content-Transfer-Encoding: Content-Type: MIME-Version: Sender; bh=hENbf6DLHZQ9EDwLZm4d/dfWRbeRGqIPP0WtfVX8Mp0=; b=Bd9L6PjkP38SKN1MeKHbd/i2nKi7hREmGfn5mLEKRMEaa76UJx8flYVjLdVBaukqUlvMMc1M Ddf6Uw/hksW2DlEflLp63Nzj1f4ryXfunfC9QI4J+utYiBeE9YxLgilvj0IYb76C46WOVPQM Mj0XHc9vbX0/VrK0e+SC8kqeFjc= 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-n04.prod.us-west-2.postgun.com with SMTP id 61549869519bd8dcf0430505 (version=TLS1.2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256); Wed, 29 Sep 2021 16:46:33 GMT Sender: vnaralas=codeaurora.org@mg.codeaurora.org Received: by smtp.codeaurora.org (Postfix, from userid 1001) id 5CFD3C4360D; Wed, 29 Sep 2021 16:46:33 +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, URIBL_BLOCKED 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: vnaralas) by smtp.codeaurora.org (Postfix) with ESMTPSA id AF271C4338F; Wed, 29 Sep 2021 16:46:32 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 29 Sep 2021 22:16:32 +0530 From: Venkateswara Naralasetty To: Wen Gong Cc: johannes@sipsolutions.net, 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: References: <20210928085211.26186-1-wgong@codeaurora.org> Message-ID: <2afb1bf6f06cb53f43fe0d354afa4e7c@codeaurora.org> X-Sender: vnaralas@codeaurora.org User-Agent: Roundcube Webmail/1.3.9 Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On 2021-09-29 09:07, Wen Gong wrote: > On 2021-09-28 21:12, vnaralas@codeaurora.org wrote: >> On 2021-09-28 14:22, Wen Gong wrote: >>> 6 GHz regulatory domains introduces power spectral density(psd). >>> The power spectral density(psd) of regulatory rule should be take >>> effect to the channels. Save the values to the channel which has >>> psd value and add nl80211 attributes for it. >>> >>> Signed-off-by: Wen Gong >>> --- > ... >>> >>> @@ -2540,6 +2554,9 @@ static void handle_channel_custom(struct wiphy >>> *wiphy, >>> chan->dfs_cac_ms = IEEE80211_DFS_MIN_CAC_TIME_MS; >>> } >>> >>> + if (chan->flags & IEEE80211_CHAN_PSD) >>> + chan->psd = reg_rule->psd; >>> + >>> chan->max_power = chan->max_reg_power; >> >> What about the case AP + STA concurrency? are we going to overwrite >> the PSD power and channel flags? >> > > Hi Venkateswara, > > This patch is not relation with AP + STA concurrency. > For example, it also has other power intersection in > handle_channel_adjacent_rules(). > > chan->max_reg_power = > min_t(int, MBM_TO_DBM(power_rule1->max_eirp), > MBM_TO_DBM(power_rule2->max_eirp)); > > For AP + STA concurrency, it should to maintain 2 group of reg rules, > one is for AP, another is for STA. Can we maintain two power rules in the same channel one for AP and one for STA. In this way, we can update the power rules in the same channel for both AP and STA from the reg rules. Otherwise, we need to maintain multiple channel lists in sband for all supported power mode combinations to apply the respective power rules and build channel flags from the multiple reg rules. right? > This patch is to handle PSD info in the same reg rules. > It is to process only one reg rule in the reg rules. > AP + STA concurrency is a higher level things than this patch. >>> }