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;
Message-ID: <5c39eaec897af4d7b1005d1f7cb80552c3404e54.camel@sipsolutions.net>
Subject: Re: [PATCH] iw: add optional argument to parse 6G band channel
From:   Johannes Berg <johannes@sipsolutions.net>
To:     Pradeep Kumar Chitrapu <pradeepc@codeaurora.org>
Cc:     linux-wireless@vger.kernel.org
Date:   Fri, 06 Nov 2020 09:55:30 +0100
In-Reply-To: <1602283770-8026-1-git-send-email-pradeepc@codeaurora.org>
References: <1602283770-8026-1-git-send-email-pradeepc@codeaurora.org>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 (3.36.5-1.fc32) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Fri, 2020-10-09 at 15:49 -0700, Pradeep Kumar Chitrapu wrote:
> Channel numbers of 6G band overlaps with those of 2G or 5G bands.
> Therefore, an optional argument "6G" is added and expected next
> to channel number to map it to correct 6GHz frequency. If not
> specified, defaults to matching 2G or 5G frequency.
> 
> example:
> iw wlanX set channel 149 6G 80MHz  --> maps to 6695 MHz
> iw wlanX set channel 149 80MHz     --> maps to 5745 MHz

Hm. I can't really say I like this much.

Is it _really_ needed? I mean, we mostly specify the frequency today, so
... why not just always do that for 6 GHz?

johannes