From: Johannes Berg <johannes@sipsolutions.net>
To: Aditya Kumar Singh <aditya.kumar.singh@oss.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH wireless-next] wifi: mac80211_hwsim: advertise puncturing feature support
Date: Mon, 20 Oct 2025 16:25:09 +0200 [thread overview]
Message-ID: <e0ce9b89f0e0a6379070e9e135c53722a2d0a19f.camel@sipsolutions.net> (raw)
In-Reply-To: <20251017-hwsim_set_punct_feature_bit-v1-1-3be1bb3450c0@oss.qualcomm.com>
On Fri, 2025-10-17 at 09:32 +0530, Aditya Kumar Singh wrote:
> If userspace provides a puncturing bitmap via the NL80211_ATTR_PUNCT_BITMAP
> attribute, the kernel with mac80211_hwsim driver currently rejects the
> command with the error: "driver doesn't support puncturing", because the
> driver does not advertise support for this feature.
>
> At present, the following hwsim test cases utilize puncturing, but the
> bitmap is not sent to the kernel. Instead, the puncturing information is
> conveyed only through the beacon data:
> * eht_5ghz_80mhz_puncturing_override_1
> * eht_5ghz_80mhz_puncturing_override_2
> * eht_5ghz_80mhz_puncturing_override_3
>
> A future change in hostapd will begin configuring the puncturing bitmap
> explicitly, which will cause these test cases to fail unless the driver
> advertises support.
>
> To address this, update mac80211_hwsim driver to advertise puncturing
> feature support.
This might be a good time to introduce better checks vs. what we have
now in hwsim_chans_compat(), which just uses the control channel rather
than any actual bandwidth/puncturing/etc.
It'd also make the tests actually test more. What do you think?
johannes
next prev parent reply other threads:[~2025-10-20 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 4:02 Aditya Kumar Singh
2025-10-20 14:25 ` Johannes Berg [this message]
2025-10-21 5:56 ` Aditya Kumar Singh
2025-10-21 14:27 ` 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=e0ce9b89f0e0a6379070e9e135c53722a2d0a19f.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=aditya.kumar.singh@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®