From: "Nemanov, Michael" <michael.nemanov@ti.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Kalle Valo <kvalo@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-wireless@vger.kernel.org>, <netdev@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Sabeeh Khan <sabeeh-khan@ti.com>
Subject: Re: [PATCH v5 09/17] wifi: cc33xx: Add main.c
Date: Thu, 14 Nov 2024 19:44:27 +0200 [thread overview]
Message-ID: <6bf6412d-8f9e-461d-913c-9718b5f0b8d3@ti.com> (raw)
In-Reply-To: <685d782d68bfc664c4fcc594dff96546ffc30e5f.camel@sipsolutions.net>
On 11/8/2024 1:42 PM, Johannes Berg wrote:
>> + if (sta_rate_set) {
>> + wlvif->rate_set = cc33xx_tx_enabled_rates_get(cc, sta_rate_set,
>> + wlvif->band);
>> + }
>
> you have a thing for extra braces ;-)
> (also in many other places)
>
Yeah most of those head debug traces that were dropped as part of the
feedback. Will fix the style too.
>> +static int cc33xx_init_ieee80211(struct cc33xx *cc)
>> +{
>> + unsigned int i;
>> +
>> + if (cc->conf.core.mixed_mode_support) {
>> + static const u32 cipher_suites[] = {
>> + WLAN_CIPHER_SUITE_CCMP,
>> + WLAN_CIPHER_SUITE_AES_CMAC,
>> + WLAN_CIPHER_SUITE_TKIP,
>> + WLAN_CIPHER_SUITE_GCMP,
>> + WLAN_CIPHER_SUITE_GCMP_256,
>> + WLAN_CIPHER_SUITE_BIP_GMAC_128,
>> + WLAN_CIPHER_SUITE_BIP_GMAC_256,
>> + };
>> + cc->hw->wiphy->cipher_suites = cipher_suites;
>> + cc->hw->wiphy->n_cipher_suites = ARRAY_SIZE(cipher_suites);
>> +
>> + } else {
>> + static const u32 cipher_suites[] = {
>> + WLAN_CIPHER_SUITE_CCMP,
>> + WLAN_CIPHER_SUITE_AES_CMAC,
>> + WLAN_CIPHER_SUITE_GCMP,
>> + WLAN_CIPHER_SUITE_GCMP_256,
>> + WLAN_CIPHER_SUITE_BIP_GMAC_128,
>> + WLAN_CIPHER_SUITE_BIP_GMAC_256,
>> + };
>
> I don't see you have GEM here, yet you handle it in other places above,
> that seems odd. Also I'm not sure it can work at all now that we removed
> the whole extended IV mess, unless you offloaded that?
>
This cipher is unsupported. Will remove this and any related code.
>> + /* clear channel flags from the previous usage
>> + * and restore max_power & max_antenna_gain values.
>> + */
>> + for (i = 0; i < ARRAY_SIZE(cc33xx_channels); i++) {
>> + cc33xx_band_2ghz.channels[i].flags = 0;
>> + cc33xx_band_2ghz.channels[i].max_power = CC33XX_MAX_TXPWR;
>> + cc33xx_band_2ghz.channels[i].max_antenna_gain = 0;
>> + }
>> +
>> + for (i = 0; i < ARRAY_SIZE(cc33xx_channels_5ghz); i++) {
>> + cc33xx_band_5ghz.channels[i].flags = 0;
>> + cc33xx_band_5ghz.channels[i].max_power = CC33XX_MAX_TXPWR;
>> + cc33xx_band_5ghz.channels[i].max_antenna_gain = 0;
>> + }
>> +
>> + /* Enable/Disable He based on conf file params */
>> + if (!cc->conf.mac.he_enable) {
>> + cc33xx_band_2ghz.iftype_data = NULL;
>> + cc33xx_band_2ghz.n_iftype_data = 0;
>> +
>> + cc33xx_band_5ghz.iftype_data = NULL;
>> + cc33xx_band_5ghz.n_iftype_data = 0;
>> + }
>
> it seems wrong to modify the global data here
>
>> + /* We keep local copies of the band structs because we need to
>> + * modify them on a per-device basis.
>> + */
>> + memcpy(&cc->bands[NL80211_BAND_2GHZ], &cc33xx_band_2ghz,
>> + sizeof(cc33xx_band_2ghz));
>> + memcpy(&cc->bands[NL80211_BAND_2GHZ].ht_cap,
>> + &cc->ht_cap[NL80211_BAND_2GHZ],
>> + sizeof(*cc->ht_cap));
>
> and in particular if you *then* do that??
>
I see your point. I'll drop the init loops and use C initializers
instead as this data does not change. Any dynamic modification will done
to cc->bands.
Thanks and regards,
Michael.
next prev parent reply other threads:[~2024-11-14 17:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 12:51 [PATCH v5 00/17] wifi: cc33xx: Add driver for new TI CC33xx wireless device family Michael Nemanov
2024-11-07 12:51 ` [PATCH v5 01/17] dt-bindings: net: wireless: cc33xx: Add ti,cc33xx.yaml Michael Nemanov
2024-11-08 12:02 ` Krzysztof Kozlowski
2024-11-12 6:45 ` Nemanov, Michael
2024-11-19 9:15 ` Krzysztof Kozlowski
2024-11-19 12:10 ` Nemanov, Michael
2024-11-08 12:07 ` Krzysztof Kozlowski
2024-11-07 12:51 ` [PATCH v5 02/17] wifi: cc33xx: Add cc33xx.h, cc33xx_i.h Michael Nemanov
2024-11-07 12:51 ` [PATCH v5 03/17] wifi: cc33xx: Add debug.h Michael Nemanov
2024-11-07 12:51 ` [PATCH v5 04/17] wifi: cc33xx: Add sdio.c, io.c, io.h Michael Nemanov
2024-11-07 12:51 ` [PATCH v5 05/17] wifi: cc33xx: Add cmd.c, cmd.h Michael Nemanov
2024-11-08 16:25 ` Markus Elfring
2024-11-07 12:51 ` [PATCH v5 06/17] wifi: cc33xx: Add acx.c, acx.h Michael Nemanov
2024-11-07 12:51 ` [PATCH v5 07/17] wifi: cc33xx: Add event.c, event.h Michael Nemanov
2024-11-07 12:52 ` [PATCH v5 08/17] wifi: cc33xx: Add boot.c, boot.h Michael Nemanov
2024-11-07 12:52 ` [PATCH v5 09/17] wifi: cc33xx: Add main.c Michael Nemanov
2024-11-08 11:42 ` Johannes Berg
2024-11-11 11:38 ` Kalle Valo
2024-11-12 15:34 ` Nemanov, Michael
2024-11-12 15:39 ` Johannes Berg
2024-11-14 17:44 ` Nemanov, Michael [this message]
2024-12-01 9:47 ` Nemanov, Michael
2024-12-01 17:09 ` Nemanov, Michael
2024-11-07 12:52 ` [PATCH v5 10/17] wifi: cc33xx: Add rx.c, rx.h Michael Nemanov
2024-11-07 12:52 ` [PATCH v5 11/17] wifi: cc33xx: Add tx.c, tx.h Michael Nemanov
2024-11-07 12:52 ` [PATCH v5 12/17] wifi: cc33xx: Add init.c, init.h Michael Nemanov
2024-11-07 12:52 ` [PATCH v5 13/17] wifi: cc33xx: Add scan.c, scan.h Michael Nemanov
2024-11-07 12:52 ` [PATCH v5 14/17] wifi: cc33xx: Add conf.h Michael Nemanov
2024-11-07 12:52 ` [PATCH v5 15/17] wifi: cc33xx: Add ps.c, ps.h Michael Nemanov
2024-11-07 12:52 ` [PATCH v5 16/17] wifi: cc33xx: Add testmode.c, testmode.h Michael Nemanov
2024-11-07 12:52 ` [PATCH v5 17/17] wifi: cc33xx: Add Kconfig, Makefile Michael Nemanov
2025-04-29 16:38 ` [PATCH v5 00/17] wifi: cc33xx: Add driver for new TI CC33xx wireless device family Ezra Buehler
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=6bf6412d-8f9e-461d-913c-9718b5f0b8d3@ti.com \
--to=michael.nemanov@ti.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=sabeeh-khan@ti.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®