Received: by 2002:a05:7412:37c9:b0:e2:908c:2ebd with SMTP id jz9csp2781811rdb; Fri, 22 Sep 2023 08:14:35 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFZrkDX5SjXpMChj4tUib8xYxhTnM4du14sKU9DU4nIZX5FY4j+via3fnBmBIWpNULiyshq X-Received: by 2002:a05:6358:9924:b0:134:e3d2:1e50 with SMTP id w36-20020a056358992400b00134e3d21e50mr11766037rwa.18.1695395675547; Fri, 22 Sep 2023 08:14:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1695395675; cv=none; d=google.com; s=arc-20160816; b=IGQ0mHCrVKsnaXp+/pBDY9hIvdlwlARgdZrbRa2j+kOOnCbb0kFSuf9V7KLN3iVLxS KrZtTP8Ob9IfhzZhaR/iNXBDjBcFjJ9BXsqxlc7fX1lkUsPzvXCZ2u0LYyynhP+9YTHG ToUj2Rg/hv5Uei4bfOH5Pe5FH+prLDQgV+mnxgWqjeweuPgrZwxWlzW9Ghx6foAYzG2Y VpijBkOSNCNAn2cf3eRW2qH2w6dJCFLYXntA7HVTJtza4kYRVpM4bgvfvJiOt5Q5GAzR LQ6VK82ZU83FLrw8vKSINDCqJKdBgEeJpYHXpgQa03hWryqzdiXQ2Oe8qd/SM7XiDRCo d4oQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=B+/ACta5Uv0EYpox8tHiK6YZhFkMUmjy5h4LeKkghVM=; fh=75CDHJDuowxspHrWYGyFkxqtTsCAv36FxKet5aSzFkk=; b=AYN4/3zZ/1VNkaPdwxm40CfI2O79FoT8FkR9Wuvp30EGwJlX5rdwjc9tU4zB9moukm WvJ9bPW9FdzLQ1H1jCcVfFoq9xlZnIvlSj4/wJeMlGdxmuryz3RHqLGqXMs/MEhM9fc4 5xkZ2J5ERR7n1yI/3Iu1HmPpF2goX5EXvY8GFla4egzTIHj3DrMOkwtriCSo0K7qE1LU y0MjelZY04mNgY8PzduWiMyALzIsHAWUV6IyhaAayFYUVX/IyMdlwia1iaPbQgtsHPbU OWFA+nysQm0sHDEaHfJRJzQI7gyAIw+4NIQy4++mroVkhsNMenI1gGGqHSKRuUoHTIhu Rf+g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@quicinc.com header.s=qcppdkim1 header.b=A70V3NOg; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=quicinc.com Return-Path: Received: from fry.vger.email (fry.vger.email. [23.128.96.38]) by mx.google.com with ESMTPS id r9-20020a632b09000000b00573f837821fsi3799638pgr.689.2023.09.22.08.14.35 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Sep 2023 08:14:35 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) client-ip=23.128.96.38; Authentication-Results: mx.google.com; dkim=pass header.i=@quicinc.com header.s=qcppdkim1 header.b=A70V3NOg; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=quicinc.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by fry.vger.email (Postfix) with ESMTP id 01ACE80D9B1A; Fri, 22 Sep 2023 06:19:26 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at fry.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231310AbjIVNSr (ORCPT + 56 others); Fri, 22 Sep 2023 09:18:47 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58146 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229634AbjIVNSq (ORCPT ); Fri, 22 Sep 2023 09:18:46 -0400 Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.131]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 36608CE for ; Fri, 22 Sep 2023 06:18:40 -0700 (PDT) Received: from pps.filterd (m0279866.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 38MBV4jP023156; Fri, 22 Sep 2023 13:18:33 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; h=message-id : date : mime-version : subject : to : cc : references : from : in-reply-to : content-type : content-transfer-encoding; s=qcppdkim1; bh=B+/ACta5Uv0EYpox8tHiK6YZhFkMUmjy5h4LeKkghVM=; b=A70V3NOgNEXH+OXBFPeb02l/7cSlQg9SbxBYAgtdcJYNfhllFDmqZ+OE8GocF8e3XnsH U9m99pA8tmyOampxmxbD0VdWtrfg8QkreC+MwUVOOpPN0kAtFCzDwNgCtBQTA4ASmRs4 RFLF0ZquX6pwMxrJEAkSZL0HTxRk3YNyCNBaOT4vrZhMLGBJCICy2N/9XnZFIzH/liSW 3qWtyyVfUHiYDX4LKdkRUcrnTN1zdd0umAkFRFKxUZC3wdcUupOvSx3N8vcGF8wSNKNH EBOQvmOGmQmHNl173IaaJ6fg1jbmL4LiCptKk9IVMbCUzB/bXgtCECpaxax5OjRUERHz Nw== Received: from nalasppmta05.qualcomm.com (Global_NAT1.qualcomm.com [129.46.96.20]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 3t9a3e87ry-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 22 Sep 2023 13:18:33 +0000 Received: from nalasex01a.na.qualcomm.com (nalasex01a.na.qualcomm.com [10.47.209.196]) by NALASPPMTA05.qualcomm.com (8.17.1.5/8.17.1.5) with ESMTPS id 38MDIWdg031776 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 22 Sep 2023 13:18:32 GMT Received: from [10.216.13.153] (10.80.80.8) by nalasex01a.na.qualcomm.com (10.47.209.196) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.36; Fri, 22 Sep 2023 06:18:30 -0700 Message-ID: <47e2ce79-2885-489c-b567-fdbcb120d056@quicinc.com> Date: Fri, 22 Sep 2023 18:48:26 +0530 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v6 05/13] wifi: ath11k: update regulatory rules when connect to AP on 6 GHz band for station Content-Language: en-US To: Wen Gong , CC: , , References: <20230920082349.29111-1-quic_wgong@quicinc.com> <20230920082349.29111-6-quic_wgong@quicinc.com> <5e9439c5-fc02-4a18-8cc8-c76998bfcbc6@quicinc.com> <1f739d62-d5c0-a64b-ef9b-d5fd7b79755e@quicinc.com> From: Aditya Kumar Singh In-Reply-To: <1f739d62-d5c0-a64b-ef9b-d5fd7b79755e@quicinc.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01b.na.qualcomm.com (10.46.141.250) To nalasex01a.na.qualcomm.com (10.47.209.196) X-QCInternal: smtphost X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-ORIG-GUID: -L4IplQhQ2bqOvIb-UxjlkrqrnP-qVWl X-Proofpoint-GUID: -L4IplQhQ2bqOvIb-UxjlkrqrnP-qVWl X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.267,Aquarius:18.0.980,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2023-09-22_11,2023-09-21_01,2023-05-22_02 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 adultscore=0 clxscore=1015 priorityscore=1501 phishscore=0 malwarescore=0 lowpriorityscore=0 mlxlogscore=999 mlxscore=0 suspectscore=0 bulkscore=0 spamscore=0 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2309180000 definitions=main-2309220113 X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on fry.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (fry.vger.email [0.0.0.0]); Fri, 22 Sep 2023 06:19:26 -0700 (PDT) On 9/22/23 15:32, Wen Gong wrote: > On 9/22/2023 5:39 PM, Aditya Kumar Singh wrote: >> On 9/20/23 13:53, Wen Gong wrote: >> >>> +    if (ath11k_mac_supports_6ghz_cc_ext(ar) && >>> +        ctx->def.chan->band == NL80211_BAND_6GHZ && >>> +        arvif->vdev_type == WMI_VDEV_TYPE_STA) { >>> +        reg_info = &ab->reg_info_store[ar->pdev_idx]; >>> +        power_type = vif->bss_conf.power_type; >>> +        ath11k_dbg(ab, ATH11K_DBG_MAC, "mac chanctx power type %d\n", >>> +               power_type); >>> +        if (power_type == IEEE80211_REG_UNSET_AP) >>> +            power_type = IEEE80211_REG_LPI_AP; >> Why having _UNSET_ power type in vif->bss_conf.power_type is fine? >> Typically, during association, we would be setting this from the >> beacon/association response frame's HE 6 GHz Operation Info Field. So >> is it fine if the field is carrying some info which we don't know (or >> may be don't support it yet)? Why are we masking it with _LPI_ mode? >> >> Also, I see that currently mac80211 only sets LPI or SP. So let's say >> STA is trying to connect to VLP AP, mac80211 will set it as _UNSET_. >> And then here, we will be treating it as LPI AP. Is that fine? > > Currently only SP/LPI are defined in "Table E-12—Regulatory Info > subfield encoding in the United States" of IEEE Std 802.11ax™‐2021. > > So maybe I need to set power_type to VLP when it is UNSET here. Yeah, or may be deny association if we don't support that mode? I would let others comment on this.