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;
Subject: Re: [RFC 3/7] mac80211: handle channel frequency offset
To:     Johannes Berg <johannes@sipsolutions.net>
Cc:     linux-wireless <linux-wireless@vger.kernel.org>
References: <20200401062150.3324-1-thomas@adapt-ip.com>
 <20200401062150.3324-4-thomas@adapt-ip.com>
 <7fc6331597f53f5d100f3aa7e29434c20cf6fe90.camel@sipsolutions.net>
From:   Thomas Pedersen <thomas@adapt-ip.com>
Message-ID: <7b3b34dd-882a-73e7-f857-8e581c3f7bc0@adapt-ip.com>
Date:   Wed, 1 Apr 2020 10:39:16 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <7fc6331597f53f5d100f3aa7e29434c20cf6fe90.camel@sipsolutions.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

On 3/31/20 11:59 PM, Johannes Berg wrote:
> On Tue, 2020-03-31 at 23:21 -0700, Thomas Pedersen wrote:
>> ie. ignore
>> for mesh, ibss, HT/VHT specific stuff, TDLS, etc.
> 
> This makes sense, but I don't see that you prevent using mesh, ibss and
> perhaps TDLS on s1g channels?
> 
> Or do we not expect drivers/devices that support this, as well as S1G
> channels?

Well it's really orthogonal to S1G (maybe a new 2412.5Mhz channel opens
up :)). We should probably return an error 'if (chan->freq_offset)' or
so for features which have not yet been tested / implemented for
frequency offset.

-- 
thomas