From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: Ping-Ke Shih <pkshih@realtek.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 16:33:19 +0300 [thread overview]
Message-ID: <6ea2dd8b-fe9e-4434-b502-5badfe547c1f@gmail.com> (raw)
In-Reply-To: <3fedc4d56ac3414e8e500961b9850aa1@realtek.com>
On 11/06/2024 06:26, Ping-Ke Shih wrote:
> 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.
>
I thought you wanted the members initialised in the same order
they appear in struct rtw_chip_info in main.h. Maybe I misunderstood.
> 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.
>
Ah, it should be done in a different patch, okay.
I'm still not sure what you meant here:
>> diff --git a/drivers/net/wireless/realtek/rtw88/main.h b/drivers/net/wireless/realtek/rtw88/main.h
>> index 49894331f7b4..49a3fd4fb7dc 100644
>> --- a/drivers/net/wireless/realtek/rtw88/main.h
>> +++ b/drivers/net/wireless/realtek/rtw88/main.h
>> @@ -1197,6 +1197,8 @@ struct rtw_chip_info {
>> u16 fw_fifo_addr[RTW_FW_FIFO_MAX];
>> const struct rtw_fwcd_segs *fwcd_segs;
>>
>> + u8 usb_tx_agg_desc_num;
>> +
>
> Please keep order of field and instance declaration, like rtw8703b_hw_spec.
and here:
>> #define REG_DWBCN0_CTRL 0x0208
>> #define BIT_BCN_VALID BIT(16)
>> #define REG_TXDMA_OFFSET_CHK 0x020C
>> diff --git a/drivers/net/wireless/realtek/rtw88/rtw8703b.c
>> b/drivers/net/wireless/realtek/rtw88/rtw8703b.c
>> index 8919f9e11f03..222608de33cd 100644
>> --- a/drivers/net/wireless/realtek/rtw88/rtw8703b.c
>> +++ b/drivers/net/wireless/realtek/rtw88/rtw8703b.c
>> @@ -2013,6 +2013,7 @@ const struct rtw_chip_info rtw8703b_hw_spec = {
>> .tx_stbc = false,
>> .max_power_index = 0x3f,
>> .ampdu_density = IEEE80211_HT_MPDU_DENSITY_16,
>> + .usb_tx_agg_desc_num = 1, /* Not sure if this chip has USB interface */
>
> The position to declare this field is very different from others.
>
> Not sure when we messed up the order, but please don't feel free to add one,
> keep the order.
next prev parent reply other threads:[~2024-06-11 13:33 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
2024-06-11 13:33 ` Bitterblue Smith [this message]
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=6ea2dd8b-fe9e-4434-b502-5badfe547c1f@gmail.com \
--to=rtl8821cerfe2@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.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