Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp348599ybl; Fri, 30 Aug 2019 00:20:25 -0700 (PDT) X-Google-Smtp-Source: APXvYqz/rIopinvkEir2Pp8HeH6rANqfI1ViuDsR5W+lG/VXqLd1vEXrichcjNtqT2srWaeOHta0 X-Received: by 2002:a65:608e:: with SMTP id t14mr11841051pgu.373.1567149624783; Fri, 30 Aug 2019 00:20:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567149624; cv=none; d=google.com; s=arc-20160816; b=Hpg3EetOoPeVy3i9trffsbuRAStjrC5UC1BOhQLMgMp4LpUt+fEJ4wQ7Ayj9KaeIJk lkarU13/7+JvStGZHhPIOQPywVex4+M8g/4NM7a+hMd65NVyIVcoNV5efwoK5z4T49sp PzebRc/EVgzmEugt50GtGldj+Ya1xuV58mkK5N477Xy0fFB/t1+pF/tVze7e5R6qfKxG 77uzkH5Z756ehpSjlHpMkg4fgGbnKcPPmtAgyTHLqDekXquUbC+ecaijwO3GULN1026d IqPPIZFq1x+CyUqPAlQKdmsoMBwHbBGt3WXmBv8kbZW0jkf6dF7pQjGLm50sJ7ACEIU4 NbCw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=x2NVHP4gZ6g7kJXN1OICSflbEE8BygeY3D3XJoRXHp0=; b=GsgJdNIpcfRmBb88CjG66KBsdcBKJNxeLMOFYyE45sD27035CJhAxq/KEWvqvRGLDd /whqpKN8zIjgJJ0jUDhMAoo+9y/RDvEy6TUc4L4HLQj6KCxqwSsHhQslQ+IMnJ0fiZJC 33W307yqTztOnCh7JHcq1fUMB4+t1LcDvfgcZOjtzzV+T2bWNp2c3UNr8bPdLWu2okZu 4eJaZHQfleOJIiW2ZHLZCSlcfFl0UmigTF4aoW849P8wMhVw+lIABE5JAavCSaAAIkR3 ndSQQ1uKNTZhavzSlUKiYoFt4o9CJVW+eSGl5KiRTcxUgRF8LKXSR7N6t1ci5NDKOgHM uiQA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id cd11si4220661plb.136.2019.08.30.00.20.10; Fri, 30 Aug 2019 00:20:24 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728548AbfH3HTT (ORCPT + 99 others); Fri, 30 Aug 2019 03:19:19 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:59630 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728538AbfH3HTT (ORCPT ); Fri, 30 Aug 2019 03:19:19 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.92.1) (envelope-from ) id 1i3bBl-0008KG-Kb; Fri, 30 Aug 2019 09:19:17 +0200 Message-ID: Subject: Re: [PATCH] cfg80211: Add new fields to wiphy structure From: Johannes Berg To: Amar Singhal , jouni@codeaurora.org Cc: linux-wireless@vger.kernel.org, jjohnson@codeaurora.org, rmanohar@codeaurora.org Date: Fri, 30 Aug 2019 09:19:16 +0200 In-Reply-To: <1567116559-17419-1-git-send-email-asinghal@codeaurora.org> References: <1567116559-17419-1-git-send-email-asinghal@codeaurora.org> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5 (3.30.5-1.fc29) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Thu, 2019-08-29 at 15:09 -0700, Amar Singhal wrote: > A channel is completely defined by (oper_class, channel number) tuple, > and not just by center frequency. Operating class also tells about the > bandwidth supported by the channel. Therefore add the operating class and > channel number to the wiphy structure. We don't split out the channels that way, so this doesn't seem like the right approach. Instead, we list the *frequencies*, and then have flags for the permitted bandwidths. We already support things like "no-HT40+" and could possibly extend that to others, if it were _really_ possible, though in practice those limitations are usually not present in devices, just in the spec, and we can rely on hostapd/wpa_s to take care of them. Even if you do have those limitations, this isn't the right way to go about it, because it'll be very confusing to userspace to see the same frequency multiple times. It'd also cause a bunch of problems with scanning (listing the same channel twice) etc. Since you haven't explained why you want to do this I cannot offer any further guidance, but this cannot be the right approach. johannes