From: Kalle Valo <kvalo@kernel.org>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: Sriram R <quic_srirrama@quicinc.com>,
<ath12k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 07/12] wifi: ath12k: Cache vdev configs before vdev create
Date: Sat, 13 Jan 2024 11:44:36 +0200 [thread overview]
Message-ID: <87cyu5h8jf.fsf@kernel.org> (raw)
In-Reply-To: <c35da30b-335c-4418-9d7c-0784ec9e8d30@quicinc.com> (Jeff Johnson's message of "Fri, 12 Jan 2024 09:23:59 -0800")
Jeff Johnson <quic_jjohnson@quicinc.com> writes:
>> +static int ath12k_mac_op_set_key(struct ieee80211_hw *hw, enum set_key_cmd cmd,
>> + struct ieee80211_vif *vif, struct ieee80211_sta *sta,
>> + struct ieee80211_key_conf *key)
>> +{
>> + struct ath12k_hw *ah = ath12k_hw_to_ah(hw);
>> + struct ath12k *ar;
>> + struct ath12k_vif *arvif = ath12k_vif_to_arvif(vif);
>> + int ret;
>> +
>> + /* BIP needs to be done in software */
>> + if (key->cipher == WLAN_CIPHER_SUITE_AES_CMAC ||
>> + key->cipher == WLAN_CIPHER_SUITE_BIP_GMAC_128 ||
>> + key->cipher == WLAN_CIPHER_SUITE_BIP_GMAC_256 ||
>> + key->cipher == WLAN_CIPHER_SUITE_BIP_CMAC_256)
>> + return 1;
>
> I know this in the existing code, but what is the significance of
> returning 1? Should this be returning a -errno like the error cases that
> follow?
It's to use software encryption, from mac80211.h:
* Note that in the case that the @IEEE80211_HW_SW_CRYPTO_CONTROL flag is
* set, mac80211 will not automatically fall back to software crypto if
* enabling hardware crypto failed. The set_key() call may also return the
* value 1 to permit this specific key/algorithm to be done in software.
Yeah, this is confusing. IMHO there should be a define or an enum for
this value.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-01-13 9:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 4:50 [PATCH 00/12] wifi: ath12k: Add single wiphy support Sriram R
2024-01-11 4:50 ` [PATCH 01/12] wifi: ath12k: add multiple radio support in a single MAC HW un/register Sriram R
2024-01-12 15:11 ` Jeff Johnson
2024-01-12 17:03 ` Jeff Johnson
2024-01-16 4:45 ` Karthikeyan Periyasamy
2024-01-11 4:50 ` [PATCH 02/12] wifi: ath12k: Modify add and remove chanctx ops for single wiphy support Sriram R
2024-01-12 17:05 ` Jeff Johnson
2024-01-11 4:50 ` [PATCH 03/12] wifi: ath12k: modify ath12k mac start/stop ops for single wiphy Sriram R
2024-01-12 17:07 ` Jeff Johnson
2024-01-11 4:50 ` [PATCH 04/12] wifi: ath12k: vdev statemachine changes " Sriram R
2024-01-12 17:10 ` Jeff Johnson
2024-01-11 4:50 ` [PATCH 05/12] wifi: ath12k: scan " Sriram R
2024-01-12 17:13 ` Jeff Johnson
2024-01-11 4:50 ` [PATCH 06/12] wifi: ath12k: fetch correct radio based on vdev status Sriram R
2024-01-12 17:15 ` Jeff Johnson
2024-01-11 4:50 ` [PATCH 07/12] wifi: ath12k: Cache vdev configs before vdev create Sriram R
2024-01-12 17:23 ` Jeff Johnson
2024-01-13 9:44 ` Kalle Valo [this message]
2024-01-11 4:50 ` [PATCH 08/12] wifi: ath12k: Add additional checks for vif and sta iterators Sriram R
2024-01-12 17:26 ` Jeff Johnson
2024-01-11 4:50 ` [PATCH 09/12] wifi: ath12k: modify regulatory support for single wiphy architecture Sriram R
2024-01-12 18:15 ` Jeff Johnson
2024-01-15 7:53 ` Sriram R (QUIC)
2024-01-11 4:50 ` [PATCH 10/12] wifi: ath12k: Modify set and get antenna mac ops for single wiphy Sriram R
2024-01-12 18:25 ` Jeff Johnson
2024-01-11 4:50 ` [PATCH 11/12] wifi: ath12k: Modify rts threshold mac op " Sriram R
2024-01-12 18:26 ` Jeff Johnson
2024-01-11 4:50 ` [PATCH 12/12] wifi: ath12k: support get_survey " Sriram R
2024-01-12 18:26 ` Jeff Johnson
2024-01-11 20:16 ` [PATCH 00/12] wifi: ath12k: Add single wiphy support Jeff Johnson
2024-01-12 4:34 ` Sriram R (QUIC)
2024-01-12 16:44 ` Jeff Johnson
2024-01-12 18:30 ` Jeff Johnson
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=87cyu5h8jf.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=quic_srirrama@quicinc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.