From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Sascha Hauer <sha@pengutronix.de>
Subject: RE: [PATCH v2] wifi: rtw88: usb: Further limit the TX aggregation
Date: Tue, 11 Jun 2024 03:26:14 +0000 [thread overview]
Message-ID: <3fedc4d56ac3414e8e500961b9850aa1@realtek.com> (raw)
In-Reply-To: <dfb019b6-4285-4381-86d2-d85409abee4b@gmail.com>
Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> @@ -2065,25 +2066,26 @@ const struct rtw_chip_info rtw8703b_hw_spec = {
> .bt_rssi_type = COEX_BTRSSI_RATIO,
> .ant_isolation = 15,
> .rssi_tolerance = 2,
> - .bt_rssi_step = bt_rssi_step_8703b,
> - .wl_rssi_step = wl_rssi_step_8703b,
> /* sant -> shared antenna, nsant -> non-shared antenna
> * Not sure if 8703b versions with non-shard antenna even exist.
> */
> .table_sant_num = ARRAY_SIZE(table_sant_8703b),
> - .table_sant = table_sant_8703b,
Not sure why you move array and array size apart.
No need to churn this as well as other similar stuffs.
This patch can only change things required by what subject mention. Align these
fields by another patch, or do it later. Both are fine to me.
> .table_nsant_num = 0,
> - .table_nsant = NULL,
> .tdma_sant_num = ARRAY_SIZE(tdma_sant_8703b),
> - .tdma_sant = tdma_sant_8703b,
> .tdma_nsant_num = 0,
> - .tdma_nsant = NULL,
> - .wl_rf_para_num = ARRAY_SIZE(rf_para_tx_8703b),
> - .wl_rf_para_tx = rf_para_tx_8703b,
> - .wl_rf_para_rx = rf_para_rx_8703b,
> .bt_afh_span_bw20 = 0x20,
> .bt_afh_span_bw40 = 0x30,
> .afh_5g_num = ARRAY_SIZE(afh_5g_8703b),
> + .wl_rf_para_num = ARRAY_SIZE(rf_para_tx_8703b),
> + .coex_info_hw_regs_num = 0,
> + .bt_rssi_step = bt_rssi_step_8703b,
> + .wl_rssi_step = wl_rssi_step_8703b,
> + .table_nsant = NULL,
> + .table_sant = table_sant_8703b,
> + .tdma_sant = tdma_sant_8703b,
> + .tdma_nsant = NULL,
> + .wl_rf_para_tx = rf_para_tx_8703b,
> + .wl_rf_para_rx = rf_para_rx_8703b,
> .afh_5g = afh_5g_8703b,
> /* REG_BTG_SEL doesn't seem to have a counterpart in the
> * vendor driver. Mathematically it's REG_PAD_CTRL1 + 3.
> @@ -2096,7 +2098,6 @@ const struct rtw_chip_info rtw8703b_hw_spec = {
> /* These registers are used to read (and print) from if
> * CONFIG_RTW88_DEBUGFS is enabled.
> */
> - .coex_info_hw_regs_num = 0,
> .coex_info_hw_regs = NULL,
> };
> EXPORT_SYMBOL(rtw8703b_hw_spec);
next prev parent reply other threads:[~2024-06-11 3:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 14:42 [PATCH] wifi: rtw88: usb: Further limit the TX aggregation Bitterblue Smith
2024-05-30 6:36 ` Ping-Ke Shih
2024-05-31 21:10 ` Bitterblue Smith
2024-06-10 17:27 ` [PATCH v2] " Bitterblue Smith
2024-06-11 3:26 ` Ping-Ke Shih [this message]
2024-06-11 13:33 ` Bitterblue Smith
2024-06-12 1:24 ` Ping-Ke Shih
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=3fedc4d56ac3414e8e500961b9850aa1@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rtl8821cerfe2@gmail.com \
--cc=sha@pengutronix.de \
/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