From: Ping-Ke Shih <pkshih@realtek.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: Viacheslav <adeep@lexina.in>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Jernej Škrabec" <jernej.skrabec@gmail.com>
Subject: RE: rtw88: rtl8822cs AP mode not working
Date: Mon, 15 Jan 2024 02:17:39 +0000 [thread overview]
Message-ID: <8192e59807e14525b821317a5f550ea4@realtek.com> (raw)
In-Reply-To: <CAFBinCDT2Pj_BYqCtk+i7y8LPU2qwah-4Scdq29ONBqs3wt0pQ@mail.gmail.com>
> -----Original Message-----
> From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> Sent: Sunday, January 14, 2024 6:50 AM
> To: Ping-Ke Shih <pkshih@realtek.com>
> Cc: Viacheslav <adeep@lexina.in>; linux-wireless@vger.kernel.org; Jernej Škrabec
> <jernej.skrabec@gmail.com>
> Subject: Re: rtw88: rtl8822cs AP mode not working
>
> Hi Ping-Ke,
>
> On Fri, Jan 12, 2024 at 1:40 AM Ping-Ke Shih <pkshih@realtek.com> wrote:
> [...]
> > > dmesg/journalctl is clean. No messages related to wifi.
> > >
> >
> > Have you ever tried AP mode on SDIO interface wifi cards, like RTL8822CS?
> > It seems no beacon issues properly, but no obvious errors during starting
> > AP mode.
> I haven't tried AP mode before (and I think* that Jernej also hasn't tried it).
>
> > I don't have this kind of wifi cards, could you help to check if AP mode
> > works in your side?
> I'll check that in the next few days.
> Also I'm wondering where code enables beacons (is it
> rtw_core_enable_beacon() or is there another relevant function?).
> Knowing that would be helpful to analyze this further.
>
The main function to get and set beacon template to firmware is
rtw_fw_download_rsvd_page(). The basic concept is to put beacon frame via
qsel=BCN to a special TX FIFO area called "reserve page", and then
hardware/firmware will send beacon in interval of 100ms.
The TX FIFO look like
+---------+
| | ^
| | |
| | |
| | | normal TX FIFO page
| | |
| | |
| | v
+---------+ <----------- BCN_HEAD
| | ^
| | | reserve page
| | v
+---------+
The initial pages of reserve page is to store beacon, but latter one could be
PS null frame that firmware uses it to notify AP.
Ping-Ke
next prev parent reply other threads:[~2024-01-15 2:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 7:07 rtw88: rtl8822cs AP mode not working Viacheslav
2024-01-10 9:15 ` Ping-Ke Shih
2024-01-10 11:04 ` Viacheslav
2024-01-11 0:42 ` Ping-Ke Shih
2024-01-11 6:19 ` Viacheslav
2024-01-12 0:39 ` Ping-Ke Shih
2024-01-13 22:50 ` Martin Blumenstingl
2024-01-15 2:17 ` Ping-Ke Shih [this message]
2024-01-16 22:07 ` Martin Blumenstingl
2024-01-17 0:35 ` Ping-Ke Shih
2024-01-17 7:34 ` Sascha Hauer
2024-01-17 9:48 ` Viacheslav
2024-01-17 20:48 ` Martin Blumenstingl
2024-04-18 6:58 ` Gabriel Tisan
2024-04-18 10:55 ` Viacheslav
2024-05-06 9:38 ` Gabriel Tisan
2024-05-06 10:18 ` Viacheslav
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=8192e59807e14525b821317a5f550ea4@realtek.com \
--to=pkshih@realtek.com \
--cc=adeep@lexina.in \
--cc=jernej.skrabec@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.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