Hi, On Mon, 2021-12-06 at 12:56 +0530, Aditya Kumar Singh wrote: > 6 GHz introduces various power modes of operation. Currently, > based on the power mode, channel's psd value as well as > channel disabled flag can change. For single interface, current > implementaion works just fine. But for multi-interfaces, for > example AP-STA concurrency, two different channel needs to be > maintained. This is because, STA power mode also depends on the > AP's power mode it is going to associate with. Hence, psd value > and channel disabled flag might vary. In this case, same channel > can not be used for both AP and STA. So ... you correctly point out that we need to deal with multiple interface scenarios. But we had a previous/ongoing discussion: https://lore.kernel.org/linux-wireless/20210928085211.26186-1-wgong@xxxxxxxxxxxxxx/ > Hence, this patch adds support to store all possible 6 GHz > channels according to power mode as well as add API > support for getting chan/freq info from the new struct > ieee80211_6ghz_channel. > FWIW, I'm not sure that it's a good idea to have separate channel structs? Wouldn't it make more sense to have each channel store separate relevant information regarding the power? I think you and Wen should go work together and figure out the story as you think it should be - I don't have a lot of opinion on it, and thus I'm not sure it's reasonable to ask me to figure out all the different things. Please work together and come up with a coherent story of how to handle this, hopefully including multi-interface scenarios and maybe regulatory database, internal data structures, etc. johannes
