From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: Martin Kaistra <martin.kaistra@linutronix.de>,
linux-wireless@vger.kernel.org
Cc: Jes Sorensen <Jes.Sorensen@gmail.com>,
Kalle Valo <kvalo@kernel.org>, Ping-Ke Shih <pkshih@realtek.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [RFC PATCH 01/14] wifi: rtl8xxxu: Add start_ap() callback
Date: Mon, 27 Mar 2023 16:10:16 +0300 [thread overview]
Message-ID: <62bf7fa9-e041-c8d8-c63e-42b3674fc9d8@gmail.com> (raw)
In-Reply-To: <20230322171905.492855-2-martin.kaistra@linutronix.de>
On 22/03/2023 19:18, Martin Kaistra wrote:
> This gets called at the start of AP mode operation. Set bssid, beacon
> interval and send a connect report to the HW.
>
Hmm, but why send a connect report when you don't have anything
connected yet?
> Signed-off-by: Martin Kaistra <martin.kaistra@linutronix.de>
> ---
> .../net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c
> index c152b228606f1..90b98b9dcbd9d 100644
> --- a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c
> +++ b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c
> @@ -4899,6 +4899,20 @@ rtl8xxxu_bss_info_changed(struct ieee80211_hw *hw, struct ieee80211_vif *vif,
> return;
> }
>
> +static int rtl8xxxu_start_ap(struct ieee80211_hw *hw, struct ieee80211_vif *vif,
> + struct ieee80211_bss_conf *link_conf)
> +{
> + struct rtl8xxxu_priv *priv = hw->priv;
> + struct device *dev = &priv->udev->dev;
> +
> + dev_dbg(dev, "Start AP mode\n");
> + rtl8xxxu_set_bssid(priv, vif->bss_conf.bssid);
> + rtl8xxxu_write16(priv, REG_BCN_INTERVAL, vif->bss_conf.beacon_int);
> + priv->fops->report_connect(priv, 0, true);
> +
> + return 0;
> +}
> +
> static u32 rtl8xxxu_80211_to_rtl_queue(u32 queue)
> {
> u32 rtlqueue;
> @@ -7026,6 +7040,7 @@ static const struct ieee80211_ops rtl8xxxu_ops = {
> .config = rtl8xxxu_config,
> .conf_tx = rtl8xxxu_conf_tx,
> .bss_info_changed = rtl8xxxu_bss_info_changed,
> + .start_ap = rtl8xxxu_start_ap,
> .configure_filter = rtl8xxxu_configure_filter,
> .set_rts_threshold = rtl8xxxu_set_rts_threshold,
> .start = rtl8xxxu_start,
next prev parent reply other threads:[~2023-03-27 13:10 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 17:18 [RFC PATCH 00/14] wifi: rtl8xxxu: Add AP mode support for 8188f Martin Kaistra
2023-03-22 17:18 ` [RFC PATCH 01/14] wifi: rtl8xxxu: Add start_ap() callback Martin Kaistra
2023-03-27 0:46 ` Ping-Ke Shih
2023-03-27 13:10 ` Bitterblue Smith [this message]
2023-03-27 16:08 ` Martin Kaistra
2023-03-27 18:29 ` Bitterblue Smith
2023-03-29 0:18 ` Ping-Ke Shih
2023-03-22 17:18 ` [RFC PATCH 02/14] wifi: rtl8xxxu: Select correct queue for beacon frames Martin Kaistra
2023-03-27 0:51 ` Ping-Ke Shih
2023-03-22 17:18 ` [RFC PATCH 03/14] wifi: rtl8xxxu: Add beacon functions Martin Kaistra
2023-03-27 1:19 ` Ping-Ke Shih
2023-03-27 13:10 ` Bitterblue Smith
2023-03-22 17:18 ` [RFC PATCH 04/14] wifi: rtl8xxxu: Add set_tim() callback Martin Kaistra
2023-03-27 1:20 ` Ping-Ke Shih
2023-03-22 17:18 ` [RFC PATCH 05/14] wifi: rtl8xxxu: Allow setting rts threshold to -1 Martin Kaistra
2023-03-27 1:21 ` Ping-Ke Shih
2023-03-22 17:18 ` [RFC PATCH 06/14] wifi: rtl8xxxu: Allow creating interface in AP mode Martin Kaistra
2023-03-27 1:39 ` Ping-Ke Shih
2023-03-27 13:15 ` Martin Kaistra
2023-03-22 17:18 ` [RFC PATCH 07/14] wifi: rtl8xxxu: Add parameter macid to update_rate_mask Martin Kaistra
2023-03-27 1:48 ` Ping-Ke Shih
2023-03-27 8:41 ` Kalle Valo
2023-03-27 9:19 ` Ping-Ke Shih
2023-03-27 13:12 ` Bitterblue Smith
2023-03-22 17:18 ` [RFC PATCH 08/14] wifi: rtl8xxxu: Actually use macid in rtl8xxxu_gen2_report_connect Martin Kaistra
2023-03-27 1:48 ` Ping-Ke Shih
2023-03-22 17:19 ` [RFC PATCH 09/14] wifi: rtl8xxxu: Add parameter role to report_connect Martin Kaistra
2023-03-27 1:54 ` Ping-Ke Shih
2023-03-27 13:11 ` Bitterblue Smith
2023-03-22 17:19 ` [RFC PATCH 10/14] wifi: rtl8xxxu: Add sta_add() callback Martin Kaistra
2023-03-27 1:56 ` Ping-Ke Shih
2023-03-22 17:19 ` [RFC PATCH 11/14] wifi: rtl8xxxu: Put the macid in txdesc Martin Kaistra
2023-03-27 1:58 ` Ping-Ke Shih
2023-03-27 13:11 ` Bitterblue Smith
2023-03-22 17:19 ` [RFC PATCH 12/14] wifi: rtl8xxxu: Enable hw seq for all non-qos frames Martin Kaistra
2023-03-27 2:01 ` Ping-Ke Shih
2023-03-22 17:19 ` [RFC PATCH 13/14] wifi: rtl8xxxu: Clean up filter configuration Martin Kaistra
2023-03-27 2:06 ` Ping-Ke Shih
2023-03-28 14:47 ` Martin Kaistra
2023-03-29 0:27 ` Ping-Ke Shih
2023-03-22 17:19 ` [RFC PATCH 14/14] wifi: rtl8xxxu: Declare AP mode support for 8188f Martin Kaistra
2023-03-27 2:06 ` Ping-Ke Shih
2023-03-23 17:12 ` [RFC PATCH 00/14] wifi: rtl8xxxu: Add " Bitterblue Smith
2023-03-27 7:58 ` Martin Kaistra
2023-04-05 15:31 ` Martin Kaistra
2023-04-06 0:42 ` Ping-Ke Shih
2023-04-06 15:09 ` Martin Kaistra
2023-04-09 12:41 ` Bitterblue Smith
2023-04-12 10:02 ` Martin Kaistra
2023-04-14 21:49 ` Bitterblue Smith
2023-04-07 1:18 ` 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=62bf7fa9-e041-c8d8-c63e-42b3674fc9d8@gmail.com \
--to=rtl8821cerfe2@gmail.com \
--cc=Jes.Sorensen@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.kaistra@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).