linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Adding CMD_SET_CHANNEL for station iftypes
Date: Thu, 18 Nov 2021 16:11:40 -0800	[thread overview]
Message-ID: <2b18f86924c3d64437aa139f6401ee2e7705eeb0.camel@gmail.com> (raw)

Hi,

I see CMD_SET_CHANNEL is only supported for AP-type iftypes (AP,
P2P_GO, etc). While this definitely makes sense in most cases,
protocols like p2p/dpp require going off channel for an undetermined
amount of time.

I could go into the exact scenarios but in short your REMAIN_ON_CHANNEL
could end at very inconvenient times.

Specifically when a station is not associated to any AP is there any
harm in allowing CMD_SET_CHANNEL? Is this purely a software limitation
or do drivers not allow this?

If this sounds reasonable (and possible) I would propose adding the
station iftype to CMD_SET_CHANNEL in addition to an extended feature
e.g. NL80211_EXT_FEATURE_STA_SET_CHANNEL so supplicants can detect
support or fall back to using REMAIN_ON_CHANNEL for these specific use
cases.

Thanks,
James


             reply	other threads:[~2021-11-19  0:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-19  0:11 James Prestwood [this message]
2021-11-19  8:31 ` Adding CMD_SET_CHANNEL for station iftypes Johannes Berg
2021-11-19 17:43   ` James Prestwood
2022-01-06 22:01     ` Johannes Berg
2022-01-07 19:35       ` James Prestwood
2022-01-09 12:00         ` Arend van Spriel
2022-01-10 17:13           ` James Prestwood
2022-02-03 22:06             ` Johannes Berg

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=2b18f86924c3d64437aa139f6401ee2e7705eeb0.camel@gmail.com \
    --to=prestwoj@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).