From: Johannes Berg <johannes@sipsolutions.net>
To: Ria Thomas <ria.thomas@morsemicro.com>
Cc: linux-wireless@vger.kernel.org, lachlan.hodges@morsemicro.com,
arien.judge@morsemicro.com, pradeep.reddy@morsemicro.com,
simon@morsemicro.com
Subject: Re: [PATCH wireless-next v2 1/3] wifi: cfg80211: Add support for S1G Response Indication Configuration
Date: Tue, 13 Jan 2026 09:50:44 +0100 [thread overview]
Message-ID: <048c2715d08822d7f79b082cbe332f982d8ced61.camel@sipsolutions.net> (raw)
In-Reply-To: <20260109040041.tnk7e6uewo24u3tr@1207> (sfid-20260109_050048_012596_BDA1E561)
On Fri, 2026-01-09 at 09:30 +0530, Ria Thomas wrote:
> The WFA HaLow test plan includes explicit test cases that require
> configuring the Response Indication on both the AP and the STA.
> In these scenarios, the Response Indication is not negotiated as
> part of association, but is instead set dynamically after the
> association has been established.
Fair.
> As a result, the Response Indication needs to be configurable at
> runtime from userspace and applied to the driver/firmware
> independently of association or AP setup. This requirement
> motivated the introduction of a userspace‑configurable selector
> that updates the Response Indication state on an already active
> interface.
Actually, reading the spec, are you sure it's even on an *interface*
scope? A lot of this seems to me like it should be per intended
receiver, and you need to know its capabilities for generating the
intended response?
If it were per-STA then I think that'd have a much more natural lifetime
(since it cannot exceed that of the STA) which seems far better to me.
But you're going to have to help me understand it :)
johannes
next prev parent reply other threads:[~2026-01-13 8:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 6:24 [PATCH wireless-next v2 0/3] wifi: add S1G response indication configuration with NDP BA support Ria Thomas
2025-12-09 6:24 ` [PATCH wireless-next v2 1/3] wifi: cfg80211: Add support for S1G Response Indication Configuration Ria Thomas
2026-01-08 12:27 ` Johannes Berg
2026-01-09 4:00 ` Ria Thomas
2026-01-13 8:50 ` Johannes Berg [this message]
2026-01-16 5:31 ` Ria Thomas
2026-02-06 6:11 ` Ria Thomas
2026-02-06 7:57 ` Johannes Berg
2026-02-12 8:43 ` Ria Thomas
2026-02-17 11:41 ` Johannes Berg
2025-12-09 6:24 ` [PATCH wireless-next v2 2/3] wifi: mac80211: track S1G Response Indication (RI) and notify drivers Ria Thomas
2025-12-09 6:24 ` [PATCH wireless-next v2 3/3] wifi: mac80211: add support for NDP ADDBA/DELBA for S1G Ria Thomas
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=048c2715d08822d7f79b082cbe332f982d8ced61.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arien.judge@morsemicro.com \
--cc=lachlan.hodges@morsemicro.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pradeep.reddy@morsemicro.com \
--cc=ria.thomas@morsemicro.com \
--cc=simon@morsemicro.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