From: Kalle Valo <kvalo@kernel.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 5/5] wifi: rtw89: support TX diversity for 1T2R chipset
Date: Wed, 07 Sep 2022 10:46:35 +0300 [thread overview]
Message-ID: <878rmvaap0.fsf@kernel.org> (raw)
In-Reply-To: <20220902124422.13610-6-pkshih@realtek.com> (Ping-Ke Shih's message of "Fri, 2 Sep 2022 20:44:22 +0800")
Ping-Ke Shih <pkshih@realtek.com> writes:
> Check RSSI strength to decide which path is better, and then set TX path
> accordingly.
>
> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
[...]
> +static void rtw89_phy_tx_path_div_sta_iter(void *data, struct ieee80211_sta *sta)
> +{
> + struct rtw89_sta *rtwsta = (struct rtw89_sta *)sta->drv_priv;
> + struct rtw89_dev *rtwdev = rtwsta->rtwdev;
> + struct rtw89_vif *rtwvif = rtwsta->rtwvif;
> + struct rtw89_hal *hal = &rtwdev->hal;
> + bool *done = (bool *)data;
data is a void pointer, you don't need the cast here.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-09-07 7:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 12:44 [PATCH 0/5] wifi: rtw89: support TX diversity for 1T2R variant model Ping-Ke Shih
2022-09-02 12:44 ` [PATCH 1/5] wifi: rtw89: use u32_get_bits to access C2H content of PHY capability Ping-Ke Shih
2022-09-02 12:44 ` [PATCH 2/5] wifi: rtw89: parse phycap of TX/RX antenna number Ping-Ke Shih
2022-09-02 12:44 ` [PATCH 3/5] wifi: rtw89: configure TX path via H2C command Ping-Ke Shih
2022-09-07 7:43 ` Kalle Valo
2022-09-02 12:44 ` [PATCH 4/5] wifi: rtw89: record signal strength per RF path Ping-Ke Shih
2022-09-02 12:44 ` [PATCH 5/5] wifi: rtw89: support TX diversity for 1T2R chipset Ping-Ke Shih
2022-09-07 7:46 ` Kalle Valo [this message]
2022-09-07 9:21 ` 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=878rmvaap0.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.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.