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;
Message-ID: <e2faf5ac-ee71-3ed4-7598-70f083a5996c@quicinc.com>
Date:   Wed, 23 Mar 2022 13:45:02 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.6.0
Subject: Re: [PATCH v2 1/4] nl80211: advertise RU puncturing support to
 userspace
Content-Language: en-US
To:     <johannes@sipsolutions.net>, <linux-wireless@vger.kernel.org>
References: <20220323191640.31230-1-quic_alokad@quicinc.com>
From:   Aloka Dixit <quic_alokad@quicinc.com>
In-Reply-To: <20220323191640.31230-1-quic_alokad@quicinc.com>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 3/23/2022 12:16 PM, Aloka Dixit wrote:
> RU preamble puncturing is allowed for bandwidths more that 80 MHz
> except 80+80. Drivers may not support puncturing at all or have
> restrictions for a minimum bandwidth.
> Add new attribute NL80211_ATTR_RU_PUNCT_SUPP_BW to advertise the
> driver support to the userspace. Default value (0) will indicate that
> RU puncturing is not supported.
> 
> Signed-off-by: Aloka Dixit <quic_alokad@quicinc.com>
> ---
> v2: Moved boundary check for ru_punct_supp_bw to wiphy_register().
> 

These patches depend on EHT support from
https://patchwork.kernel.org/project/linux-wireless/list/?series=614176&state=%2A&archive=both 
which are not yet present in mac80211-next tree.
But found those in wireless-next tree hence I used the same repository.