public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: Re: Receive OMI support in mac80211?
Date: Fri, 21 Jun 2024 14:37:01 +0200	[thread overview]
Message-ID: <9559970ad396591e628424a50b35c5c3dc7b9f63.camel@sipsolutions.net> (raw)
In-Reply-To: <b7ca414c297df4acb0a8132339293ea7249cfad3.camel@sipsolutions.net>

On Fri, 2024-06-21 at 14:31 +0200, Johannes Berg wrote:
> 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

Hmm. Maybe I sent this too early ;)

Maybe mac80211 shouldn't even do the TX configuration for the STA? It
would have to track this as a separate data point because it's due to
the *local* configuration, so it doesn't actually match the other things
that it's doing today ...

OTOH, if mac80211 does rate control? But maybe we don't really care
about that case? I don't really for iwlwifi ...

And then if we don't care about that part, all we need is to be able to
notify mac80211 about the BW change on that given connection.

johannes

      reply	other threads:[~2024-06-21 12:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21 12:31 Receive OMI support in mac80211? Johannes Berg
2024-06-21 12:37 ` Johannes Berg [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9559970ad396591e628424a50b35c5c3dc7b9f63.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox