mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rameshkumar Sundaram <rameshkumar.sundaram@oss.qualcomm.com>
To: christophergriffin05@gmail.com, Jeff Johnson <jjohnson@kernel.org>
Cc: Baochen Qiang <baochen.qiang@oss.qualcomm.com>,
	linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
	ath12k@lists.infradead.org, linux-kernel@vger.kernel.org,
	Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Subject: Re: [PATCH 1/2] wifi: ath11k: simplify copying a peer's PPE thresholds
Date: Tue, 10 Nov 2026 12:23:59 +0530	[thread overview]
Message-ID: <e269da8d-f3dd-461b-93c5-ff4c81843918@oss.qualcomm.com> (raw)
In-Reply-To: <20261106-ath-peer-ppe-thres-loop-v1-1-f6bb5fe9ffb3@gmail.com>

On 11/7/2026 12:18 AM, Christopher Griffin via B4 Relay wrote:
> From: Christopher Griffin <christophergriffin05@gmail.com>
> 
> ath11k_peer_assoc_h_he() copies each 6-bit PPE threshold of a peer's HE
> capabilities into the WMI layout one bit at a time, shifting it in from
> the top: val >>= 1, then the new bit at bit 5, six times over. After the
> sixth bit, bit i of the field sits at bit i of val, so put it there
> directly.
> 
> No functional change: a userspace copy of both loops gives the same
> ppet16_ppet8_ru3_ru0 for every 6-bit value in every RU slot and for 2.5
> million random threshold fields. Compile-tested with W=1.
> 

this information seems to be unnecessary as its obvious from code.

> The change, this message and the test were written with Claude, an AI
> coding assistant.
> 

This might also be not needed as per latest guidelines.


> Suggested-by: Rameshkumar Sundaram <rameshkumar.sundaram@oss.qualcomm.com>
> Link: https://lore.kernel.org/all/b60c4c56-483b-406e-92ab-643b0fdf2dc8@oss.qualcomm.com/
> Signed-off-by: Christopher Griffin <christophergriffin05@gmail.com>
> ---
>   drivers/net/wireless/ath/ath11k/mac.c | 3 +--
>   1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/net/wireless/ath/ath11k/mac.c b/drivers/net/wireless/ath/ath11k/mac.c
> index 1a237adaa37d1..d7ae9e8747233 100644
> --- a/drivers/net/wireless/ath/ath11k/mac.c
> +++ b/drivers/net/wireless/ath/ath11k/mac.c
> @@ -2496,9 +2496,8 @@ static void ath11k_peer_assoc_h_he(struct ath11k *ar,
>   				if ((arg->peer_ppet.ru_bit_mask & BIT(ru)) == 0)
>   					continue;
>   				for (i = 0; i < 6; i++) {
> -					val >>= 1;
>   					val |= ((he_cap->ppe_thres[bit / 8] >>
> -						 (bit % 8)) & 0x1) << 5;
> +						 (bit % 8)) & 0x1) << i;
>   					bit++;
>   				}
>   				arg->peer_ppet.ppet16_ppet8_ru3_ru0[nss] |=
> 

both comments apply to ath12k patch as well

-- 
Ramesh

  reply	other threads:[~2026-11-10  6:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 18:48 [PATCH 0/2] wifi: ath: " Christopher Griffin via B4 Relay
2026-11-06 18:48 ` [PATCH 1/2] wifi: ath11k: " Christopher Griffin via B4 Relay
2026-11-10  6:53   ` Rameshkumar Sundaram [this message]
2026-11-06 18:48 ` [PATCH 2/2] wifi: ath12k: " Christopher Griffin via B4 Relay

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=e269da8d-f3dd-461b-93c5-ff4c81843918@oss.qualcomm.com \
    --to=rameshkumar.sundaram@oss.qualcomm.com \
    --cc=ath11k@lists.infradead.org \
    --cc=ath12k@lists.infradead.org \
    --cc=baochen.qiang@oss.qualcomm.com \
    --cc=christophergriffin05@gmail.com \
    --cc=jeff.johnson@oss.qualcomm.com \
    --cc=jjohnson@kernel.org \
    --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®