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;
To:     Johannes Berg <johannes@sipsolutions.net>,
        Maharaja Kennadyrajan <mkenna@codeaurora.org>,
        ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
References: <1623164855-15910-1-git-send-email-mkenna@codeaurora.org>
 <1623164855-15910-2-git-send-email-mkenna@codeaurora.org>
 <f14e6e6b81978ace4580774981a7e032b4001182.camel@sipsolutions.net>
From:   Felix Fietkau <nbd@nbd.name>
Subject: Re: [PATCH v4 1/3] nl80211: Add support for beacon tx mode
Message-ID: <0e3d0abd-a895-77d8-d3a6-ef6d2616b7db@nbd.name>
Date:   Tue, 29 Jun 2021 19:44:53 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
 Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <f14e6e6b81978ace4580774981a7e032b4001182.camel@sipsolutions.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Precedence: bulk


On 2021-06-23 13:16, Johannes Berg wrote:
> First, I'd like to see some input from other vendors - is this useful?
> 
> I have no objections to it and it comes with an in-kernel driver, so I'm
> inclined to accept it, but maybe we should have other modes, etc.?
I haven't seen any config option like this outside of QCA stuff.
It seems to me that before getting merged, the documentation should at
least cover when and why the *user* would configure this implementation
detail, instead of having the driver/fw make a reasonable decision on
its own.

- Felix