From: Rameshkumar Sundaram <rameshkumar.sundaram@oss.qualcomm.com>
To: christophergriffin05@gmail.com,
Jeff Johnson <jjohnson@kernel.org>,
John Crispin <john@phrozen.org>, Kalle Valo <kvalo@kernel.org>,
Shashidhar Lakkavalli <slakkavalli@datto.com>,
P Praneesh <quic_ppranees@quicinc.com>,
Pradeep Kumar Chitrapu <quic_pradeepc@quicinc.com>,
Karthikeyan Periyasamy <quic_periyasa@quicinc.com>,
Wen Gong <quic_wgong@quicinc.com>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
linux-kernel@vger.kernel.org,
Baochen Qiang <baochen.qiang@oss.qualcomm.com>,
Carl Huang <quic_cjhuang@quicinc.com>,
Ramya Gnanasekar <quic_rgnanase@quicinc.com>,
Balamurugan Selvarajan <quic_bselvara@quicinc.com>,
ath12k@lists.infradead.org
Subject: Re: [PATCH ath-next 0/2] wifi: ath11k/ath12k: don't bit-reverse the firmware's PPE thresholds
Date: Thu, 5 Nov 2026 22:42:54 +0530 [thread overview]
Message-ID: <d9da4f14-4f13-4cec-b519-2c848894c35c@oss.qualcomm.com> (raw)
In-Reply-To: <20261104-ath-ppe-thresholds-bit-order-v1-0-0f569106cbc4@gmail.com>
On 11/5/2026 10:47 AM, Christopher Griffin via B4 Relay wrote:
> ath11k and ath12k build the PPE Thresholds field of their HE
> capabilities from the firmware's WMI layout with each 3-bit threshold
> bit-reversed (QPSK and 256-QAM swap places, 64-QAM becomes reserved),
> while a peer's thresholds are converted the right way. Firmware that
> reports 0 and 7 only, as IPQ8074 and QCN9074 do, hides it. One patch
> per driver.
>
> ---
> Christopher Griffin (2):
> wifi: ath11k: don't bit-reverse the firmware's PPE thresholds
> wifi: ath12k: don't bit-reverse the firmware's PPE thresholds
>
> drivers/net/wireless/ath/ath11k/mac.c | 3 +--
> drivers/net/wireless/ath/ath12k/mac.c | 3 +--
> 2 files changed, 2 insertions(+), 4 deletions(-)
> ---
> base-commit: a3ddbb45768717b5c9f923489387cf55c838d1ad
> change-id: 20261104-ath-ppe-thresholds-bit-order-436ac99c5745
Apart from Assisted-by Tag nits,
Reviewed-by: Rameshkumar Sundaram <rameshkumar.sundaram@oss.qualcomm.com>
prev parent reply other threads:[~2026-11-05 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 5:17 Christopher Griffin via B4 Relay
2026-11-05 5:17 ` [PATCH ath-next 1/2] wifi: ath11k: " Christopher Griffin via B4 Relay
2026-11-05 17:04 ` Rameshkumar Sundaram
2026-11-05 5:17 ` [PATCH ath-next 2/2] wifi: ath12k: " Christopher Griffin via B4 Relay
2026-11-05 17:12 ` Rameshkumar Sundaram [this message]
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=d9da4f14-4f13-4cec-b519-2c848894c35c@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=jjohnson@kernel.org \
--cc=john@phrozen.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_bselvara@quicinc.com \
--cc=quic_cjhuang@quicinc.com \
--cc=quic_periyasa@quicinc.com \
--cc=quic_ppranees@quicinc.com \
--cc=quic_pradeepc@quicinc.com \
--cc=quic_rgnanase@quicinc.com \
--cc=quic_wgong@quicinc.com \
--cc=slakkavalli@datto.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
all inboxes | Powered by JetHome®