From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Karthikeyan Kathirvel <karthikeyan.kathirvel@oss.qualcomm.com>,
Nicolas Escande <nico.escande@gmail.com>,
ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH ath-next] wifi: ath12k: allow beacon protection keys to be installed in hardware
Date: Wed, 4 Jun 2025 13:38:20 -0700 [thread overview]
Message-ID: <a949a8f5-1b08-4ba8-bd74-c2fd7fb754fc@oss.qualcomm.com> (raw)
In-Reply-To: <3249b83b-00e6-464a-a6ad-80e114ffd438@oss.qualcomm.com>
On 6/4/2025 1:59 AM, Karthikeyan Kathirvel wrote:
> On 5/9/2025 9:37 PM, Jeff Johnson wrote:
>> Will you be spinning a v2? Note the dependent mac80211 change has merged.
> Yes Jeff, we've identified and confirmed a firmware bug that gets
> triggered during IGTK key installation, which leads to corruption of the
> GTK keys in firmware. To work around this, I’ll send a new version where
> IGTK uses software crypto. Once the firmware bug is resolved upstream,
> we can re-enable hardware offload for IGTK.
Note that then means firmware must advertise that the correct support is
present so that the host knows whether or not it can enable the offload.
/jeff
next prev parent reply other threads:[~2025-06-04 20:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 11:47 [PATCH ath-next] wifi: ath12k: allow beacon protection keys to be installed in hardware Karthikeyan Kathirvel
2025-04-21 17:16 ` kernel test robot
2025-04-21 18:44 ` Jeff Johnson
2025-04-23 1:37 ` Philip Li
2025-04-23 18:05 ` Jeff Johnson
2025-04-22 9:48 ` kernel test robot
2025-04-29 15:47 ` Nicolas Escande
2025-04-30 6:05 ` Karthikeyan Kathirvel
2025-05-09 16:07 ` Jeff Johnson
2025-06-04 8:59 ` Karthikeyan Kathirvel
2025-06-04 20:38 ` Jeff Johnson [this message]
2025-06-06 13:22 ` Karthikeyan Kathirvel
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=a949a8f5-1b08-4ba8-bd74-c2fd7fb754fc@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=karthikeyan.kathirvel@oss.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nico.escande@gmail.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