All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Cc: johannes@sipsolutions.net,  linux-wireless@vger.kernel.org,
	 Ilan Peer <ilan.peer@intel.com>,
	 Johannes Berg <johannes.berg@intel.com>,
	iil_jenkins iil_jenkins <EC.GER.UNIX.IIL.JENKINS@INTEL.COM>
Subject: Re: [PATCH 6/7] wifi: cfg80211: Add support for interface usage notification
Date: Thu, 06 Jun 2024 12:27:54 +0300	[thread overview]
Message-ID: <875xummndx.fsf@kernel.org> (raw)
In-Reply-To: <20240605135233.23d15e758640.I7a62740a6868416acaed01e41157b3c0a7a41b4d@changeid> (Miri Korenblit's message of "Wed, 5 Jun 2024 13:57:21 +0300")

Miri Korenblit <miriam.rachel.korenblit@intel.com> writes:

> From: Ilan Peer <ilan.peer@intel.com>
>
> In some cases, when an interface is added by user space, user space
> might not know yet what is the intended type of the interface, e.g.,
> before a P2P Group Ownership Negotiation (GON) an interface is added
> but only at the end of the GON flow the final interface type is
> determined. This doesn't allow the kernel drivers to prepare for the
> actual interface type, e.g., make resources available for the
> interface type etc.
>
> Generally, adding an interface doesn't necessarily imply that it will
> actually be used soon, and as described the interface might not be used
> with the type it's added as.
>
> This new API allows user space to indicate that it does indeed intend to
> use the interface soon, along with the types (of which the interface
> must be one) that may be selected for that usage. This will allow the
> underlying driver to adjust resources accordingly.
>
> Signed-off-by: Ilan Peer <ilan.peer@intel.com>
> Reviewed-by: Johannes Berg <johannes.berg@intel.com>
> Tested-by: iil_jenkins iil_jenkins <EC.GER.UNIX.IIL.JENKINS@INTEL.COM>

This new command just looks weird to me, do we really need it? I would
expect to see a workaround like this in out-of-tree drivers but not in
upstream.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2024-06-06  9:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 10:57 [PATCH 0/7] cfg80211/mac80211 patches from our internal tree 2024-06-05 Miri Korenblit
2024-06-05 10:57 ` [PATCH 1/7] wifi: nl80211: remove the FTMs per burst limit for NDP ranging Miri Korenblit
2024-06-05 10:57 ` [PATCH 2/7] wifi: mac80211_hwsim: add 320 MHz to hwsim channel widths Miri Korenblit
2024-06-05 10:57 ` [PATCH 3/7] wifi: mac80211: fix erroneous errors for STA changes Miri Korenblit
2024-06-05 10:57 ` [PATCH 4/7] wifi: mac80211: clean up 'ret' in sta_link_apply_parameters() Miri Korenblit
2024-06-05 10:57 ` [PATCH 5/7] wifi: cfg80211: honor WIPHY_FLAG_SPLIT_SCAN_6GHZ in cfg80211_conn_scan Miri Korenblit
2024-06-05 10:57 ` [PATCH 6/7] wifi: cfg80211: Add support for interface usage notification Miri Korenblit
2024-06-06  9:27   ` Kalle Valo [this message]
2024-06-09  7:35     ` Peer, Ilan
2024-06-12 16:19       ` Kalle Valo
2024-06-16 14:58         ` Peer, Ilan
2024-06-24 12:49           ` Kalle Valo
2024-07-01  9:40             ` Peer, Ilan
2024-06-05 10:57 ` [PATCH 7/7] wifi: mac80211: " Miri Korenblit

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=875xummndx.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=EC.GER.UNIX.IIL.JENKINS@INTEL.COM \
    --cc=ilan.peer@intel.com \
    --cc=johannes.berg@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=miriam.rachel.korenblit@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.