Hey all,
We're contemplating adding some support for using (sending) OMI to save
power or perhaps other reasons.
The implementation logic would seem to end up being somewhat similar to
some other cases of changing parameters (CSA or simply AP doing
HT/VHT/HE/EHT operation changes, VHT operating mode notification action
frame), but
- for widening bandwidth/increasing NSS:
- update chanctx
- send OMI / wait / response
- update TX configuration for the STA it was sent to
- for reducing bandwidth/NSS:
- update TX configuration for the STA it was sent to
- send OMI / wait / response
- update chanctx
FWIW, one thing I'm still unsure about is how OMI interacts with VHT
operating mode notification, but we don't transmit the latter right now.
Initially I thought it might be best to have some kind of request_omi()
function the driver can call, but since sending the OM field is done
with any data frame, I'm not sure how to really get that done - a new
driver op seems a bit overkill?
So perhaps it'd be better to have at least two new functions that always
have to be called in pairs, like prepare_omi() and finalize_omi() and
it'd be up to the driver to make sure the field was sent inbetween?
I'm tending towards the latter, any thoughts?
johannes
