From: Kalle Valo <kvalo@kernel.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: <phhuang@realtek.com>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/4] wifi: rtw89: add mac TSF sync function
Date: Thu, 8 Dec 2022 14:48:13 +0000 (UTC) [thread overview]
Message-ID: <167051089193.9839.7580560813060192456.kvalo@kernel.org> (raw)
In-Reply-To: <20221202061527.505668-2-pkshih@realtek.com>
Ping-Ke Shih <pkshih@realtek.com> wrote:
> From: Po-Hao Huang <phhuang@realtek.com>
>
> If the interface is in AP/P2P GO mode, we adjust the TSF with random
> offset to avoid TBTT of different vifs to overlap and collide.
> For every new interface added, we adjust the value and resync for all
> interfaces.
>
> Signed-off-by: Po-Hao Huang <phhuang@realtek.com>
> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
4 patches applied to wireless-next.git, thanks.
fb2b8cec81d7 wifi: rtw89: add mac TSF sync function
d592b9f74264 wifi: rtw89: stop mac port function when stop_ap()
8fc5d4338620 wifi: rtw89: fix unsuccessful interface_add flow
a0e78d5c6082 wifi: rtw89: add join info upon create interface
--
https://patchwork.kernel.org/project/linux-wireless/patch/20221202061527.505668-2-pkshih@realtek.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-12-08 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 6:15 [PATCH 0/4] wifi: rtw89: correct settings for multiple VIFs Ping-Ke Shih
2022-12-02 6:15 ` [PATCH 1/4] wifi: rtw89: add mac TSF sync function Ping-Ke Shih
2022-12-08 14:48 ` Kalle Valo [this message]
2022-12-02 6:15 ` [PATCH 2/4] wifi: rtw89: stop mac port function when stop_ap() Ping-Ke Shih
2022-12-02 6:15 ` [PATCH 3/4] wifi: rtw89: fix unsuccessful interface_add flow Ping-Ke Shih
2022-12-02 6:15 ` [PATCH 4/4] wifi: rtw89: add join info upon create interface 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=167051089193.9839.7580560813060192456.kvalo@kernel.org \
--to=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=phhuang@realtek.com \
--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.