From: Kalle Valo <kvalo@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH 2/5] wifi: ieee80211/ath11k: remove IEEE80211_MAX_NUM_PWR_LEVEL
Date: Wed, 15 May 2024 16:11:26 +0300 [thread overview]
Message-ID: <87r0e3cj9d.fsf@kernel.org> (raw)
In-Reply-To: <20240506214536.9818e5471055.Icece7e47e963d6b68e0d97ba13c102b37fbaa689@changeid> (Johannes Berg's message of "Mon, 6 May 2024 21:37:54 +0200")
Johannes Berg <johannes@sipsolutions.net> writes:
> From: Johannes Berg <johannes.berg@intel.com>
>
> The define IEEE80211_MAX_NUM_PWR_LEVEL doesn't make much
> sense. Yes, that table has a maximum value of 8, and the
> table will actually remain that way, but EHT introduced
> a way to encode more levels for 320 MHz channels.
>
> Remove IEEE80211_MAX_NUM_PWR_LEVEL and, for ath11k being
> the only user, add ATH11K_NUM_PWR_LEVELS, where it makes
> sense since it cannot support 320 MHz channels.
>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Acked-by: Kalle Valo <kvalo@kernel.org>
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-05-15 13:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 19:37 [PATCH 0/5] wifi: mac80211: build TPE handling Johannes Berg
2024-05-06 19:37 ` [PATCH 1/5] wifi: mac80211: update 6 GHz AP power type before association Johannes Berg
2024-05-06 19:37 ` [PATCH 2/5] wifi: ieee80211/ath11k: remove IEEE80211_MAX_NUM_PWR_LEVEL Johannes Berg
2024-05-15 13:11 ` Kalle Valo [this message]
2024-05-06 19:37 ` [PATCH 3/5] wifi: ath11k: fix TPE power levels Johannes Berg
2024-05-15 13:12 ` Kalle Valo
2024-05-06 19:37 ` [PATCH 4/5] wifi: mac80211: pass parsed TPE data to drivers Johannes Berg
2024-05-15 13:16 ` Kalle Valo
2024-05-06 19:37 ` [PATCH 5/5] wifi: mac80211: track changes in AP's TPE 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=87r0e3cj9d.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).