Hi, > The old flow also converted the Element to operation elements first, > then it used ieee80211_chandef_vht_oper() to build the new chandef from > operation elements. > > We think it's necessary for the case that AP is trying to switch to a > 160 MHz bandwidth, while the STA doesn't support the 160 MHz bandwidth. Yeah, you're right, it did before and I suppose it's still easier than managing two conversions, since some formats are the same. > Just like what had been done during the association, > ieee80211_chandef_vht_oper() checks the STA's capabilities and builds a > valid chandef for the STA. However, even if the STA doesn't support the > 160 MHz bandwidth, ieee80211_chandef_vht_oper() doesn't mark the > conn_flags as IEEE80211_CONN_DISABLE_160MHZ, so the same check is > necessary when handling CSA. Right. > Like we had discussed in previous mail, we expected the patch will be > simplified. Yeah I just circled back to it for stupid reasons (I guess mostly forgot to mark in patchwork that you were going to make changes) and looked again after having looked at all the other code in the series I posted late last week. > In summary, the steps for STA to handling CSA are, > 1. parse the new channel information from either operating class or > WBCS Element. > 2. convert the channel information into corresponding operation Element > (HT/VHT in 5 GHz band and HE/EHT in 6 GHz band) > 3. Build a valid chandef from the operation Element. > Sounds good. johannes
