Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp2614721iob; Mon, 16 May 2022 02:09:56 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwFKw2fwP89osHOj6Mvy/JyYtZiQvbv4uH/p1zOZZ6jYyllpbPw7A6UItF1OT18KE7AUqsm X-Received: by 2002:a05:600c:154d:b0:394:880f:ae3a with SMTP id f13-20020a05600c154d00b00394880fae3amr25960473wmg.13.1652692196580; Mon, 16 May 2022 02:09:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652692196; cv=none; d=google.com; s=arc-20160816; b=FsZ7jzJZPMEdRmnKDEs4l+HcdqrmlgP2Ut0KDO/jkwUJs7m0k03tbTWmtkCKT/5lzj CHuJN8cC5+0NENR5XD4/3oSBZeqHBDSpWcbl+cMI2Dl7b7aUHILnv2Kbv+2JVIury/G8 Seff5rK1PvW2Qj/zl7eqZRFlZitwv8SCV1YIZhA0ZZi3mB0OonSy4akMIa0I1LBZqdTG Maf4nBCR/2imFY/efZSFzogVLGqATgR7LVMGkwjUXaH8GjWqsMx3fdOndfUz3cWwyx97 0HsZXxYMWxoCopmyEgOVRjveEEbutU8z4tJkLXoAY52w5zJRgu5CgKZvay2BqA6r2+vO j7Sg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent :content-transfer-encoding:references:in-reply-to:date:cc:to:from :subject:message-id:dkim-signature; bh=2tDRA8eK4645V9UkT0yXkIBzM/JFLxX0x/OiYBLVdPM=; b=wTeHgzUaoA8qMntoWtu+T4bZg6ocJNGH8CvFzt/mdCp/sJaFQy4rwjI9ZKe3Bf2Da6 AvLrXcspF7DgNALi+NNy7LdxmasOPVrqPG22bgNGbMH9eMKDj+n1UeNLnPtSmQqyR7xf gN8w1OjqvIhm5Nnp9N71TsI5S/iCYtLNSV26YMbRsFV3VZET0GSb1olqUuUJTWT6fD3w wbCVrndAcSD9QVKkbgdIDt3TDzZHnhSXr1g8ywaYvwpqmITEejreB2n6j7s+gmoIKkQ4 SXYgto+V7v7k8uP/JeUNp5Lf6Bjft4gUXzxBg7CDcUsEIxkaum8LSv1PKP6NWX8uG/Ez cfLA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=TTLjHyUw; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id t11-20020a1c770b000000b0038eb8b3ff13si8816046wmi.59.2022.05.16.02.09.38; Mon, 16 May 2022 02:09:56 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=TTLjHyUw; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241432AbiEPIDG (ORCPT + 70 others); Mon, 16 May 2022 04:03:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56138 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241425AbiEPIDB (ORCPT ); Mon, 16 May 2022 04:03:01 -0400 Received: from sipsolutions.net (s3.sipsolutions.net [IPv6:2a01:4f8:191:4433::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AD5FC2D1D9 for ; Mon, 16 May 2022 01:02:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=2tDRA8eK4645V9UkT0yXkIBzM/JFLxX0x/OiYBLVdPM=; t=1652688178; x=1653897778; b=TTLjHyUwZv4sMNp7gP4qA/HaLua4V4ttyDFjsrFj5iUXjyp xa0fD5zVSmIHlkZy28o3cjUp4dD5Yg2EJcpfio6aLfmzw5twi3GGU2MX1TZqY8TCu5140e09k/jUg Ptu8zIxhk9zzoo/vFcKCr2STVSNA6L6guKtTuRc2K3dxj9kjKyldyU67ZYYnYkzLK1hfglnSredqm foHg0otzmIyGtdi2UiO4+4u4Fv+S9doS73MV5Lc5qYNvRuHUqxe0bFOQAjpTgQYT1VrsQT9RpMltd IyGO2bGqeH+F9Er9xFbOjalBz7iNjbESb76Vq1+7DiE0pZ3MPj3Tp9SbGy0xfZ1A==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.95) (envelope-from ) id 1nqVgu-00DHy9-Fa; Mon, 16 May 2022 10:02:56 +0200 Message-ID: Subject: Re: [RFC] mac80211: add support for 6 GHz channels and regulatory From: Johannes Berg To: Aditya Kumar Singh , linux-wireless@vger.kernel.org Cc: Wen Gong Date: Mon, 16 May 2022 10:02:55 +0200 In-Reply-To: <1638775571-24366-1-git-send-email-quic_adisi@quicinc.com> References: <1638775571-24366-1-git-send-email-quic_adisi@quicinc.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.1 (3.44.1-1.fc36) MIME-Version: 1.0 X-malware-bazaar: not-scanned X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Hi, On Mon, 2021-12-06 at 12:56 +0530, Aditya Kumar Singh wrote: > 6 GHz introduces various power modes of operation. Currently, > based on the power mode, channel's psd value as well as > channel disabled flag can change. For single interface, current > implementaion works just fine. But for multi-interfaces, for > example AP-STA concurrency, two different channel needs to be > maintained. This is because, STA power mode also depends on the > AP's power mode it is going to associate with. Hence, psd value > and channel disabled flag might vary. In this case, same channel > can not be used for both AP and STA. So ... you correctly point out that we need to deal with multiple interface scenarios. But we had a previous/ongoing discussion: https://lore.kernel.org/linux-wireless/20210928085211.26186-1-wgong@codeaur= ora.org/ > Hence, this patch adds support to store all possible 6 GHz > channels according to power mode as well as add API > support for getting chan/freq info from the new struct > ieee80211_6ghz_channel. >=20 FWIW, I'm not sure that it's a good idea to have separate channel structs? Wouldn't it make more sense to have each channel store separate relevant information regarding the power? I think you and Wen should go work together and figure out the story as you think it should be - I don't have a lot of opinion on it, and thus I'm not sure it's reasonable to ask me to figure out all the different things. Please work together and come up with a coherent story of how to handle this, hopefully including multi-interface scenarios and maybe regulatory database, internal data structures, etc. johannes