From: Johannes Berg <johannes@sipsolutions.net>
To: Wen Gong <quic_wgong@quicinc.com>, linux-wireless@vger.kernel.org
Cc: ath12k@lists.infradead.org, quic_rkaliapp@quicinc.com
Subject: Re: [PATCH 61/76] wifi: nl80211: add EML/MLD capabilities to per-iftype capabilities
Date: Fri, 11 Aug 2023 11:27:37 +0200 [thread overview]
Message-ID: <1ec93eca79a7bc96c1498b771c3b6ea2ebc78d95.camel@sipsolutions.net> (raw)
In-Reply-To: <29ab2b41-0adf-3a04-6eb9-3d5666253eb9@quicinc.com>
On Fri, 2023-08-11 at 17:24 +0800, Wen Gong wrote:
> >
> > And again, what would you do with it? Not advertise EML when you have
> > selected links that are not in the map? And if the links change
> > dynamically in the future? You'd probably need a bunch of validation for
> > that.
> For example, for station, NOT support EML on 2 GHz, support EML on 5
> GHz/6 GHz.
>
> When connect to 2/3 links AP, then EML should NOT add in assoc req while
> connect to AP which is 2 GHz+5 GHz or 2 GHz+6 GHz or 2 GHz+5 GHz+6 GHz.
>
> EML should add in assoc req while connect to AP which is 5 GHz+6 GHz.
OK, at least that answers the question what you'd want to do with it :)
> For dynamic link change, it is another new topic, so I have not good advise
> for that.😁
But everyone's looking at that?
Honestly I'm not even sure - and you might know better - what the EML
capabilities matter for if you never enable EML.
So almost feels like if you never send the EML OMN frame (thanks for the
name!) the AP wouldn't really care, and that's something you could do
very easily without changing it, i.e. you pretend that your 2.4 GHz
actually has EML, you just never enable it in case 2.4 GHz is active?
johannes
--
ath12k mailing list
ath12k@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/ath12k
next prev parent reply other threads:[~2023-08-11 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220713094502.163926-1-johannes@sipsolutions.net>
[not found] ` <20220713114426.4dfc9ebd0461.Ice7b841051cfeb23da17bb2caa0e45191b34c4db@changeid>
2023-08-11 3:51 ` [PATCH 61/76] wifi: nl80211: add EML/MLD capabilities to per-iftype capabilities Wen Gong
2023-08-11 9:03 ` Johannes Berg
2023-08-11 9:05 ` Wen Gong
2023-08-11 9:08 ` Johannes Berg
2023-08-11 9:24 ` Wen Gong
2023-08-11 9:27 ` Johannes Berg [this message]
2023-08-11 9:54 ` Wen Gong
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=1ec93eca79a7bc96c1498b771c3b6ea2ebc78d95.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_rkaliapp@quicinc.com \
--cc=quic_wgong@quicinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox