All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jad Keskes <inasj268@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, dan.carpenter@linaro.org
Subject: Re: [PATCH] staging: rtl8723bs: replace beacon timing magic numbers with named constants
Date: Wed, 8 Jul 2026 15:36:23 +0100	[thread overview]
Message-ID: <ak5fovHVro3YTh9m@fedora> (raw)
In-Reply-To: <2026070820-unclog-busboy-dad9@gregkh>

On 07/08, Greg KH wrote:
> On Wed, Jul 08, 2026 at 03:17:02PM +0100, Jad Keskes wrote:
> 
> <snip>
> 
> For some reason you sent this only to me, which is a bit rude to
> everyone else on the mailing list.  I'll be glad to respond if you
> resend it to everyone.
> 
> thanks,
> 
> greg k-h

Apologies, meant to send that to the list. Resending:

Yeah, that info is from the out-of-tree driver Dan linked in the TODO thread.  
REG_TBTT_PROHIBIT has the same hold/setup layout as rtw88's WLAN_TBTT_HOLD_TIME / WLAN_TBTT_PROHIBIT.

REG_BCNTCFG — check rtl8192cu in the tree. Same register, same 0x66 CW byte. 
Production writes 0x660F, test chips write 0x66FF. Only the AIFS changes.


  parent reply	other threads:[~2026-07-08 14:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03 14:31 [PATCH] staging: rtl8723bs: replace magic numbers with named constants Jad Keskes
2026-06-04 14:31 ` Dan Carpenter
2026-06-04 14:34   ` Dan Carpenter
2026-06-04 15:18   ` [PATCH] staging: rtl8723bs: replace beacon timing " Jad Keskes
2026-07-07 11:05     ` Greg KH
     [not found]       ` <ak5bkRTGALDhBMAL@fedora>
     [not found]         ` <2026070820-unclog-busboy-dad9@gregkh>
2026-07-08 14:36           ` Jad Keskes [this message]
2026-07-08 14:58             ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2026-06-16 16:29 Jad Keskes
2026-06-16 17:09 ` Greg Kroah-Hartman
2026-07-08 15:09 Jad Keskes

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=ak5fovHVro3YTh9m@fedora \
    --to=inasj268@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-staging@lists.linux.dev \
    /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.