Linux wireless drivers development
 help / color / mirror / Atom feed
From: Mehmet Fide <mehmet.fide@gmail.com>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	mehmet.fide@screeningeagle.com
Subject: Re: [PATCH rtw-next v7 3/3] wifi: rtw88: time the countdown downloads from the TBTT
Date: Wed, 21 Oct 2026 09:24:23 +0200	[thread overview]
Message-ID: <20261021072423.4006833-1-mehmet.fide@gmail.com> (raw)
In-Reply-To: <f61cfbcd59cd441da59a16db52512897@realtek.com>

Hi Ping-Ke,

On 2026-10-21, Ping-Ke Shih wrote:
> +/* the beaconing interface is always on port 0 */
>
> Move into function? Or just mention this in commit message.

The commit message says it already, so v8 drops the comment.

> How about setting a retry limit? Consider if hardware goes wrong
> suddenly returning random number, I'm afraid it becomes infinite
> loop. As my thought, at most it needs one time retry.

Agreed. v8 reads the high word once more and, if it changed, the low
word again; no loop.

> an empty line

Will do, all three.

> The csa_tbtt is just read from register and adjusted to what you want,
> but in rtw_fw_csa_queue() it reads again and adjust. Can you reduce it?
> How about adding an argument to tell rtw_fw_csa_queue() that this is first
> time to initialize csa_tbtt (like the restart case)?

Yes. In v8 rtw_fw_csa_queue() takes a start argument and reads the TSF
once: on start it takes the next TBTT, or the one just passed within
the margin, and the countdown work adds an interval as before.

Regards,
Mehmet

      reply	other threads:[~2026-10-21  7:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 20:47 [PATCH rtw-next v7 0/3] wifi: rtw88: channel switch in AP mode Mehmet Fide
2026-10-20 20:47 ` [PATCH rtw-next v7 1/3] wifi: rtw88: download the beacon the reserved page was built with Mehmet Fide
2026-10-20 20:47 ` [PATCH rtw-next v7 2/3] wifi: rtw88: support channel switch in AP mode Mehmet Fide
2026-10-21  2:30   ` Ping-Ke Shih
2026-10-20 20:47 ` [PATCH rtw-next v7 3/3] wifi: rtw88: time the countdown downloads from the TBTT Mehmet Fide
2026-10-21  3:35   ` Ping-Ke Shih
2026-10-21  7:24     ` Mehmet Fide [this message]

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=20261021072423.4006833-1-mehmet.fide@gmail.com \
    --to=mehmet.fide@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mehmet.fide@screeningeagle.com \
    --cc=pkshih@realtek.com \
    --cc=rtl8821cerfe2@gmail.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