On 1/18/2023 9:12 PM, Johannes Berg wrote:
On Tue, 2022-12-06 at 13:32 +0530, Veerendranath Jakkam wrote:
+ * @assoc_link_id: Indicates link ID of the AP MLD link on which (re)association
+ * requested by peer. In non-MLD AP mode, it will be -1. Used only with OWE
+ * update event (driver to user space).
+ * @peer_mld_addr: MLD address of the peer. For non-MLD peer, it will be all
+ * zeros. Used only with OWE update event (driver to user space).
Similar here - why require setting assoc_link_id == -1 if
peer_mld_address can be left zeroes to indicate non-MLO connection?
"assoc_link_id" will be set to -1 when the AP operating in non-MLD mode,
in that case peer_mld_addr can always be ignored since STAs always
connects in non-MLO mode only.
When the AP operating in MLD mode, "assoc_link_id" should always be
filled irrespective of the STA is MLD or not. This is needed to indicate
user space about the event belong which affiliated AP of the AP MLD.
"peer_mld_addr" filled to indicate whether the peer is MLD or not.
Ex: if the AP operating in MLD mode and connected STA is non-MLD then
"peer_mld_addr" will be all zeros but still "assoc_link_id" will set
link ID of the corresponding AP under the AP MLD.
---
veeru
