linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Kevin Yang" <kevin_yang@realtek.com>
Subject: Re: [PATCH 0/6] wifi: rtw89: preparation of TDMA-based MCC (STA+P2P)
Date: Wed, 23 Aug 2023 21:24:56 +0300	[thread overview]
Message-ID: <87fs49hb0n.fsf@kernel.org> (raw)
In-Reply-To: <22a5d99c4f4be30dd7659400ba9a42c0701f6521.camel@realtek.com> (Ping-Ke Shih's message of "Wed, 23 Aug 2023 14:47:12 +0000")

Ping-Ke Shih <pkshih@realtek.com> writes:

> On Wed, 2023-08-23 at 16:56 +0300, Kalle Valo wrote:
>> 
>> Ping-Ke Shih <pkshih@realtek.com> writes:
>> 
>> > TDMA-based MCC (STA+P2P) is a kind of multiple interfaces concurrence.
>> > Basically, driver is to calculate timeslot pattern and firmware follows
>> > the pattern to switch channels. Since BT-coexistence is also a TDMA-based
>> > mechanism, also consider BT timeslot into pattern if BT devices present.
>> 
>> What do you mean with TDMA here? It something like that in STA mode the
>> driver enables 802.11 PS mode before going to another channel? Or
>> something else?
>> 
>
> Yes, when it is working as STA mode or GC, using 802.11 PS mode before
> switching channel. When it plays as GO, NoA is used to inform GC absent
> timing. 
>
> For example, STA on channel 1 + GO on channel 11, and preserve some
> time slot for BT
>
>
>                              (1)
>  channel 1   (STA)   +++++++++
>
>                               (2)
>  channel 11  (GO)             +++++++++
>
>  BT                                    ++++++++
>
>                      |<----------------------->|
>                        Period (or cycle time)
>  
> (1) issue null with power bit
> (2) issue beacon with NoA 
>
>
> Though STA and GO are in different channels, they don't operate at
> the same time. This is the reason I point "TDMA" to prevent
> misunderstanding two virtual interfaces can operate two channels
> at the same time, which may be called DBS or DBCC. But, I'm trying
> to explain hardware capability correctly.

Got it, thanks for the great explanation.

Just out of curiosity, how do you create your ascii diagrams? Is there
some nifty tool to help with those? :)

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2023-08-23 18:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16  8:21 [PATCH 0/6] wifi: rtw89: preparation of TDMA-based MCC (STA+P2P) Ping-Ke Shih
2023-08-16  8:21 ` [PATCH 1/6] wifi: rtw89: add function prototype for coex request duration Ping-Ke Shih
2023-08-25  9:59   ` Kalle Valo
2023-08-16  8:21 ` [PATCH 2/6] wifi: rtw89: refine rtw89_correct_cck_chan() by rtw89_hw_to_nl80211_band() Ping-Ke Shih
2023-08-16  8:21 ` [PATCH 3/6] wifi: rtw89: sar: let caller decide the center frequency to query Ping-Ke Shih
2023-08-16  8:21 ` [PATCH 4/6] wifi: rtw89: call rtw89_chan_get() by vif chanctx if aware of vif Ping-Ke Shih
2023-08-16  8:21 ` [PATCH 5/6] wifi: rtw89: provide functions to configure NoA for beacon update Ping-Ke Shih
2023-08-16  8:21 ` [PATCH 6/6] wifi: rtw89: initialize multi-channel handling Ping-Ke Shih
2023-08-23 13:56 ` [PATCH 0/6] wifi: rtw89: preparation of TDMA-based MCC (STA+P2P) Kalle Valo
2023-08-23 14:47   ` Ping-Ke Shih
2023-08-23 18:24     ` Kalle Valo [this message]
2023-08-24  1:10       ` Ping-Ke Shih
2023-08-25  7:14         ` Kalle Valo

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=87fs49hb0n.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=kevin_yang@realtek.com \
    --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 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).